Comments don't work?
PeterJones last edited by
If you’re interested in further debug (and I won’t be offended if you aren’t), you could try just installing that one plugin, and see if it really is the culprit. If you’re not interested, I’m at least glad it seems to be working for you. Enjoy.
Unfortunately, I spoke too soon. After not running into any issues after the fresh install yesterday, today when I started it back up I can’t use the CTRL-Q toggle to comment / un-comment. Same issue as before. :( Here’s the contents of the debug window:
Notepad++ v7.3.1 (64-bit)
Build time : Jan 17 2017 - 00:28:43
Path : C:\Program Files\Notepad++\notepad++.exe
Admin mode : OFF
Local Conf mode : OFF
OS : Windows 7
Plugins : mimeTools.dll NppConverter.dll
I’ve just installed Notepad++ version 6.0 to see if it works any better than the newer versions. As I posted at the beginning of this thread, I’ve been using Notepad++ without issues for years and only started seeing this issue when I updated last year.
Finley Dabinett last edited by
I believe it has something to do with auto-reloaded files. What I mean by this is, when you open notepad++ then open a file, the commenting feature works fine. But if you keep that file open and close the notepad++ program then relaunch it, the file will be automatically open, and that is when the commenting does not work. But, if you re-open the file, it will work again.
So basically, files that are opened on launch of the notepad++ application have some issue with commenting using the shortcut.
Claudia Frank last edited by
Tested it - I do not have that behavior.
Must be something else.
Claudia Frank last edited by Claudia Frank
So I have not seen much of a need for these “comment” commands:
To be honest - I use ctrl-k (and shift+ctrl+k) exclusively.
If you are at the position where you can put in a hash ( to stay with the python example) then
yes, of course, it would be quicker, but I’m almost never at that position.
Am I missing the value here?
No, it’s just not implemented - but as said, I don’t care I just have to remember two shortcuts,
well, not true, three shortcuts (I use toggle comment often also). Single line un-/comment and
toggle line comment. They work for blocks as well. ;-)
Alan Kilborn last edited by
Your statements make a lot of sense. I think I understand now. I have been using the ‘toggle’ shortcut key since I saw your reply and I LIKE IT. I think I was wanting the “block” version of the command to work, but since the toggle works for single lines or blocks I can just ignore (not use) the block version. Many thanks!
Larry Bell last edited by
@Finley-Dabinett I agree. That is the behavior I am having too. In addition, I changed my mapping for Single Line Comment to another key combination and now my CTRL+K puts a VT in a black box on the page. So there is probably a conflict somewhere even though the mapper says there isn’t any conflicts.
PeterJones last edited by PeterJones
No, there is no shortcut conflict. If
Ctrl+Kis assigned to nothing, it will go back to it’s extremely ancient mapping, which is
VT(char 11, 0x0B). Just like
Ctrl+Iall behave just like their ENTER, BACKSPACE, and TAB key equivalents in something like
Dennis Paroutsas last edited by Dennis Paroutsas
I found my way around it. I just created two new shortcuts, like this:
- First, I hilighted a whole line.
- Then started recording a new “Macro”.
- I cutted the line to the clipboard (ctrl-x).
- Then i printed two slashes “//”.
- Then i pasted the cutted line again (ctrl-v).
- Then paused recording, assinged the shorcut Alt-A (so it can be eazy with my left hand)
Now when I press “alt-A” comments any line i want.
I also did the same for block of lines. (Highlight the block, cut it, type “/*”+enter, paste in again, type “*/”+enter, save with Alt-Q, and that’s it!!!
Alan Kilborn last edited by
It does work, but it isn’t (and can’t be) language aware.
Thus if you always program in C-style languages you are all set.
But if you code in several different languages you’d have to have different macros and different keycombos that invoke them.
And, you have to highlight a line (or a block) before running the macro. It’s arguably easier to just press
/and achieve the same thing, with no follow-on caret positioning needed.