$(#N) doesn't always evaluate correctly in NppExec 0.62 DLL dated 2021.06.21 about nppexec

[d0vgan]

Should be fixed in f675e55

[artie-finkelstein]

Thank you for the heads up. I'll gladly test it after the next 32 bit DLL is released.

…

On 7/12/21, Vitaliy Dovgan ***@***.***> wrote: Should be fixed in f675e55 -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #44 (comment)

[d0vgan]

https://community.notepad-plus-plus.org/topic/21365/nppexec-latest-development-version/5

[artie-finkelstein]

Sorry for the slow reply. There was a local lightning strike that took out my phone & internet service for the day. The NppExec 0.699 works very nicely. The direct and indirect referencing to $(#) works as desired now. I do have a question- What do the various new 'local' attribute additions let me accomplish that I couldn't without them? Is it really just allowing me to not have to clean up after myself in the closing lines of a script? Of course, now that I write that, it occurs to me that I would no longer have to maintain a common 'known good state' and always return to it at the end of each script. Am I underselling or undervaluing these new attributes and therefore missing a bigger picture? Thank you for the fix to $(#).

…

On 7/19/21, Vitaliy Dovgan ***@***.***> wrote: https://community.notepad-plus-plus.org/topic/21365/nppexec-latest-development-version/5 -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #44 (comment)

[d0vgan]

The idea of the "local" keyword has two main effects in mind:

1. ability to automatically return to the previous state, whatever it was;
2. no need of manual clean-up.
   As an example, let's consider a command "npe_console -- m- v+". It disables the Console's "internal" messages (in green) and enables the $(OUTPUT) variable. To do the opposite, you may execute another command "npe_console -- m+ v-" later. The question is : what was the original state of "m" and "v" before the first command "npe_console -- m- v+" has been executed? Maybe the "internal" messages were already disabled and/or the $(OUTPUT) variable was already enabled before executing "npe_console -- m- v+" ? In such case, executing "npe_console -- m+ v-" later, we will actually change the state of "m" and "v" comparing to how it was before the first command. And here is when "npe_console local -- m- v+" comes in handy: it guarantees that the state of "m" and "v" will be reverted exactly to their previous values.

[artie-finkelstein]

Thank you for that very clear explanation. And THANK YOU for creating the most useful Npp plugin.

…

On 7/20/21, Vitaliy Dovgan ***@***.***> wrote: The idea of the "local" keyword has two main effects in mind: 1) ability to automatically return to the previous state, whatever it was; 2) no need of manual clean-up. As an example, let's consider a command "npe_console -- m- v+". It disables the Console's "internal" messages (in green) and enables the $(OUTPUT) variable. To do the opposite, you may execute another command "npe_console -- m+ v-" later. The question is : what was the original state of "m" and "v" before the first command "npe_console -- m- v+" has been executed? Maybe the "internal" messages were already disabled and/or the $(OUTPUT) variable was already enabled before executing "npe_console -- m- v+" ? In such case, executing "npe_console -- m+ v-" later, we will actually change the state of "m" and "v" comparing to how it was before the first command. And here is when "npe_console local -- m- v+" comes in handy: it guarantees that the state of "m" and "v" will be reverted exactly to their previous values. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #44 (comment)

[artie-finkelstein]

Oops. I forgot to come here to close the issue earlier. Mea culpea.