I need to do a simple thing at first glance - add a bar with line numbers to CKEditor. The main idea is a writer can refer to a particular paragraph while discussing the text.
I have tried to find a plugin, tried to find an another WYSIWYG editor with line numbers but no success.
Does anybody know any solution for CKEditor or another one that already has line numbering?
Or the only I can do is to write it from scratch?
Thanks!
I implemented it from scratch. When it will be possible I'm going to improve it. There are some issues and limitations now.
Link to repository.
Instead you can use the Codemirror plugin as well to get the Line numbers which includes search and replace as well.
Related
i just noticed the line spacing are always the same, and was wondering if there's a magic way to use one paragraphy style to realize this layout? Thanks in advance
i tried the settings of paragraph style but still dont know how it works.
The new structure guide lines in VS2017 are extremely confusing, as they are positioned in the middle of a character, instead of to the left. The biggest problem is that I don't know when my cursor is ALL the way to the left, as it seems to be when it is standing on the grid line, but it may off by one.
How can I change them to look more like Visual Code? I know how to enable and disable them but can't find any way to alter their looks.
No guide lines in VS2017: This does not help me much.
With guide lines in VS2017: This is awful, it looks like there is just 1 space between two guide lines, when in fact there are two!
Guide lines in Visual Code: Very helpful.
Finally found this plugin, which fixes the main off-by-one problem and works for VS2017. See below for a screenshot of the indent guides added by the plugin.
The plugin is customizable, such that you can get a solid line if preferred.
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.
What is the best way to hack away a bug in GTK+? The bug in https://bugzilla.gnome.org/show_bug.cgi?id=127840 is irritating and I would like to see a working version of it. But there is just so many lines of code so how can I find the correct part of the code? I'm using DDD.
In this case you know it's a bug in the text view, so you'd look at gtk+/gtk/gtktextview.c and then start following the source out to other related files.
This particular bug is essentially unfixable though. Each paragraph is rendered as a single PangoLayout and PangoLayout doesn't really support processing only part of a single paragraph.
The best fix might be in GEdit to throw an error or insert line breaks or something.