On 2007-05-24 10:28:35 -0500, David Champion wrote:
> PATH_SEPARATOR does not exist in a Bourne shell. It may be POSIX, but
> only a few shells are indeed POSIX; whereas the convention for calling a
> shell script does not specify POSIX shells, only /bin/sh.
PATH_SEPARATOR is user code only. Not
#2894: mutt dumps core when opening a not existent imap mailbox.
Mutt was configured with:
{{{
./configure --prefix=$HOME/freebsd --enable-smtp --enable-imap \
--with-ssl=/usr --with-libiconv-prefix=/usr/local \
--with-qdbm=$HOME/freebsd --enable-inodesort --enable-hca
On Thu, May 24, 2007 at 07:57:45 +0100, David Laight wrote:
> Except that &> isn't posix-compliant shell syntax (it is from csh), and
> isn't supported by all shells.
Except that some standard (i.e. #!/bin/sh) shells are _not_ POSIX, such
as on Solaris. That was already mentioned somewhere else in
On Fri, May 25, 2007 at 11:24:19AM +0200, Vincent Lefevre wrote:
> On 2007-05-24 10:28:35 -0500, David Champion wrote:
> > PATH_SEPARATOR does not exist in a Bourne shell. It may be POSIX, but
> > only a few shells are indeed POSIX; whereas the convention for calling a
> > shell script does not sp
