Re: scripting gnuclient and emacs for mutt [ was: emacsclient -nw]

2003-11-21 Thread Matt Price
On Thu, Nov 20, 2003 at 10:56:01AM -0600, Lucas Bergman wrote: > Matt Price <[EMAIL PROTECTED]> writes: > > > David Z Maze wrote: > > > > is it possible in bash to test whether a comand has actually worked? > > The '||' operator does this, like: > > #!/bin/sh > gnuclient "$@" || xemacs -noma

Re: scripting gnuclient and emacs for mutt [ was: emacsclient -nw]

2003-11-20 Thread Lucas Bergman
Matt Price <[EMAIL PROTECTED]> writes: > David Z Maze wrote: > > > See earlier commentary about XEmacs; gnuclient(1) is the XEmacs > > equivalent to emacsclient, and it does claim to support a -nw > > option. I could see things being unhappy if you set $EDITOR to > > that, but it's easy enough to

Re: scripting gnuclient and emacs for mutt [ was: emacsclient -nw]

2003-11-20 Thread Matt Price
On Thu, Nov 20, 2003 at 04:29:39PM +, Colin Watson wrote: > On Thu, Nov 20, 2003 at 10:49:45AM -0500, Matt Price wrote: > > is it possible in bash to test whether a comand has actually worked? > > I feel like I've seen such tests, but I tried one and can't make it > > work for me: > > > > #!

Re: scripting gnuclient and emacs for mutt [ was: emacsclient -nw]

2003-11-20 Thread Colin Watson
On Thu, Nov 20, 2003 at 10:49:45AM -0500, Matt Price wrote: > is it possible in bash to test whether a comand has actually worked? > I feel like I've seen such tests, but I tried one and can't make it > work for me: > > #! /bin/bash > if [ 'gnuclient -q $*' ]; then That's definitely wrong: 'gnu

scripting gnuclient and emacs for mutt [ was: emacsclient -nw]

2003-11-20 Thread Matt Price
On Wed, Nov 19, 2003 at 02:54:48PM -0500, David Z Maze wrote: > Matt Price <[EMAIL PROTECTED]> writes: > > While this doesn't help your actual problem, you should probably be > aware that 'emacs' and 'xemacs' are separate programs, either of which > can run in X or not in X. ('xemacs -nw' works;