v0.2 RC3 - January 2008
-----------------------
+ search in the Console
+ history in the Console Filters dialog
+ several issues fixed
+ several cosmetic improvements
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v0.2 RC3.1 - February 2008
--------------------------
- fixed: buffer overflow in the Warning Analyzer
* changed: now NPP_RUN calls ShellExecute() instead of WinExec()
Things which have not been implemented:
1) No scrolling while adding new lines into the Console Output window. I was not able to find the solution for this. It requires more time and aspiration than I have.
2) Word-wrap in the Console Output window. Requires the word-wrap function which is not the one of my interest.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for this version, but there is a big problem, indeed if I use
npp_run notepad $(FULL_CURRENT_PATH)
it was working good before, but now it is not working while npp_run notepad is ok
The pb is on XP SP2 and vista
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, yes. ShellExecute() requres more "tender" handling than WinExec() ;-)
Now I have to separate the argument of NPP_RUN manually - because ShellExecute() expects an executable name ("notepad.exe") and its parameters ("$(FULL_CURRENT_PATH)") as two different arguments.
Will be done in RC3.2 (I think).
Meantime you can use just
npp_run "$(FULL_CURRENT_PATH)"
It will open the current file in its associated program.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would like to be able to use perl debugger within your plugin. But is seems not possible to transfer/get stdin/stdout messages. Is it possible to have this in future?
For test download Perl Active and start a small hello world script with "perl -d helloworld.pl".
Best Regards
Jens
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
c:\perl\bin\perl.exe -d C:\Perl\eg\example.pl
Process started >>>
The system cannot find the path specified.
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work. The resize program didn't work. at c:/perl/lib/Term/ReadKey.pm line 362.
Compilation failed in require at c:/perl/lib/Term/ReadLine/Perl.pm line 64.
at c:/perl/lib/Term/ReadLine/Perl.pm line 64
Term::ReadLine::Perl::new('Term::ReadLine', 'perldb', 'GLOB(0x18dd2ec)', 'GLOB(0x1880a9c)') called at c:/perl/lib/perl5db.pl line 5998
DB::setterm called at c:/perl/lib/perl5db.pl line 2227
DB::DB called at C:\Perl\eg\example.pl line 1
Attempt to reload Term/ReadLine/readline.pm aborted.
Compilation failed in require at c:/perl/lib/Term/ReadLine/Perl.pm line 64.
END failed--call queue aborted at C:\Perl\eg\example.pl line 64.
at C:\Perl\eg\example.pl line 64
<<< Process finished.
As you can see, Perl says "Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work". It seems Perl requires a real console terminal. Whereas NppExec does not have a real console screen or something similar - it just uses pipes to redirect the child process'es output (and input).
So, you must call Perl in its own console screen:
But it will not work in NppExec v0.2 RC3.1 due to "features" of ShellExecute() which is called by NPP_RUN. The NPP_RUN command works correctly in NppExec v. 0.2 RC3 and will work correctly in v0.2 RC3.2 (coming soon).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v0.2 RC3 - January 2008
-----------------------
+ search in the Console
+ history in the Console Filters dialog
+ several issues fixed
+ several cosmetic improvements
v0.2 RC3.2 - February 2008
--------------------------
- fixed: NPP_RUN (ShellExecute) did not work with several arguments
v0.2 RC3.1 - February 2008
--------------------------
- fixed: buffer overflow in the Warning Analyzer
* changed: now NPP_RUN calls ShellExecute() instead of WinExec()
Things which have not been implemented:
1) No scrolling while adding new lines into the Console Output window. I was not able to find the solution for this. It requires more time and aspiration than I have.
2) Word-wrap in the Console Output window. Requires the word-wrap function which is not the one of my interest.
Hi
Thanks for this version, but there is a big problem, indeed if I use
npp_run notepad $(FULL_CURRENT_PATH)
it was working good before, but now it is not working while npp_run notepad is ok
The pb is on XP SP2 and vista
Thanks
What about
npp_run notepad.exe "$(FULL_CURRENT_PATH)"
?
it is not working
Thanks dv__ for shellexecute. Works fine now with associated program.
Rog
Well, yes. ShellExecute() requres more "tender" handling than WinExec() ;-)
Now I have to separate the argument of NPP_RUN manually - because ShellExecute() expects an executable name ("notepad.exe") and its parameters ("$(FULL_CURRENT_PATH)") as two different arguments.
Will be done in RC3.2 (I think).
Meantime you can use just
npp_run "$(FULL_CURRENT_PATH)"
It will open the current file in its associated program.
Hi DV,
I would like to be able to use perl debugger within your plugin. But is seems not possible to transfer/get stdin/stdout messages. Is it possible to have this in future?
For test download Perl Active and start a small hello world script with "perl -d helloworld.pl".
Best Regards
Jens
That's what I get:
c:\perl\bin\perl.exe -d C:\Perl\eg\example.pl
Process started >>>
The system cannot find the path specified.
Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work. The resize program didn't work. at c:/perl/lib/Term/ReadKey.pm line 362.
Compilation failed in require at c:/perl/lib/Term/ReadLine/Perl.pm line 64.
at c:/perl/lib/Term/ReadLine/Perl.pm line 64
Term::ReadLine::Perl::new('Term::ReadLine', 'perldb', 'GLOB(0x18dd2ec)', 'GLOB(0x1880a9c)') called at c:/perl/lib/perl5db.pl line 5998
DB::setterm called at c:/perl/lib/perl5db.pl line 2227
DB::DB called at C:\Perl\eg\example.pl line 1
Attempt to reload Term/ReadLine/readline.pm aborted.
Compilation failed in require at c:/perl/lib/Term/ReadLine/Perl.pm line 64.
END failed--call queue aborted at C:\Perl\eg\example.pl line 64.
at C:\Perl\eg\example.pl line 64
<<< Process finished.
As you can see, Perl says "Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work". It seems Perl requires a real console terminal. Whereas NppExec does not have a real console screen or something similar - it just uses pipes to redirect the child process'es output (and input).
So, you must call Perl in its own console screen:
NPP_RUN c:\perl\bin\perl.exe -d C:\Perl\eg\example.pl
But it will not work in NppExec v0.2 RC3.1 due to "features" of ShellExecute() which is called by NPP_RUN. The NPP_RUN command works correctly in NppExec v. 0.2 RC3 and will work correctly in v0.2 RC3.2 (coming soon).