Feature Request - Toggle Line Numbers
-
This post is deleted! -
I added this comment to Issue #10762:
Only somewhat tangentially,
- promoting line number to a first class per-file attribute that persists across sessions is clearly not a priority, and this is understandable, however…
- double clicking on the line number column presently does nothing (different than single-clicking) so it seems to me that toggling line numbers visibility (thus sometimes overriding the Settings-Preferences directive) on a per-file but non-persistent basis by double-click should be “almost free” to code. When I say “almost free” I mean: no anguish over cluttering up any options dialogs; no extensions to session xml; and almost no need to document since folks nowadays will often double-click or right-click on a visual element just to see what happens; … which in turn suggests …
- Somewhat nicer still would be a right-click pop-up menu “Toggle line nums for this file” item
-
@Neil-Schipper said in Feature Request - Toggle Line Numbers:
double clicking on the line number column
OK, so double-clicking on the line number column will cause it to disappear, and to get it to reappear just what exactly do I double-click on??
-
@Alan-Kilborn Persistent skinny margin.
-
@Neil-Schipper said in Feature Request - Toggle Line Numbers:
Persistent skinny margin.
I see. So the line number margin is always visually available, just when it is “logically hidden” it still has some minimum visual component to allow restoration. I suppose if it is very minimal then it is hard to hit to restore it, but if it isn’t very minimal it doesn’t really achieve the goal of being hidden. Maybe as long as numbers aren’t visible the goal is achieved.
-
@Neil-Schipper Neil, thank you and all that replied. and thank you for the FAQ link. I see you have added suggestions to #10762, if that is sufficient for the issue, then that’s good for me.
I understand features are added based on a user-support type system, and I’ve seen that in other projects as well. It has merit, but I agree that for smaller, specific features such as a line number toggle, it is unlikely that it will generate sufficient vote interest. (not much sex-appeal from a feature standpoint)
That is where the user-support (vote) system has its weakness. Many features are just those that are expected in any editor, the type where any one of the nuts-and-bolts features are unlikely to receive many “popular” votes for addition. That doesn’t mean the feature shouldn’t be added, moreover just that basic features are not the type that end up at the top of a users wish-list.
If you think it would be helpful for me to follow the FAQ further to put the issue before the developers, let me know and I’m happy to do it. Thanks again to all that replied. -
Really, one could just use the script I linked to before and stop all the discussion. It works, end of story.
One of the main points of scripting is giving you control over things so you don’t have to wait for developers to agree that what you want is worth it, then wait even longer for then to code, document and release it.
-
@Alan-Kilborn I installed PythonScript plugin. That really isn’t an efficient solution. Installing a 20M plugin just to toggle line-numbers on/off seem a bit overkill. (not to mention the additional vulnerability from having yet another part of npp automatically pulled from github - and being python - the recent Pypy attack is a reminder that isn’t always a good idea)
-
@drankinatty,
The other option is to write your own plugin, or wait until one of the developers thinks it’s important enough to make part of the codebase.
There are always going to be “attacks” by malcontents. Your only true option to avoid this type of problem is to get a Smith Corona to do your text editing. Then you can control everything with no need for code. -
@drankinatty said in Feature Request - Toggle Line Numbers:
I installed PythonScript plugin. That really isn’t an efficient solution. Installing a 20M plugin just to toggle line-numbers on/off seem a bit overkill.
I really can’t conversate rationally with someone that is going to complain about a 20MB usage in today’s world.
(not to mention the additional vulnerability from having yet another part of npp automatically pulled from github - and being python - the recent Pypy attack is a reminder that isn’t always a good idea)
Another irrational point – go with Smith Corona, as suggested?
We’re just N++ users here, attempting to point out ways in which you can obtain your desired functionality right this instant. Often these ways involve some sort of compromise on your part. Your alternative is to just go on missing the feature you are missing.