v0.2.5 release 2 - September 2008
---------------------------------
- fixed: (potential) bug in CNppExec::DoExecScript()
- fixed: several (potential) bugs, thanks to Patrick Corwin
I.e. this is the same NppExec v0.2.5 except several fixed bugs.
This is an ANSI (non-Unicode) version so far, which is compatible with old versions of Notepad++ and new ANSI build of Notepad++ (non-Unicode).
To build the Unicode version of NppExec, some enhancement are required. It will be done in next NppExec's release. Future versions of NppExec will be completely Unicode-compatible.
Please suggest the implementation of the pipe redirection '>' and '<'.
You see, if you start cmd.exe and type, for example, "awk.exe >awk.txt", the the awk's output will be redirected to "awk.txt". However, if you type the same "awk.exe >awk.txt" in the NppExec's Console, it will call CreateProcess which will understand " >awk.txt" as a command line arguments and WILL NOT redirect the output to "awk.txt". Thus, we need our own implementation of the redirection mechanism. And this is not a thing which could be done quickly.
Regarding the combo-box history for $(INPUT), here is what I think: you can call some script several times, but with different parameters as $(INPUT): some times it coud be $(FULL_CURRENT_PATH), sometimes it could be another full file path and so on. And sometimes you would like to use the same parameter as you use some time ago: $(FULL_CURRENT_PATH) again or some previously entered full file path. As your script does not know anything about the values you used, these values are stored as a history in combo-box of the $(INPUT) to allow you to select these values again in the drop-down list instead of typing them again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
is it possible to implement a new feature? I miss in your plugin a "pipe" function and a box where you can choose one of the piped element. I would like love to see following supported command:
// initilize input
$(INPUT) < dir "C:\" - sets $(INPUT) with element of root folder C:
// open inputbox and select an item means, that every combo entry has one folder like "Program Files", "Windows"
inputbox "Choose an item:"
// After OK (about does nothing)
set selected = $(INPUT[SEL])
I know this is not currently your concept of inputbox. But my imagine of an inputbox differs a lot from your implementation. Combo shows the history of INPUT values, for what do you use it. Normally you can store you most prefered values in a script.
Best Regards
Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v0.2.5 release 2 - September 2008
---------------------------------
- fixed: (potential) bug in CNppExec::DoExecScript()
- fixed: several (potential) bugs, thanks to Patrick Corwin
I.e. this is the same NppExec v0.2.5 except several fixed bugs.
This is an ANSI (non-Unicode) version so far, which is compatible with old versions of Notepad++ and new ANSI build of Notepad++ (non-Unicode).
To build the Unicode version of NppExec, some enhancement are required. It will be done in next NppExec's release. Future versions of NppExec will be completely Unicode-compatible.
Plugins download link:
https://sourceforge.net/project/showfiles.php?group_id=189927
Please suggest the implementation of the pipe redirection '>' and '<'.
You see, if you start cmd.exe and type, for example, "awk.exe >awk.txt", the the awk's output will be redirected to "awk.txt". However, if you type the same "awk.exe >awk.txt" in the NppExec's Console, it will call CreateProcess which will understand " >awk.txt" as a command line arguments and WILL NOT redirect the output to "awk.txt". Thus, we need our own implementation of the redirection mechanism. And this is not a thing which could be done quickly.
Regarding the combo-box history for $(INPUT), here is what I think: you can call some script several times, but with different parameters as $(INPUT): some times it coud be $(FULL_CURRENT_PATH), sometimes it could be another full file path and so on. And sometimes you would like to use the same parameter as you use some time ago: $(FULL_CURRENT_PATH) again or some previously entered full file path. As your script does not know anything about the values you used, these values are stored as a history in combo-box of the $(INPUT) to allow you to select these values again in the drop-down list instead of typing them again.
I think another bug...:
- Execute-Window: When I "save" f.e.
fpc "$(FULL_CURRENT_PATH)"
as "FreePascalComp"
then I write "test xy" an push "OK" ->
"test xy" overwrites my saved "FreePascalComp"
Regards
Thomas
No, you can modify your scripts at any time. The modifications will be saved automatically.
Hi DV,
is it possible to implement a new feature? I miss in your plugin a "pipe" function and a box where you can choose one of the piped element. I would like love to see following supported command:
// initilize input
$(INPUT) < dir "C:\" - sets $(INPUT) with element of root folder C:
// open inputbox and select an item means, that every combo entry has one folder like "Program Files", "Windows"
inputbox "Choose an item:"
// After OK (about does nothing)
set selected = $(INPUT[SEL])
I know this is not currently your concept of inputbox. But my imagine of an inputbox differs a lot from your implementation. Combo shows the history of INPUT values, for what do you use it. Normally you can store you most prefered values in a script.
Best Regards
Jens