On 2017-04-25 12:36:01 -0700, Kevin J. McCarthy wrote:
> On Tue, Apr 25, 2017 at 12:49:05PM -0500, Derek Martin wrote:
> > On Mon, Apr 24, 2017 at 11:33:20AM +0200, Vincent Lefevre wrote:
> > > On 2017-04-23 09:59:33 -0500, Derek Martin wrote:
> > > > Although, I don't really get why Mutt needs a f
On 2017-04-25 12:49:05 -0500, Derek Martin wrote:
> $ cat ~/prog/termsize
> #!/bin/sh
> echo "lines = $LINES; cols = $COLUMNS"
>
> $ export LINES COLUMNS
> $ ~/prog/termsize
> lines = 24; cols = 129
> $ echo $TERM
> screen
> $ mutt
>
> Then, from within mutt, execute ~/prog/termsize:
>
> ---Mut
#3937: Build failure on macOS 10.12.14
-+--
Reporter: chdiza | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: build |Version:
Resolution: | Keywords:
-+---
#3937: Build failure on macOS 10.12.14
-+--
Reporter: chdiza | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: build |Version:
Resolution: fixed | Keywords:
-+
On 02May2017 10:43, vincent lefevre wrote:
[...] And I compiled Mutt with EXECSHELL set to
a wrapper to /bin/bash (not /bin/sh since this is dash in general
and dash is broken[*]) [...]
[*] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683671
I'm not sure this is a bug in dash, but a misfe
On 03May2017 08:52, Cameron Simpson wrote:
If you know it will be interactive you need to arrange that specially. In
particular, you possibly want to make the shell or command the process group
leader and set that group as the controlling terminal's group, as that affects
the handling of sign
