This other thread, about wrapmargin setting in Mutt, generally: On Fri, 15 Oct, 2004 at 08:05:44 +0200, Anders Johansson wrote:
On Friday, 15 October 2004 07.54, Jon Clausen wrote:
On the commandline;
echo $[COLUMNS - 72]
works fine. It's just as if Mutt doesn't respond to the "set wrapmargin" -line...
Are you sure it doesn't evaluate to -72, making mutt ignore it? If you execute that echo in a non-interactive shell, I don't think $COLUMNS is set
Indeed. Your example (quoted in the thread "Dynamic variables (was; Mutt configurations)") made me wonder about the reasoning behind the whole `echo $[COLUMNS - 72]` -deal. In your example (using an 80 char terminal) the above evaluates to 8. What sense, then, does it make to set wrapmargin using the above expression? I dunno, maybe I'm misunderstanding something... Does wrapmargin 'count' from the right side or the left side of the terminal? *Anyway* I think I should clarify on what I'm seeing. I almost all the time ssh into the server and run mutt on it. This usually happens from a Kterm, maximized on my 17" monitor. When I 'echo $COLUMNS' I get 156. It's not that mutt doesn't wrap single long lines, but it does it at the edge of the Kterm. Which means that long lines really *stay* long. If I resize the terminal, text reflows nicely though. So: Just setting wrapmargin=80 has the effect that I desired. Long lines are wrapped at about the same place on the screen, that 'short' lines do. Making the term narrower than 80 chars, mutt reflows the text to fit, so I'm all happy about that. /Jon -- Just say "know!"