So I'm coding in VIM, and I ran into a strange problem. I closed out of my source code, but when I opened it back up, a lot of my curly brackets are highlighted in yellow, and I can't seem to fix it. The closing brackets are matched up with opening brackets, so I don't see what the issue is.
Here is a picture of the problem:
How can I fix this?
Did you do a search for the closing bracket?
Try the following, in command mode
:set nohlsearch
You can use :noh to turn off highlighting of previously searched term.
You can do set nohl that will turn off the highlighting for the session. Reopening will highlight again.
To fix that, search anything that you don't like, for instance /""
Related
I have no idea what on earth has happened to my VSCode. I am unable to trace which or exactly what extension caused this. But, the C++ syntax coloring and theme looks absolutely ugly.
I want this,
How can I get that back? I am unable to figure this out. I uninstalled all C/C++ extensions and still the issue remains.
VSCode colorizes brackets and parentheses to make it easier to see which opening bracket belongs to which closing bracket.
You can turn it off in the settings:
I get this functionality by default with WebStorm. On clicking a closing bracket, it temporarily displays the line with the opening bracket on top of the editor (if the line is not within the viewport) and hides it when I click somewhere else. I don't have to jump to the matching opening bracket to see it.
I have no idea what this functionality is called and I looked up many possibilities and couldn't find anything. Please help!
I have code that looks like
'.Parameters.Add("p_Date", OracleClient.OracleType.DateTime).Value
or
.Parameters.Add("p_Date", OracleClient.OracleType.DateTime).Value
The only difference is that one is commented and the other is not.
I want to search for all code in my project that aren't commented so I can focus on that
I don't mind downloading an IDE that you're familiar with to help me ONLY find those lines that are NOT commented.
Using Notepad++
The simplest way is to find with Regular expression checked.
(?<!')\.Parameters\.Add\("p_Date", OracleClient\.OracleType\.DateTime\)\.Value.*$
or
(?<!')\.Parameters\.Add.*$
To filter lines that don't begin with cmd., add (?<!cmd) before \.Parameters, so the regex becomes:
(?<!')(?<!cmd)\.Parameters\.Add.*$
Just now I was working on a fancy search and replace regular expression.
It looked good so I tested it on one entry then went to the editing area and the search and replace box went away.
I reopened the search and replace box to continue, but the selected text in the edit window replaced my search expression.
Control Z in the search box did not go back to my regex but undid the last change in the editing area.
I can't seem to find a way to get back to previous regexes in the find box. Is there any way? Googling turned up nothing.
Currently, Adobe Brackets doesn't maintain any kind of history of search and replace expressions. The feature is still missing.
Enter this in a file:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Hello
A
Hello
B
And then search for this using /:
\(Hello\n\)\#<=A
On my version of Vim (7.4, included patches: 1-582), the A underneath Hello is matched as expected, B is not, but also the 446th A on the first line is matched.
There is also some weird behaviour with this, if I make the line longer with more As, the 632nd A is highlighted. If I introduce 16 spaces at the beginning of the line, the 447th and the 632nd characters on the line are matched.
My question is, does this affect anyone else, and is it really a bug or is my search erroneous?
Yes, this looks like a bug. I can reproduce with Vim 7.4.608, but only with the default :set regexpengine=0 automatic selection.
To avoid the problem, you can either change the global option, or explicitly specify an engine inside the pattern:
\%#=1\(Hello\n\)\#<=A
\%#=2\(Hello\n\)\#<=A
Please report this bug, either to the vim_dev mailing list, or its issue tracker.