Re: Reducing KODRETRY

Ryan Barrett dixit:

> i've used tcsh as my interactive shell for a long time. i prefer it due to a
> few features, mostly in its line editor, that give it the edge over bash for

Interesting. I didn't try tcsh, only csh, because it came with
the operating system by default...

> i have no problem using one shell for scripting and another for
> interactive, though.

I think, personally, it's more consistent to have only one,
because interactive use and scripting is pretty much the same,
but I can imagine other people have different needs. But if
you're like this...

> sure, when i have to write non-trivial shell scripts, i turn to bash.

... definitively look at mksh.

> use the best tool for the job (and for you), right?

Agreed. Some people want to "evangelise" and forget that there
is no such thing as a "one size fits all" tool.

But back to the problem... I don't speak (t)csh scripting,
but you could write a small wrapper around pine:

% cat >/usr/local/bin/pinewrapper
#!/bin/sh
if pgrep pine >/dev/null 2>&1; then
	echo "Pine is already running!"
	exit 1
else
	exec pine "$@"
fi
^D

Then use the "alias" function which, incidentally, originated
in csh if I remember correctly, to alias pine to pinewrapper.

And look at the mbx stuff.

bye,
//mirabile
-- 
  "Using Lynx is like wearing a really good pair of shades: cuts out
   the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL."
                                         -- Henry Nelson, March 1999
_______________________________________________
Pine-info mailing list
[email protected]
http://mailman1.u.washington.edu/mailman/listinfo/pine-info