Re: Error messages

2000-12-14 Thread Josh Huber
On Thu, Dec 14, 2000 at 06:27:54PM +0200, Peter Pentchev wrote: > I dare you to name a relatively-modern version of csh, tcsh, bash, ksh > or zsh, which does not have test/[ as a builtin ;) Ok, you got me there. I'm sure they all have this as a builtin, but was that at least the historical reaso

Re: Error messages

2000-12-14 Thread Peter Pentchev
On Thu, Dec 14, 2000 at 11:12:48AM -0500, Josh Huber wrote: > On Thu, Dec 14, 2000 at 07:37:47AM -0800, David Alban wrote: > > Of course, this would be O.K. I prefer the [[ ]] operator (found in > > ksh and bash 2.x) because it is smarter and more resistant to syntax > > errors that occur with [

Re: Error messages

2000-12-14 Thread Josh Huber
On Thu, Dec 14, 2000 at 07:37:47AM -0800, David Alban wrote: > Of course, this would be O.K. I prefer the [[ ]] operator (found in > ksh and bash 2.x) because it is smarter and more resistant to syntax > errors that occur with [ ] if a variable is undefined. But > certainly one can use [ ] and

Re: Error messages

2000-12-14 Thread David Alban
Peter, At 2000/12/14/12:19 +0200 Peter Pentchev <[EMAIL PROTECTED]> wrote: > Just a side note - is there a reason you could not use the standard '[' > test operator? Along with some quoting of possibly-null arguments, of > course.. something like: > > [ -n "$1" ] && muttrc="$1" > > [ ! -e "$mu

Re: Error messages

2000-12-14 Thread Peter Pentchev
On Wed, Dec 13, 2000 at 06:12:43PM -0800, David Alban wrote: > Greetings! > > At 2000/12/13/18:58 -0600 David Champion <[EMAIL PROTECTED]> wrote: > > You mean just to test the muttrc file and report parse errors? > > > > How about: > > mutt -F test.muttrc -f /dev/null -e "push x" >/dev/null

Re: Error messages

2000-12-13 Thread David Alban
Greetings! At 2000/12/13/18:58 -0600 David Champion <[EMAIL PROTECTED]> wrote: > You mean just to test the muttrc file and report parse errors? > > How about: > mutt -F test.muttrc -f /dev/null -e "push x" >/dev/null That's *way* cool! Here's a script[1] which uses your idea to test $1 i

Re: Error messages

2000-12-13 Thread David Champion
On 2000.12.13, in <[EMAIL PROTECTED]>, "Charles Curley" <[EMAIL PROTECTED]> wrote: > When working on my .muttrc, it would be very nice if there were some way > to see error messages generated by bugs in the .muttrc. Is there any such > mechanism? You mean just to test the muttrc file and