Comments don't work?



  • I might know what was causing the problem. I have been using a custom language definition for UnityScript (a version of Javascript) that was created by the Unity3D community 6 or 7 years ago. When I did the clean install, I removed all my old settings, including that custom language. I’ve been using this updated / clean version for several hours and so far no issues. I can’t think of any other reason why I would have problems while no one else seems to.



  • 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.



  • 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.



  • @Finley-Dabinett

    Tested it - I do not have that behavior.
    Must be something else.

    Cheers
    Claudia



  • @Alan-Kilborn

    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. ;-)

    Cheers
    Claudia



  • @Claudia-Frank

    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!



  • @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.



  • No, there is no shortcut conflict. If Ctrl+K is assigned to nothing, it will go back to it’s extremely ancient mapping, which is VT (char 11, 0x0B). Just like Ctrl+J is LF, Ctrl+M is CR, Ctrl+H is BS, and Ctrl+I is TAB.

    (Ctrl+M, Ctrl+H and Ctrl+I all behave just like their ENTER, BACKSPACE, and TAB key equivalents in something like cmd.exe)


Log in to reply