On Thu, Jun 19, 2008 at 09:52:19AM -0500, Kyle Wheeler wrote:
Come to think of it, how can such an email actually exist? When email
is transmitted via SMTP, it's *required* to be terminated by a
newline. If it isn't, there's no way to know that the message has
finished.
Ah, we can't fault
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, June 18 at 07:16 PM, quoth Erik Christiansen:
However, invoking vim within mutt reveals the invisible last (or
only) paragraph. Curiously, appending a newline, to terminate the
last line, while in vim, causes the whole trailing
Reading mail from a variety of lists, with Mutt 1.5.15+20070412
(2007-04-11), I'm finding that the last paragraph of replies in the
posts from just one person are not displayed.
However, invoking vim within mutt reveals the invisible last (or only)
paragraph. Curiously, appending a newline, to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, June 18 at 07:16 PM, quoth Erik Christiansen:
Reading mail from a variety of lists, with Mutt 1.5.15+20070412
(2007-04-11), I'm finding that the last paragraph of replies in the
posts from just one person are not displayed.
However,
On Wed, Jun 18, 2008 at 08:25:53AM -0500, Kyle Wheeler wrote:
It sounds like you might have a $display_filter set. Do you?
Nope, but it's educational to know that's there, if I ever need it.
I wondered if I'd inadvertently zapped the unterminated last line in a
color regex, but there's nothing
On Fri, Feb 15, 2002 at 03:10:35PM +, Simon White wrote:
You probably all use save-hooks and all that, but on my setup:
I hit s, then backspace to get rid of the default, and as I hit backspace the
string gets 'corrupted', i.e. what I see on screen is a mix of what I typed
and what I
Perhaps this is where the problem lies. I haven't done anything for ncurses to
handle multibyte input (which is what I understand dead-keys to be). If
ncurses sees that as 3 characters, it'll think that's how long it displays via
a prompt. So the repainting would be farther to the right,
