Does anybody know where this line and the grey area to the right of it comes from?
If it's just a bug, feel free to close this question!
That line is there to give you an impression on how long your lines should be. It's good practice to keep your code within a certain width, so its readable on different resolutions.
That is the Page Guide.
You can disable it here...
By unchecking this...
You can also change the distance that it shows.
It's there to show where your code would wrap on a standard 80 character width terminal.
Related
I have started to use tmux and noticed that the lines that seperate the different panes are not entirely straight, instead there are small bumps. I think it might have something to do with the font, my thought is that characters from one "character-field" are overlapping into the next, which creates the little bumps. Does anyone know how I can fix this and get a straight line without bumps?
The font I use: Menlo
example of the bumpy lines
The problem was actually the terminal emulator I used, Alacritty, which lets some characters reach outside of their cell. To solve this issue, I switched to Kitty, which has better support for preventing characters from overflowing into other cells.
In this screenshot of my vimrc settings, I have installed the plugin vim-airline using vundle. After going through airlines docs, I found the set of lines to customise my airline.
The problem is the ones highlighted in red. The blue highlighted one works fine but the red one does not. The left one is same as right one. I tried using different Unicode symbols but does not work. Any workaround to this situation as this is troubling my OCD :P.
Thanks in advance.
This is a well-known issue related to the font (size and family) used in your terminal.
For a better display, you have two solutions:
Do not use arrows as separators
Configure your terminal emulator to use a patched font with the right size
If you prefer the first solution, make sure you have this code in your .vimrc:
let g:airline_right_sep = ""
let g:airline_left_sep = ""
If you prefer the other solution, take a look at this: https://github.com/powerline/fonts
I have used the Hack font with size 11 for a long time and the arrows are perfectly displayed in my editor...
Using Atom Editor, I can change the position of the vertical margin from
File > Settings > Preferred Line Length
Is there a way to add multiple margins?
You can if you install the omni-ruler plugin.
I'm amazed as how dificult is for everyone to understand the problem.
Being a "stack overflow" user, you would expect to find many user with experience on the problem of working with [fixed-width-fields] text files.
is not a text file with a long line.
is data contained in those lines, that need to be make easier for human eye to check.
that being said, the besto solution so far fo me is:
https://www.ultraedit.com/support/tutorials-power-tips/ultraedit/column-markers.html
I've spent like an hour tying to find a way to fix this, but I just can't do it. Some lines/characters will show up a different color in Aptana (all semicolons, some tabs, and some whole). I just installed it today, so I don't know my way around the software very well.
Here's a picture to help you get the idea:
I would like get rid of the way some sections are lighter (the line saying some text is the line the caret's on, which is not the problem)
P.S. If this is the wrong place to ask this, I'm sorry, but I'm getting frustrated searching through Google and the Aptana preferences.
I too spent way too much time on this issue.
The answer by phazei is correct:
Aptana 3, php code background highlighting
But my main problem was I didn't know where to look. So to give some insight into how I found the answer:
It turns out you can see what markup the editor is using and how it classifies any block of text, by just right-clicking on the text you are interested in and pick Show in -> Properties.
I have text objects on a Crystal Report in Visual Studio with an initial capital. When I print the report, the text is all lower case.
And the reason is?
We have found a workaround for this problem. Not sure how this works :) - can any expert explain?
We found that this problem of case change was happening whenever the extent of text within any page / section of the report was going beyond the settings of the page size minus gutter, left/right margins, top/bottom margins set for the report.
As a workaround, we have asked all our reports developers to keep the text (for A4 size reports) to within 7.5 inches X 7.5 inches. The problem does not happen when this is adhered to.
Would definitely like to know exact reasons for the misbehavior though.
This might be affecting by some of the settings.
But if you go and edit the field , you can see it automatically change to lowercase.
If you agains change it back your case, then it will work fine.
It looks like it happend for one time. To be honest, I don't know why this happend