NppExec v0.6 beta 1 has been realeased!



  • NppExec v0.6 beta 1 has been realeased!

    Here is some brief info about NppExec for new users:
    * NppExec adds a Console window at the bottom of Notepad++'s window;
    This Console window allows to run different console programs directly in it;
    Also there is Plugins -> NppExec -> Execute… window that allows to execute NppExec’s scripts (set of commands).
    * NppExec’s commands and variables are listed in the “NppExec.txt” file.
    * To get more details, type “help” (without the quotes) directly in NppExec’s Console. To get a detailed help about any NppExec’s command, type “help <command>” - e.g. “help npp_open” or “help set”.
    And don’t forget about Plugins -> NppExec -> Help/Manual.

    What’s new in NppExec v0.6 beta 1:
    * changed: now the Execute dialog’s auto-completion pop-up uses the same upper/lower case as the first character of a word being typed (e.g. Npp -> NPP…; npp -> npp…);
    also: now the auto-completion pop-up’s height is limited by the number of its items
    + new commands: SCI_FIND, SCI_REPLACE
    + new commands: TEXT_SAVETO, TEXT_LOADFROM
    + Function Parser has been updated to support the bitwise operators: ~, |, &, << and >> (thanks to Juha Nieminen and Joel Yliluoma for their advice)
    + $(LAST_CMD_RESULT) - result of the last NppExec’s command (1 - succeeded, 0 - failed, -1 - invalid arg)
    - fixed: parameters of sci_sendmsg/npp_sendmsg were truncated to 32-bit in 64-bit NppExec
    - fixed: now pasting to the Console via Shift+Insert is equal to Ctrl+V

    Download link: https://sourceforge.net/projects/npp-plugins/files/NppExec/NppExec Plugin v0.6 beta 1/

    Kind of dev diary (from v0.6 alpha dev to v0.6 beta 1): https://sourceforge.net/p/npp-plugins/discussion/672146/thread/20b09c96/

    P.S.
    Today is a sad day in Ukraine, it is dedicated to the memory of the Heavenly Hundred ( https://en.wikipedia.org/wiki/List_of_people_killed_during_Euromaidan ).
    And still nothing is over. Our men and even women are still continuing to risk their lives in the East of Ukraine. They are real heroes there.



  • Thanks, @Vitaliy-Dovgan !!

    This is one of the more useful plug-ins, in my humble opinion.



  • Thanks!
    By the way, the file “NppExec_06beta1_dll_x64.zip” has been re-uploaded - initially it did not include the “NppExec” subfolder which is used by the NppExec plugin to read its constants (such as SCI_… and NPPM_… messages and so on).



  • From now, NppExec’s sources are available on GitHub:
    https://github.com/d0vgan/nppexec



  • Why does NppExec drop a bunch of files in my ...\plugins\doc\ folder?
    Messy.
    Why not put these files into ...\plugins\doc\NppExec\ after the style of other plugins…at least the ones I use that put stuff in the “doc” folder?

    These files are left “floating around”:

    • fparser.html
    • NppExec.txt
    • NppExec_Manual.chm
    • NppExec_TechInfo.txt
    • ScintillaDoc.html
    • style.css

    Actually I wasn’t quite sure all of these files belonged to NppExec (I mean, some obvously do…) until I went to try out this new version and noticed them in the zip file.

    Anyway, anxious to try it out, especially the search and replace functionality alluded to here…thanks!



  • I did not know that other plugins use a subfolder under the “doc” folder to place there documentation there.
    The idea is nice, anyway. Will do it that way.



  • After reading this other thread and following some of the links over to the sourceforge discussion, I was surprised to learn that my NppExec was so far out of date. Looking at my portable NPP 64bit, the Plugin Manager lists 0.6 (beta1) as the most recent and available. But in my main 32bit Notepad++ install, the Plugin Manager still shows NppExec 0.5.3 as the most recent available. If you want people to use the newest NppExec, you might want to also tell the 32bit Plugin Manager about the updated version.



  • The 64bit version I updated to the latest one as no older stable one is available. If 0.6 beta1 is considered to be stable also the 32bit version could be updated. What do you think @Vitaliy-Dovgan ?



  • Yes, I think the version of the 32-bit one can be updated as well.
    I remember I was registered at the original 32-bit Plugin Manager site, where the plugin descriptions are present. Is it still relevant? If so, I just need to find my old credentials there, to be able to update the information.



  • @Vitaliy-Dovgan Could you try to login at https://npppm.bruderste.in/users/login. If you don’t find your login I could also do the update as it could take some time to get in contact with dave to renew the login.



  • Info at the npppm has been updated - now let’s wait for the Plugin Manager to pick it up.



  • @Vitaliy-Dovgan : Nice to hear! :)

    But it seems like the 32-Bit Plugin Admin System at https://npppm.bruderste.in has a malfunction again. For example the PluginManager itself was released as v1.4.11 at March 13th but in the plugin list it still displays the release infos of its v1.4.9. The current version is only available via development plugin list.



  • That is not a malfunction, but a feature. There is a 2 week time schedule to take over the changes from the dev list to the official list to allow for beta testing before going live.



  • Hopefully the schedule is still working. There is a 2 week time schedule to take over the changes from the dev list to the official list to allow for beta testing before going live. PM was build on 2018-03-13, but added to the 32bit list on 2018-03-29 after some testing with the 64bit. So maybe still on the schedule as merge is done on Monday to my knowledge.



  • @chcg
    I rolled back to PluginManager v1.4.9 and it didn’t offer v1.4.10. Or was this version not published via Plugin Admin System?

    @Vitaliy-Dovgan
    The version info of NppExec’s DLL file states that it is v0.6.0. The version info in the Plugin Admin System is set to v0.6.0.1. Therefore the offer to update the plugin doesn’t disappear.



  • @dinkumoil Checkback with Dave Brotherstone showed that the server was not working as expected. The missing sync happened and the 2 week schedule is in place again.


Log in to reply