Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Sun, 25 Feb 2001 17:45:24 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.1.8: Mutt can't spawn editor or shell Message-ID: <20010225174524.A10383@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20010225103047.30132.qmail@web11607.mail.yahoo.com> <20010225225025.B27406@cygbert.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010225225025.B27406@cygbert.vinschen.de>; from cygwin@cygwin.com on Sun, Feb 25, 2001 at 10:50:25PM +0100 On Sun, Feb 25, 2001 at 10:50:25PM +0100, Corinna Vinschen wrote: >On Sun, Feb 25, 2001 at 02:30:47AM -0800, Manoj Plakal wrote: >> >> Thanks a lot, mutt works now! BTW, if sh was >> required for the syscall then how come vim >> was able to perform shell commands without >> problems? Is this specific to mutt? > >It's not specific to mutt but I don't know why it works in vim. >A look into the sources should help, though. I believe that vim is pretty clever about using your editor from /etc/passwd or possibly from the SHELL environment variable. cgf -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple