v0.3.2 - September 2009
-----------------------
+ new feature: TAB autocompletes file paths (in the Console)
(* thanks to ILme for initial implementation)
+ new feature: Shift+Tab (in the Console, the same as TAB but backwards)
- fixed: 'cd \path', 'dir \path' did not jump to the root of current drive
- fixed: on-exit script was not executed
+ new command: NPE_CMDALIAS
+ new menu item: Disable command aliases
+ new option in NPE_CONSOLE: q+/q-
Have got two shells opened in Npp, one should be static, and one should follow the current file path.
Issue: even though at the 'static' one the "Follow $(CURRENT_DIRECTORY)" is NOT checked, it follows the current file when cycle to the other shell and back again to the static one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Follow $(CURRENT_DIRECTORY)" uses the SetCurrentDirectory() function which is applied to the whole Notepad++ application. So, indeed, it affects another NppExec's Console(s). This may be unexpected behaviour, but not a bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v0.3.2 - September 2009
-----------------------
+ new feature: TAB autocompletes file paths (in the Console)
(* thanks to ILme for initial implementation)
+ new feature: Shift+Tab (in the Console, the same as TAB but backwards)
- fixed: 'cd \path', 'dir \path' did not jump to the root of current drive
- fixed: on-exit script was not executed
+ new command: NPE_CMDALIAS
+ new menu item: Disable command aliases
+ new option in NPE_CONSOLE: q+/q-
https://sourceforge.net/projects/npp-plugins/files/
Bug foud:
Have got two shells opened in Npp, one should be static, and one should follow the current file path.
Issue: even though at the 'static' one the "Follow $(CURRENT_DIRECTORY)" is NOT checked, it follows the current file when cycle to the other shell and back again to the static one.
"Follow $(CURRENT_DIRECTORY)" uses the SetCurrentDirectory() function which is applied to the whole Notepad++ application. So, indeed, it affects another NppExec's Console(s). This may be unexpected behaviour, but not a bug.