drieux <[EMAIL PROTECTED]> writes:
> Under *nix files I kept a similar trick where I had a shell
> script fork up an xterm window with vi taking a template file...
> { but I do not recommend that strategy }
Along these lines. I use a perl script called `skel' to start a
script in any of several interpreters. It uses some home grown cmdline
processing to allow flags like `skel -[abks] filename'to start an
executable (it sets permissions on the file) awk ksh, bash, sh script.
Called with no flag it defaults to perl. Inside the script the path
to those various interpreters is found with `which perl (or
whatever)'.
The script assumes a unix/linux platform.
So in brief, `skel' starts the script with the appropropiate
interpreter path, sets the file executable and loads it in vim with
the cursor ready to type one line below the interpreter path.
It does save quite a bit of time if you write lots of scripts.
Especially when you need a quicky to check something in a more
complex one before adding it.
Its posted here, but its not very polished, and contains some
unfinished stuff where I started to code for emacs as a choice of
editors but never finished. Currently it will start perl (default)
awk, bash, or ksh scripts
http://www.jtan.com/~reader/exp/scripts
In fact, if any of the sharpshooters here feel like taking the time
to look at it, I could use all the criticisms you notice.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
