Community

    • Login
    • Search
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    NppExec: npp command resulting in error message in scripts

    Plugin Development
    3
    5
    144
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Domi M
      Domi M last edited by

      If I run “NPP_SAVE” in a script, an error message is generated (file is saved, anyway). “NPP_SAVE” directly typed in the console is working correctly.
      8e6d7f1a-6294-438c-b519-1cff8b11546b-grafik.png

      Does anyone know, how to resolve this? (maybe a missing setting or sth. else?)

      I’m running NPP v. 7.8.9 64-bit on Windows 10.

      Ekopalypse 1 Reply Last reply Reply Quote 0
      • Ekopalypse
        Ekopalypse @Domi M last edited by

        @domi-m

        I assume something after NPP_SAVE is the cause.
        I would insert echo statements to see where exactly it is failing.
        It must have something to do with the " ".

        Vitalii Dovgan 1 Reply Last reply Reply Quote 3
        • Vitalii Dovgan
          Vitalii Dovgan @Ekopalypse last edited by

          While processing commands, NppExec removes the leading and trailing spaces ( ’ ’ also known as ‘\x20’ ) and tabs ( ‘\t’ also known as ‘\x09’ ).
          In this situation, the next line after NPP_SAVE most likely contains some whitespace-like character that looks like a space but has a character code different from 0x20 and 0x09.

          Vitalii Dovgan Domi M 2 Replies Last reply Reply Quote 4
          • Vitalii Dovgan
            Vitalii Dovgan @Vitalii Dovgan last edited by

            This can be investigated locally by adding npe_debug local 1 right above the line with NPP_SAVE. It will print all the details of how NppExec executes the given commands and it will be possible to see the command item responsible for the “empty” command.

            1 Reply Last reply Reply Quote 5
            • Domi M
              Domi M @Vitalii Dovgan last edited by

              @vitalii-dovgan Yes, that was the issue, a whitespace-like character in the next line.

              Thank you!

              1 Reply Last reply Reply Quote 3
              • First post
                Last post
              Copyright © 2014 NodeBB Forums | Contributors