How did some of my text get highlighted with a magenta background?Unable to disable binding defined by undo-treeEmacs 24 keybindings for texWhat datatype is accepted by the last argument of the define-key function?What key sequence is killing a large chunk of my buffer?Is it possible to cancel a key combination half way through?How to find out what command I just accidentally ran with a keyboard shortcut?rebind C-RET in cua-mode to a different key?How to troubleshoot a key binding prompting for more key presses?How to bind mouse click to kill an inactive window, but not the bufferHow can I press a key combination including CTRL and ALT_GR on a Swedish keyboard?

Why has Russell's definition of numbers using equivalence classes been finally abandoned? ( If it has actually been abandoned).

How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?

I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine

New order #4: World

What defenses are there against being summoned by the Gate spell?

How do you conduct xenoanthropology after first contact?

Can Medicine checks be used, with decent rolls, to completely mitigate the risk of death from ongoing damage?

I probably found a bug with the sudo apt install function

Why is this code 6.5x slower with optimizations enabled?

Download, install and reboot computer at night if needed

Japan - Plan around max visa duration

A Journey Through Space and Time

A newer friend of my brother's gave him a load of baseball cards that are supposedly extremely valuable. Is this a scam?

least quadratic residue under GRH: an EXPLICIT bound

Is it possible to make sharp wind that can cut stuff from afar?

How is it possible for user's password to be changed after storage was encrypted? (on OS X, Android)

Modification to Chariots for Heavy Cavalry Analogue for 4-armed race

Concept of linear mappings are confusing me

What typically incentivizes a professor to change jobs to a lower ranking university?

How can I fix this gap between bookcases I made?

How can the DM most effectively choose 1 out of an odd number of players to be targeted by an attack or effect?

How do I create uniquely male characters?

Why CLRS example on residual networks does not follows its formula?

Why was the small council so happy for Tyrion to become the Master of Coin?



How did some of my text get highlighted with a magenta background?


Unable to disable binding defined by undo-treeEmacs 24 keybindings for texWhat datatype is accepted by the last argument of the define-key function?What key sequence is killing a large chunk of my buffer?Is it possible to cancel a key combination half way through?How to find out what command I just accidentally ran with a keyboard shortcut?rebind C-RET in cua-mode to a different key?How to troubleshoot a key binding prompting for more key presses?How to bind mouse click to kill an inactive window, but not the bufferHow can I press a key combination including CTRL and ALT_GR on a Swedish keyboard?













3















I pressed some combination of letters by mistake and part of my Python buffer got a purple background color (or magenta, fuschia, violet, orchid, depending on knowledge of colors).



Region of text turned purple



The only way I found to undo it is to restart Emacs. How can I undo it otherwise?










share|improve this question



















  • 2





    This looks like it could be a misfired secondary selection, though its color is yellow by default. Does clicking the left mouse button while holding Alt make it go away?

    – undercat
    Mar 31 at 14:49







  • 1





    You can use what-cursor-position C-u C-x = while cursor stay in the area. It will tell you what font face that area is using right now, then you can find out what feature you enabled.

    – Rangi Lin
    Mar 31 at 15:51















3















I pressed some combination of letters by mistake and part of my Python buffer got a purple background color (or magenta, fuschia, violet, orchid, depending on knowledge of colors).



Region of text turned purple



The only way I found to undo it is to restart Emacs. How can I undo it otherwise?










share|improve this question



















  • 2





    This looks like it could be a misfired secondary selection, though its color is yellow by default. Does clicking the left mouse button while holding Alt make it go away?

    – undercat
    Mar 31 at 14:49







  • 1





    You can use what-cursor-position C-u C-x = while cursor stay in the area. It will tell you what font face that area is using right now, then you can find out what feature you enabled.

    – Rangi Lin
    Mar 31 at 15:51













3












3








3








I pressed some combination of letters by mistake and part of my Python buffer got a purple background color (or magenta, fuschia, violet, orchid, depending on knowledge of colors).



Region of text turned purple



The only way I found to undo it is to restart Emacs. How can I undo it otherwise?










share|improve this question
















I pressed some combination of letters by mistake and part of my Python buffer got a purple background color (or magenta, fuschia, violet, orchid, depending on knowledge of colors).



Region of text turned purple



The only way I found to undo it is to restart Emacs. How can I undo it otherwise?







key-bindings






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 31 at 23:03









Drew

49k463108




49k463108










asked Mar 31 at 13:14









mmorinmmorin

2248




2248







  • 2





    This looks like it could be a misfired secondary selection, though its color is yellow by default. Does clicking the left mouse button while holding Alt make it go away?

    – undercat
    Mar 31 at 14:49







  • 1





    You can use what-cursor-position C-u C-x = while cursor stay in the area. It will tell you what font face that area is using right now, then you can find out what feature you enabled.

    – Rangi Lin
    Mar 31 at 15:51












  • 2





    This looks like it could be a misfired secondary selection, though its color is yellow by default. Does clicking the left mouse button while holding Alt make it go away?

    – undercat
    Mar 31 at 14:49







  • 1





    You can use what-cursor-position C-u C-x = while cursor stay in the area. It will tell you what font face that area is using right now, then you can find out what feature you enabled.

    – Rangi Lin
    Mar 31 at 15:51







2




2





This looks like it could be a misfired secondary selection, though its color is yellow by default. Does clicking the left mouse button while holding Alt make it go away?

– undercat
Mar 31 at 14:49






This looks like it could be a misfired secondary selection, though its color is yellow by default. Does clicking the left mouse button while holding Alt make it go away?

– undercat
Mar 31 at 14:49





1




1





You can use what-cursor-position C-u C-x = while cursor stay in the area. It will tell you what font face that area is using right now, then you can find out what feature you enabled.

– Rangi Lin
Mar 31 at 15:51





You can use what-cursor-position C-u C-x = while cursor stay in the area. It will tell you what font face that area is using right now, then you can find out what feature you enabled.

– Rangi Lin
Mar 31 at 15:51










3 Answers
3






active

oldest

votes


















6














There's too little information in the question to be sure, so I can't definitively answer what happened. Rather I'll show how to investigate this and give some plausible cases.




I pressed some combination of letters by mistake




Once you realize that, press F1 l or C-h l (that's lowercase ell) to invoke the command view-lossage. This displays the last 300 keys you pressed as well as other input events such as mouse clicks. Since Emacs 25, this also shows the commands that they invoked. In earlier versions, you have to use C-h k to find what command a key or key sequence invokes, and that can give wrong results if you've changed some setting or moved to some buffer since that event, or for mouse events if you click in a different place.



If Emacs is behaving strangely, check the mode line (the line just above the bottom line, or at the bottom of the current window, that displays information such as the file name and line number) and the minibuffer (the line at the bottom where commands prompt for input). Maybe you switched to the buffer while some command (e.g. a search) was in progress? If the mode indication in the mode line has square brackets around the parentheses (e.g. [(Python …)] instead of the normal (Python …)), it means that a recursive edit is in progress, i.e. some command lets you edit the buffer. To exit the recursive edit and resume the command that started it, press C-M-c. To exit the recursive edit and abort the command that started it, press C-] or ESC ESC ESC. If there's a prompt in the minibuffer, click there to switch back to that prompt.



If you want to know why a particular character is in a particular color or font, move the cursor to that character and run M-x describe-text-properties. This command is also available from the menu ‘Edit’ → ‘Text Properties’ → ‘Describe Properties’ or C-mouse-2 ‘Text Properties’ → ‘Describe Properties’. Typically text formatting is done through faces and the face's documentation should at least indicate which package is responsible for it.



The command M-x list-faces-display (available as ‘Display Faces’ in the ‘Text Properties’ menu) shows the available faces. With the default light background theme, two faces use a purple background that matches the image in your question: isearch and query-replace, both used to highlight matching text during a search command. I don't know how you could have reached that my mistake, but based on the colors, it's the most plausible scenario.



Emacs has a built-in package to highlight things temporarily. It leaves a discrete clue in the modeline: the minor mode indicator Hi.



Although anything could happen depending on what packages you have installed, highlighting is likely to be a per-buffer configuration. So if you can't figure out what's going on, it should be enough to close the file and reopen it.






share|improve this answer






























    0














    The face of the highlighted text could be face secondary-selection, although that has a yellow background by default.



    You can tell what the face is by putting your cursor on a highlighted character and hitting C-u C-x =. Near the bottom of buffer *Help* describing that character it tells you what face is used.



    If that's the case then you probably used the M- (Meta key) modifier while dragging the mouse with the first mouse button (<mouse-1>) pressed, and then released. (That makes the secondary selection empty.)



    To get rid of it just hold the Meta key and click <mouse-1> (without dragging it).



    (If this is in fact the answer then please add tags secondary-selection and mouse to the question.)






    share|improve this answer
































      0














      On second thought, I'm guessing that you used Isearch, query-replace or hi-lock. The default face for Isearch and query-replace, face isearch, looks just like the highlighting you show.



      Isearch highlighting appears when you search using C-s, C-r, C-M-s, or C-M-r. Query-replace highlighting appears when you use use M-% or C-M-%. Normally this search highlighting disappears when you're done with the command, but things can get "stuck".



      Hi-lock highlighting appears when you use a hi-lock command, such as hi-lock-line-face-buffer or hi-lock-face-buffer (aka highlight-regexp). Hi-lock commands are on prefix key C-x w, by default.



      Such commands either read a face name or automatically use the next face. If you previously used Isearch then the face chosen could easily be face isearch, which looks like what you show. Hi-lock highlighting persists after the command that causes the highlighting. My guess would be that you used hi-locking, perhaps without realizing it.



      If you see submenu Regexp Highlighting in the menu-bar Edit menu then hi-lock-mode is on, and this is probably the explanation.
      To get rid of hi-lock highlighting you can usually just turn off hi-lock-mode by repeating that toggle command.






      share|improve this answer

























        Your Answer








        StackExchange.ready(function()
        var channelOptions =
        tags: "".split(" "),
        id: "583"
        ;
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function()
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled)
        StackExchange.using("snippets", function()
        createEditor();
        );

        else
        createEditor();

        );

        function createEditor()
        StackExchange.prepareEditor(
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        imageUploader:
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        ,
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        );



        );













        draft saved

        draft discarded


















        StackExchange.ready(
        function ()
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f48676%2fhow-did-some-of-my-text-get-highlighted-with-a-magenta-background%23new-answer', 'question_page');

        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        6














        There's too little information in the question to be sure, so I can't definitively answer what happened. Rather I'll show how to investigate this and give some plausible cases.




        I pressed some combination of letters by mistake




        Once you realize that, press F1 l or C-h l (that's lowercase ell) to invoke the command view-lossage. This displays the last 300 keys you pressed as well as other input events such as mouse clicks. Since Emacs 25, this also shows the commands that they invoked. In earlier versions, you have to use C-h k to find what command a key or key sequence invokes, and that can give wrong results if you've changed some setting or moved to some buffer since that event, or for mouse events if you click in a different place.



        If Emacs is behaving strangely, check the mode line (the line just above the bottom line, or at the bottom of the current window, that displays information such as the file name and line number) and the minibuffer (the line at the bottom where commands prompt for input). Maybe you switched to the buffer while some command (e.g. a search) was in progress? If the mode indication in the mode line has square brackets around the parentheses (e.g. [(Python …)] instead of the normal (Python …)), it means that a recursive edit is in progress, i.e. some command lets you edit the buffer. To exit the recursive edit and resume the command that started it, press C-M-c. To exit the recursive edit and abort the command that started it, press C-] or ESC ESC ESC. If there's a prompt in the minibuffer, click there to switch back to that prompt.



        If you want to know why a particular character is in a particular color or font, move the cursor to that character and run M-x describe-text-properties. This command is also available from the menu ‘Edit’ → ‘Text Properties’ → ‘Describe Properties’ or C-mouse-2 ‘Text Properties’ → ‘Describe Properties’. Typically text formatting is done through faces and the face's documentation should at least indicate which package is responsible for it.



        The command M-x list-faces-display (available as ‘Display Faces’ in the ‘Text Properties’ menu) shows the available faces. With the default light background theme, two faces use a purple background that matches the image in your question: isearch and query-replace, both used to highlight matching text during a search command. I don't know how you could have reached that my mistake, but based on the colors, it's the most plausible scenario.



        Emacs has a built-in package to highlight things temporarily. It leaves a discrete clue in the modeline: the minor mode indicator Hi.



        Although anything could happen depending on what packages you have installed, highlighting is likely to be a per-buffer configuration. So if you can't figure out what's going on, it should be enough to close the file and reopen it.






        share|improve this answer



























          6














          There's too little information in the question to be sure, so I can't definitively answer what happened. Rather I'll show how to investigate this and give some plausible cases.




          I pressed some combination of letters by mistake




          Once you realize that, press F1 l or C-h l (that's lowercase ell) to invoke the command view-lossage. This displays the last 300 keys you pressed as well as other input events such as mouse clicks. Since Emacs 25, this also shows the commands that they invoked. In earlier versions, you have to use C-h k to find what command a key or key sequence invokes, and that can give wrong results if you've changed some setting or moved to some buffer since that event, or for mouse events if you click in a different place.



          If Emacs is behaving strangely, check the mode line (the line just above the bottom line, or at the bottom of the current window, that displays information such as the file name and line number) and the minibuffer (the line at the bottom where commands prompt for input). Maybe you switched to the buffer while some command (e.g. a search) was in progress? If the mode indication in the mode line has square brackets around the parentheses (e.g. [(Python …)] instead of the normal (Python …)), it means that a recursive edit is in progress, i.e. some command lets you edit the buffer. To exit the recursive edit and resume the command that started it, press C-M-c. To exit the recursive edit and abort the command that started it, press C-] or ESC ESC ESC. If there's a prompt in the minibuffer, click there to switch back to that prompt.



          If you want to know why a particular character is in a particular color or font, move the cursor to that character and run M-x describe-text-properties. This command is also available from the menu ‘Edit’ → ‘Text Properties’ → ‘Describe Properties’ or C-mouse-2 ‘Text Properties’ → ‘Describe Properties’. Typically text formatting is done through faces and the face's documentation should at least indicate which package is responsible for it.



          The command M-x list-faces-display (available as ‘Display Faces’ in the ‘Text Properties’ menu) shows the available faces. With the default light background theme, two faces use a purple background that matches the image in your question: isearch and query-replace, both used to highlight matching text during a search command. I don't know how you could have reached that my mistake, but based on the colors, it's the most plausible scenario.



          Emacs has a built-in package to highlight things temporarily. It leaves a discrete clue in the modeline: the minor mode indicator Hi.



          Although anything could happen depending on what packages you have installed, highlighting is likely to be a per-buffer configuration. So if you can't figure out what's going on, it should be enough to close the file and reopen it.






          share|improve this answer

























            6












            6








            6







            There's too little information in the question to be sure, so I can't definitively answer what happened. Rather I'll show how to investigate this and give some plausible cases.




            I pressed some combination of letters by mistake




            Once you realize that, press F1 l or C-h l (that's lowercase ell) to invoke the command view-lossage. This displays the last 300 keys you pressed as well as other input events such as mouse clicks. Since Emacs 25, this also shows the commands that they invoked. In earlier versions, you have to use C-h k to find what command a key or key sequence invokes, and that can give wrong results if you've changed some setting or moved to some buffer since that event, or for mouse events if you click in a different place.



            If Emacs is behaving strangely, check the mode line (the line just above the bottom line, or at the bottom of the current window, that displays information such as the file name and line number) and the minibuffer (the line at the bottom where commands prompt for input). Maybe you switched to the buffer while some command (e.g. a search) was in progress? If the mode indication in the mode line has square brackets around the parentheses (e.g. [(Python …)] instead of the normal (Python …)), it means that a recursive edit is in progress, i.e. some command lets you edit the buffer. To exit the recursive edit and resume the command that started it, press C-M-c. To exit the recursive edit and abort the command that started it, press C-] or ESC ESC ESC. If there's a prompt in the minibuffer, click there to switch back to that prompt.



            If you want to know why a particular character is in a particular color or font, move the cursor to that character and run M-x describe-text-properties. This command is also available from the menu ‘Edit’ → ‘Text Properties’ → ‘Describe Properties’ or C-mouse-2 ‘Text Properties’ → ‘Describe Properties’. Typically text formatting is done through faces and the face's documentation should at least indicate which package is responsible for it.



            The command M-x list-faces-display (available as ‘Display Faces’ in the ‘Text Properties’ menu) shows the available faces. With the default light background theme, two faces use a purple background that matches the image in your question: isearch and query-replace, both used to highlight matching text during a search command. I don't know how you could have reached that my mistake, but based on the colors, it's the most plausible scenario.



            Emacs has a built-in package to highlight things temporarily. It leaves a discrete clue in the modeline: the minor mode indicator Hi.



            Although anything could happen depending on what packages you have installed, highlighting is likely to be a per-buffer configuration. So if you can't figure out what's going on, it should be enough to close the file and reopen it.






            share|improve this answer













            There's too little information in the question to be sure, so I can't definitively answer what happened. Rather I'll show how to investigate this and give some plausible cases.




            I pressed some combination of letters by mistake




            Once you realize that, press F1 l or C-h l (that's lowercase ell) to invoke the command view-lossage. This displays the last 300 keys you pressed as well as other input events such as mouse clicks. Since Emacs 25, this also shows the commands that they invoked. In earlier versions, you have to use C-h k to find what command a key or key sequence invokes, and that can give wrong results if you've changed some setting or moved to some buffer since that event, or for mouse events if you click in a different place.



            If Emacs is behaving strangely, check the mode line (the line just above the bottom line, or at the bottom of the current window, that displays information such as the file name and line number) and the minibuffer (the line at the bottom where commands prompt for input). Maybe you switched to the buffer while some command (e.g. a search) was in progress? If the mode indication in the mode line has square brackets around the parentheses (e.g. [(Python …)] instead of the normal (Python …)), it means that a recursive edit is in progress, i.e. some command lets you edit the buffer. To exit the recursive edit and resume the command that started it, press C-M-c. To exit the recursive edit and abort the command that started it, press C-] or ESC ESC ESC. If there's a prompt in the minibuffer, click there to switch back to that prompt.



            If you want to know why a particular character is in a particular color or font, move the cursor to that character and run M-x describe-text-properties. This command is also available from the menu ‘Edit’ → ‘Text Properties’ → ‘Describe Properties’ or C-mouse-2 ‘Text Properties’ → ‘Describe Properties’. Typically text formatting is done through faces and the face's documentation should at least indicate which package is responsible for it.



            The command M-x list-faces-display (available as ‘Display Faces’ in the ‘Text Properties’ menu) shows the available faces. With the default light background theme, two faces use a purple background that matches the image in your question: isearch and query-replace, both used to highlight matching text during a search command. I don't know how you could have reached that my mistake, but based on the colors, it's the most plausible scenario.



            Emacs has a built-in package to highlight things temporarily. It leaves a discrete clue in the modeline: the minor mode indicator Hi.



            Although anything could happen depending on what packages you have installed, highlighting is likely to be a per-buffer configuration. So if you can't figure out what's going on, it should be enough to close the file and reopen it.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Mar 31 at 18:48









            GillesGilles

            13.7k43575




            13.7k43575





















                0














                The face of the highlighted text could be face secondary-selection, although that has a yellow background by default.



                You can tell what the face is by putting your cursor on a highlighted character and hitting C-u C-x =. Near the bottom of buffer *Help* describing that character it tells you what face is used.



                If that's the case then you probably used the M- (Meta key) modifier while dragging the mouse with the first mouse button (<mouse-1>) pressed, and then released. (That makes the secondary selection empty.)



                To get rid of it just hold the Meta key and click <mouse-1> (without dragging it).



                (If this is in fact the answer then please add tags secondary-selection and mouse to the question.)






                share|improve this answer





























                  0














                  The face of the highlighted text could be face secondary-selection, although that has a yellow background by default.



                  You can tell what the face is by putting your cursor on a highlighted character and hitting C-u C-x =. Near the bottom of buffer *Help* describing that character it tells you what face is used.



                  If that's the case then you probably used the M- (Meta key) modifier while dragging the mouse with the first mouse button (<mouse-1>) pressed, and then released. (That makes the secondary selection empty.)



                  To get rid of it just hold the Meta key and click <mouse-1> (without dragging it).



                  (If this is in fact the answer then please add tags secondary-selection and mouse to the question.)






                  share|improve this answer



























                    0












                    0








                    0







                    The face of the highlighted text could be face secondary-selection, although that has a yellow background by default.



                    You can tell what the face is by putting your cursor on a highlighted character and hitting C-u C-x =. Near the bottom of buffer *Help* describing that character it tells you what face is used.



                    If that's the case then you probably used the M- (Meta key) modifier while dragging the mouse with the first mouse button (<mouse-1>) pressed, and then released. (That makes the secondary selection empty.)



                    To get rid of it just hold the Meta key and click <mouse-1> (without dragging it).



                    (If this is in fact the answer then please add tags secondary-selection and mouse to the question.)






                    share|improve this answer















                    The face of the highlighted text could be face secondary-selection, although that has a yellow background by default.



                    You can tell what the face is by putting your cursor on a highlighted character and hitting C-u C-x =. Near the bottom of buffer *Help* describing that character it tells you what face is used.



                    If that's the case then you probably used the M- (Meta key) modifier while dragging the mouse with the first mouse button (<mouse-1>) pressed, and then released. (That makes the secondary selection empty.)



                    To get rid of it just hold the Meta key and click <mouse-1> (without dragging it).



                    (If this is in fact the answer then please add tags secondary-selection and mouse to the question.)







                    share|improve this answer














                    share|improve this answer



                    share|improve this answer








                    edited Mar 31 at 23:15

























                    answered Mar 31 at 22:57









                    DrewDrew

                    49k463108




                    49k463108





















                        0














                        On second thought, I'm guessing that you used Isearch, query-replace or hi-lock. The default face for Isearch and query-replace, face isearch, looks just like the highlighting you show.



                        Isearch highlighting appears when you search using C-s, C-r, C-M-s, or C-M-r. Query-replace highlighting appears when you use use M-% or C-M-%. Normally this search highlighting disappears when you're done with the command, but things can get "stuck".



                        Hi-lock highlighting appears when you use a hi-lock command, such as hi-lock-line-face-buffer or hi-lock-face-buffer (aka highlight-regexp). Hi-lock commands are on prefix key C-x w, by default.



                        Such commands either read a face name or automatically use the next face. If you previously used Isearch then the face chosen could easily be face isearch, which looks like what you show. Hi-lock highlighting persists after the command that causes the highlighting. My guess would be that you used hi-locking, perhaps without realizing it.



                        If you see submenu Regexp Highlighting in the menu-bar Edit menu then hi-lock-mode is on, and this is probably the explanation.
                        To get rid of hi-lock highlighting you can usually just turn off hi-lock-mode by repeating that toggle command.






                        share|improve this answer





























                          0














                          On second thought, I'm guessing that you used Isearch, query-replace or hi-lock. The default face for Isearch and query-replace, face isearch, looks just like the highlighting you show.



                          Isearch highlighting appears when you search using C-s, C-r, C-M-s, or C-M-r. Query-replace highlighting appears when you use use M-% or C-M-%. Normally this search highlighting disappears when you're done with the command, but things can get "stuck".



                          Hi-lock highlighting appears when you use a hi-lock command, such as hi-lock-line-face-buffer or hi-lock-face-buffer (aka highlight-regexp). Hi-lock commands are on prefix key C-x w, by default.



                          Such commands either read a face name or automatically use the next face. If you previously used Isearch then the face chosen could easily be face isearch, which looks like what you show. Hi-lock highlighting persists after the command that causes the highlighting. My guess would be that you used hi-locking, perhaps without realizing it.



                          If you see submenu Regexp Highlighting in the menu-bar Edit menu then hi-lock-mode is on, and this is probably the explanation.
                          To get rid of hi-lock highlighting you can usually just turn off hi-lock-mode by repeating that toggle command.






                          share|improve this answer



























                            0












                            0








                            0







                            On second thought, I'm guessing that you used Isearch, query-replace or hi-lock. The default face for Isearch and query-replace, face isearch, looks just like the highlighting you show.



                            Isearch highlighting appears when you search using C-s, C-r, C-M-s, or C-M-r. Query-replace highlighting appears when you use use M-% or C-M-%. Normally this search highlighting disappears when you're done with the command, but things can get "stuck".



                            Hi-lock highlighting appears when you use a hi-lock command, such as hi-lock-line-face-buffer or hi-lock-face-buffer (aka highlight-regexp). Hi-lock commands are on prefix key C-x w, by default.



                            Such commands either read a face name or automatically use the next face. If you previously used Isearch then the face chosen could easily be face isearch, which looks like what you show. Hi-lock highlighting persists after the command that causes the highlighting. My guess would be that you used hi-locking, perhaps without realizing it.



                            If you see submenu Regexp Highlighting in the menu-bar Edit menu then hi-lock-mode is on, and this is probably the explanation.
                            To get rid of hi-lock highlighting you can usually just turn off hi-lock-mode by repeating that toggle command.






                            share|improve this answer















                            On second thought, I'm guessing that you used Isearch, query-replace or hi-lock. The default face for Isearch and query-replace, face isearch, looks just like the highlighting you show.



                            Isearch highlighting appears when you search using C-s, C-r, C-M-s, or C-M-r. Query-replace highlighting appears when you use use M-% or C-M-%. Normally this search highlighting disappears when you're done with the command, but things can get "stuck".



                            Hi-lock highlighting appears when you use a hi-lock command, such as hi-lock-line-face-buffer or hi-lock-face-buffer (aka highlight-regexp). Hi-lock commands are on prefix key C-x w, by default.



                            Such commands either read a face name or automatically use the next face. If you previously used Isearch then the face chosen could easily be face isearch, which looks like what you show. Hi-lock highlighting persists after the command that causes the highlighting. My guess would be that you used hi-locking, perhaps without realizing it.



                            If you see submenu Regexp Highlighting in the menu-bar Edit menu then hi-lock-mode is on, and this is probably the explanation.
                            To get rid of hi-lock highlighting you can usually just turn off hi-lock-mode by repeating that toggle command.







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Mar 31 at 23:20

























                            answered Mar 31 at 23:06









                            DrewDrew

                            49k463108




                            49k463108



























                                draft saved

                                draft discarded
















































                                Thanks for contributing an answer to Emacs Stack Exchange!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid


                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.

                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function ()
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2femacs.stackexchange.com%2fquestions%2f48676%2fhow-did-some-of-my-text-get-highlighted-with-a-magenta-background%23new-answer', 'question_page');

                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                Adding axes to figuresAdding axes labels to LaTeX figuresLaTeX equivalent of ConTeXt buffersRotate a node but not its content: the case of the ellipse decorationHow to define the default vertical distance between nodes?TikZ scaling graphic and adjust node position and keep font sizeNumerical conditional within tikz keys?adding axes to shapesAlign axes across subfiguresAdding figures with a certain orderLine up nested tikz enviroments or how to get rid of themAdding axes labels to LaTeX figures

                                Luettelo Yhdysvaltain laivaston lentotukialuksista Lähteet | Navigointivalikko

                                Gary (muusikko) Sisällysluettelo Historia | Rockin' High | Lähteet | Aiheesta muualla | NavigointivalikkoInfobox OKTuomas "Gary" Keskinen Ancaran kitaristiksiProjekti Rockin' High