Date: Fri, 17 Jul 1998 19:22:38 +0200 From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de> To: ports@FreeBSD.ORG, dannyman@enteract.com, dannyman@dannyland.org, Greg Lehey <grog@lemis.com>, obrien@NUXI.com Subject: Re: mutt-emacs-sh and curses (was Re: pine4 and mutt) Message-ID: <19980717192238.A8308@physik.fu-berlin.de> In-Reply-To: <19980716155256.B27595@nuxi.com>; from David O'Brien on Thu, Jul 16, 1998 at 03:52:56PM -0700 References: <19980712012442.C26465@enteract.com> <19980716013329.A1330@nuxi.com> <19980716234906.A4268@physik.fu-berlin.de> <19980716155256.B27595@nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 16, 1998 at 11:49:06PM +0200, Axel Thimm wrote: > According to the mutt user list, /bin/sh from FreeBSD is `broken' in such a > way, that e.g. a spawned emacs as an editor doesn't get a ^G > through. Instead mutt aborts the current command and emacs is detached. On Fri, Jul 17, 1998 at 09:52:40AM +0930, Greg Lehey wrote: > See this reply? It was written in an Emacs editor invoked from mutt. > Before I started the reply, I pressed ^G several times. In other > words, the information from the list is wrong. It is not only the information from the list, it is my own system behaving that way (-stable Jul 11, Mutt 0.93i (1998-07-10) with ncurses 1.8.6/ache on xterm from XFree86 3.3.2) On Thu, Jul 16, 1998 at 03:52:56PM -0700, David O'Brien wrote: > I would rather someone figure out what changed in /bin/sh from 2.2-STABLE to > 3.0-CURRENT, than depend on another shell. Does it work on -current? From mutt' INSTALL file: > --with-exec-shell=SHELL > on some versions of unix, /bin/sh has a bug that makes using emacs > with mutt very difficult. If you have the problem that whenever > you press control-G in emacs, mutt and emacs become very confused, > you may want to try using a Bourne-derived shell other than > /bin/sh here. Some shells that may work are bash, zsh, and ksh. > C shells such as csh and tcsh will amost certainly not work right. > [...] > FreeBSD 3.0 > > /bin/sh is broken on this platform. You need the > "--with-exec-shell" configuration switch here; ksh > and bash are reported to be fine. > > This may also be an issue with earlier FreeBSD > versions. Some months ago (Mon, 9 Mar 1998 11:33:04 +0100) Martin Cracauer <cracauer@BIK-GmbH.DE> had posted on hackers@FreeBSD.ORG and was quoted on the mutt list with the following statement: > Another issue is that problems in our `make` require /bin/sh to behave > wrong (to terminate on SIGINT even if foreground processes run), > otherwise you'll end up with hard-to-kill recursive makes. Perhaps this helps. -- Axel.Thimm@physik.fu-berlin.de Axel.Thimm@ifh.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980717192238.A8308>