On Sat, Nov 11, 2000 at 09:40:18PM -0500, Josh Huber wrote:
I'm trying out mutt version 1.3.11i, mostly because it has support for
automatically switching the charset= line in outgoing emails to the
proper encoding.
Here's the problem: I can't get japanese to display properly without
* Brian Stearns [EMAIL PROTECTED] [11/11/00, 13:59:18]:
I've configured OpenSSH at home, and I'm using PuTTY at work to establish
a secure terminal session from work to home. Yet again, works great.
It's not a PuTTY issue. I use it at work and it works :)
Finallly, I thought perhaps
On Fri, Nov 10, 2000 at 04:00:21PM -0600, David Kanter wrote:
This is nothing earth-shattering, but rather annoying: Mutt has what looks
like an extra cursor lying on top of the highlighting bar over the last
character in the message index window.
I'm using the slang-based Mutt of OpenBSD.
On 13, Nov, 2000 at 12:28:38AM +0800, Anthony Liu wrote:
On Fri, Nov 10, 2000 at 04:00:21PM -0600, David Kanter wrote:
This is nothing earth-shattering, but rather annoying: Mutt has what looks
like an extra cursor lying on top of the highlighting bar over the last
character in the message
On Tue, Nov 07, 2000 at 02:46:40PM -0600, David Champion wrote:
[snip original discussion of word/character counting]
However, I can imagine a pattern expression that pipes each message
through a command, and matches based on that command's exit status: if
0, match; else, no match. This could
1) Apologies for the lack of line wraps; I forgot to turn on
auto-fill-mode in Emacs.
2) You were exactly right. An evil, old version of mutt in /usr/bin,
which apparently is prepended to my path only when I ssh into my box,
not telnet. I'll have to look into that.
It always seems to be the
