Re: Reducing KODRETRY
Joseph Tam <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Message-ID | <[email protected]> |
Egad, this thread has turned into a shell war, something I didn't envision. I still really didn't get an answer to my first question (whether reducing KODRETRY was harmful), but it looks like it was superceded by better solutions. Steven W. Orr <[email protected]> writes: > The history of why you were duped into using csh/tcsh/whatevercsh goes > back to the early days of SunOS when Sun made the csh the default shell > for their boxes. Read the whynot. Learn bash. Love it. csh's should all > simply be deleted. You could say that about a lot of software. But user habits die hard. This isn't the first time I found csh lacking, but on the whole, I get done what I want to get done. If had to do it all over again, I'd start with some sh variant with some good history editing. From: Thorsten Glaser <[email protected]> writes: > There's mksh, which IS actively developed, focuses on > good script using (instead of interactive, but NOT leaving > the interactive aspect away, e.g. recently, UTF-8 support > was improved), is MUCH faster, MUCH LESS bloated, and can > do _more_ things than GNU bash (e.g. co-routines). > Besides, it's freely licenced, not under the restrictive GPL. Judging from a web page I saw on mksh and the name of the Debian mainainer, you're not exactly impartial, are you? http://packages.debian.org/unstable/shells/mksh > #!/bin/sh > if pgrep pine >/dev/null 2>&1; then > echo "Pine is already running!" > exit 1 > else > exec pine "$@" > fi You probably have to do at least two other things: - narrow search to a particular user since this won't work on a multi-user machine with hundreds of users running pine: pgrep -U $USER ... - allow the ability to force the running of pine regardless of whether you can get the lock since you have users who leave pine logged in at the office, then go home and run pine. Anyways, thanks to all for the contributions: good grists for the mill. Joseph Tam <[email protected]> _______________________________________________ Pine-info mailing list [email protected] http://mailman1.u.washington.edu/mailman/listinfo/pine-info