Re: Create and edit new scripts

Replies are listed 'Best First'.
Re^2: Create and edit new scripts by wazoox (Prior) on Apr 25, 2006 at 19:07 UTC
I use nedit too and a very similar macro (bind to ctrl+shift+P :) However may I suggest that you'd better use `use warnings;` [download] rather than `#!/usr/bin/perl -w` [download] which has the undesirable side-effect to enable warnings in modules you use, and some really can't stand it (CGI.pm for instance). BTW here's my macro, which uses "which" to determine the path to perl : `set_language_mode( "Perl" ) myperl=shell_command( "which perl" , "" ) insert_string("#!" myperl "\n\nuse strict;\nuse warnings;\n") set_cursor_pos(100)` [download]	[reply] [d/l] [select]
Re^3: Create and edit new scripts by arkturuz (Curate) on Apr 26, 2006 at 07:47 UTC
I have the same binding :-) Thanx for the suggestion! I use '-w' because I want all the warnings in most of the programs I write. Some of them are CGI apps, and I like them to run clearly.	[reply]
Re^2: Create and edit new scripts by johngg (Canon) on Apr 25, 2006 at 15:20 UTC
I don't know whether you have had this issue with nedit. If I create a new script from within the editor and save it without closing the edit session and then `chmod +x` it in the shell I can run it. If I make further changes to the script and save them I can no longer run the script as the permissions revert to `rw-r--r--` after the save. If I create the file outside of nedit with execute permissions and then start editing, nedit doesn't trample on the permissions during the edit/save/test/edit ... cycle. This was one of the reasons for writing "newscript". Thank you for your reply, it has given me useful pointers to how I can better use nedit. Cheers, JohnGG	[reply] [d/l] [select]
Re^3: Create and edit new scripts by arkturuz (Curate) on Apr 26, 2006 at 07:42 UTC
I hadn't have this problem. It works OK for me on Linux system. Although, when I run the program from nedit I run it with (binded to Ctrl+Shift+E): `chmod +x %; %` [download] '%' stands for current editing file.	[reply] [d/l]


more useful options
	PerlMonks