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
Related
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.
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.
Is there any description of a diff/patch format visualization algorithm? (or maybe it is too trivial to be described)
The Rietveld code review tool has a lot of comments explaining its operation in its source code. Take particular notice of intra_regiion_diff.py and engine.py.
What diff tools produce as data is pretty basic: "this line changed that way".
"Visualizing" that normally consists of showing the original code and the modified code side by side, with the "this line changed" indicated by marking the display text somehow. Basically this means scrollable text windows with painted stripes of text. Fancy versions will paint lines between the changed line in one window, and it corresponding line in another.
I'm using guidelines right now, but I do not think there is any way to disable them for certain projects (my project with tests).
In general, how do you reconcile long, descriptive test method names with a line length limit for non-test code (both of which I think are good)? If you feel the same way and have solved this, what solution do you use?
Drop the line length policy.
If you still want to insist on keeping track of the column, try adding the following to the registry if your using Visual Studio
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Text Editor] "Guides"="RGB(192,192,192) 110"
RGB of course controls the color of the line, and you may change 110 to whatever number you like.
The end result gives you a guide line in Visual Studio so you always know where the column is, and the IDE ends up looking like this:
alt text http://blogs.msdn.com/photos/shawnfa/images/659277/637x480.aspx
We accomplish it by dropping the line length limit for all our projects that are not developed in a 1980s green screen environment. We instead use the full power of our 21st century high resolution LCD displays, bitmap screen modes and powerful IDEs to make source code that is descriptive and easy to maintain, rather then designed to fit into the screen and memory footprint of a machine whose RAM is measured in KBs.
(And then we beat the guy advocating line length limits and 3 letter variable names with a pointy stick)
Can't agree with the other answers that long lines are not an issue. You wouldn't say it's comfortable to read a minified single-line .js file - even with the horizontal scroll bars!
Visual Studio has an extension for adding visual hints - Editor Guidelines. You can manually create guidelines wherever you like - 80 or 120 characters. It does not enforce line lengths, so you are still free to deviate where you think it's appropriate.
I am in the process of writing a text editor. After looking at other text editors I have noticed that a number of them refer to a "soft" versus "hard" wrap. What is the difference? I can't seem to find the answer by searching.
A hard wrap inserts actual line breaks in the text at wrap points, with soft wrapping the actual text is still on the same line but looks like it's divided into several lines.
It's usual for text editors to auto-wrap text into paragraphs with hard newlines, but it's less common for the text to be re-flowed into a nice paragraph if you come back later and edit/add/remove words later on. (You can do this manually in emacs with M-q.)
This is rather annoying, since obsessive compulsive people like me then go back and have to manually re-insert the hard breaks at the appropriate points.
On the other hand, soft wrapping is annoying because most all command line tools use line-based diff-ing (version control is where this becomes most noticeable to me). If you've got a 1/3-page paragraph that's soft wrapped and fix a typo, it's basically impossible to see where the change is in a regular diff output or similar.
soft : The text in the textarea is not wrapped when submitted in a form. This is default
hard : The text in the textarea is wrapped (contains newlines) when submitted in a form. When "hard" is used, the cols attribute must be specified
Reference: W3Schools