I've been using vs2013 for quite some time and noticed something that is quite bothering me.
In the Code Editor, lines that contain nothing but symbols (such as '{', '/' '*' etc..) have a different line‑height / font‑size than other lines that also contain letters.
I search through the settings and couldn't find a way to turn this behavior off.
My question is if there's a way to turn this behavior off, and have consistent line heights throughout my entire code.
You probably have Productivity Power Tools installed with Syntactic line compression enabled. You can turn it off in VS Options - Productivity Power Tools - Other Extensions.
For the VS2019 it is quite similar to the provided solutions:
Tools -> Options-> Productiviry Power Tools -> General
Under "Syntatic line compression options"
you uncheck:
"Compress lines that does not have any alphanumeric characters" like {,[ and so on
You also can uncheck
"Compress blank lines" but this will be only for lines without anything in it.
Related
I hope this is okay to ask on SO, I'm not sure. I apologize if it shouldn't be here.
I reinstalled Visual Studio Professional 2015 yesterday due to a few issues I was having. With the new installation, my line numbers have a very wide section where the mouse reverses direction and select the entire line if clicked. I don't recall this area being so wide on any of my previous installations of VS2015; I know it was there in the first place. Is there a way to disable this?
This is the area where this happens, boxed in green. It's much wider than the line numbers fill (only 147 lines in this file).
There are two "margins" available in Visual Studio 2015: Selection and Indicator available under Tools > Options > Text Editor > General > Display. Turning these off remove some, but not all of the "extra space" and the feature of highlighting an entire line is still there.
If you want to turn them off because the extra space is bothersome, keep in mind you will not be able to see breakpoints unless "highlight current line" is checked.
I am having a problem with visual studio not displaying line numbers despite having checked "Line numbers" in Tools -> Options. I have included a pic with proof, and all the solutions I have found don't answer this. How can I enable line number, despite already having enabled it?
http://imgur.com/7cmfqcZ
You don't have it enabled for all languages - the square means that it's enabled for some languages, but obviously not the one you care about.
Just click the check box twice - the first will remove it for all languages, the second will select it for all languages.
The blue box in the checkbox for line numbering in the All Languages group means that line numbering is language-dependent.
Either put a tick there (to enable line numbering for all languages), or in the C/C++ - specific line numbering option (to enable line numbering for C/C++).
Is there any way to make xcode highlight operators(".","<>", "()", ";", etc) differently, like it is possible in Visual Studio? It really improves the readability of the code.
There's no such option in the preferences but maybe there's some way to edit coloring file directly and make these symbols appear as reserved words? It's ok if the color is blue, like it is for reserved words - as long as it's not the same color as the generic text. I tried googling a plug-in with this functionality, but couldn't find it. It doesn't seem like there are many xcode plug-ins out there.
Try to edit /Applications/Xcode.app/Contents/OtherFrameworks/DeoolsCore.framework/Versions/A/Resources/Built-in languages.pblangspec by adding your operators as keywords.
Does anybody know a light plug-in that do (same as Resharper) go to implementation and the quick search for a file where you just insert few characters and it shows the matches? I just want to get rid of Resharper cause it slows me down a lot!!
To answer the original question, as per this post by Andrew Arnott, you can use Ctrl+/ to move the cursor to the Find text box in the toolbar, then type ">of" and start typing file names. The matching files will appear as you type.
Using the ">" prefix causes the find text box to act as the command window would.
(Note that the Ctrl+/ short-cut may be overridden by ReSharper to comment a line of code, so this short-cut only works with ReSharper uninstalled.)
That's interesting. I use ReSharper and it uses about 400mb of RAM. I would consider that pretty low usage.
Maybe you can look into Productivity Power Tools (I don't use it).
http://visualstudiogallery.msdn.microsoft.com/d0d33361-18e2-46c0-8ff2-4adea1e34fef/
Situation
I have a plain text file where indentation is important.
line 1
line 1.1 (indented two spaces)
line 1.2 (indented two spaces)
line 1.2.3 (indented four spaces)
In Visual Studio 2008, when I pressed enter, the next line would also be indented four spaces.
However, in Visual Studio 2010, when I press enter, the next line is indented one tab.
Question
Does anybody know where, in the mountain of preferences under Tools > Options, I can return to the way that Visual Studio 2008 worked?
Under Options > Text Editor > Plain Text > Tabs, I see the following:
If I select "None", then I get no indentation when I move to the next line. If I select "Block", then I get TAB indentation (even though the previous line is spaces).
In Visual Studio 2008, my indentation is set to "Block", and I get spaces.
I have no idea what "Smart" indenting is, or why it is disabled.
"Smart" indenting is essentially asking the language service to do indentation, which covers cases like adding an extra indent level after an { in C# files. Since plain text files don't have a language service, it isn't available here. If it was, the behavior (matching indentation from the line above) would be whatever the language decides to do, though I'm pretty certain it respects the "Insert spaces"/"Keeps tabs" option.
"Block" indenting is asking the editor to take care of it, which it takes to mean "maintain the same indent level as the previous line". It appears that, in VS2008, it copied the indentation from the previous line, whereas VS2010 respects the "Insert spaces"/"Keep tabs" setting.
Can you file a bug on Connect about it? I'm not sure if it was changed on purpose or not, so it will help for this to go to our (the editor team's) triage people to make sure.