On 24Feb2009 13:18, I wrote:
| It would be nice to be able to distiniguish these two, maybe with a
| "reply_format" which defaults to the value of "display_format".
s/format/filter/g
Whoops,
--
Cameron Simpson DoD#743
http://www.cskk.ezoshosting.com/cs/
On 23Feb2009 11:35, Rejo Zenger wrote:
| ++ 10/02/09 09:48 -0800 - Gary Johnson:
| >message formatting (HTML?) to text. There may be an option in the
| >program to inhibit that behavior, or you can find the program in
| >your mailcap file and add "| col -b" after it.
|
| The generic mailcap file
++ 10/02/09 09:48 -0800 - Gary Johnson:
>message formatting (HTML?) to text. There may be an option in the
>program to inhibit that behavior, or you can find the program in
>your mailcap file and add "| col -b" after it.
The generic mailcap file in /etc/ told mutt to use html2text to use for
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, February 11 at 01:47 PM, quoth Rejo Zenger:
>> Something else that can affect things is the fact that mutt is
>> converting the email into *text* for replying to it. This doesn't
>> sound like a big deal until you consider that you're c
++ 10/02/09 10:58 -0600 - Kyle Wheeler:
>Well, it depends on the original email, obviously. But keep in mind
>that mutt is juggling the rather herculean task of providing everybody
>with the character set it expects, to the best that mutt understands
[...]
I understand.
>Something else that ca
++ 10/02/09 18:02 +0100 - Rocco Rutte:
>> Please read the manual at http://www.mutt.org!
>>
>> Then, when I try to reply to that message, this line is quoted like:
>>
>> >Please read the manual at
>> h_^Ht_^Ht_^Hp_^H:_^H/_^H/_^Hw_^Hw_^Hw_^H._^Hm_^Hu_^Ht_^Ht_^H._^Ho_^Hr_^Hg_^H!
>>
>> Of course, th
On 2009-02-10, Rejo Zenger wrote:
>
> Hi there,
>
> Of course, mutt is doing fine. Just recently, I changed the locale to be
> used by mutt (I changed the charset setting) because the threads were
> incorrectly rendered in the message listing. Since that change, or just
> somewhere afterwards, r
Hi,
* Rejo Zenger wrote:
The original message contains a line like:
Please read the manual at http://www.mutt.org!
Then, when I try to reply to that message, this line is quoted like:
>Please read the manual at
h_^Ht_^Ht_^Hp_^H:_^H/_^H/_^Hw_^Hw_^Hw_^H._^Hm_^Hu_^Ht_^Ht_^H._^Ho_^Hr_^Hg_^H!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 10 at 05:45 PM, quoth Rejo Zenger:
> What does remain is the original problem: why is it that in replies
> the URI's are mangled?
Well, it depends on the original email, obviously. But keep in mind
that mutt is juggling the rath
++ 10/02/09 08:55 -0600 - Kyle Wheeler:
>> Possibly relevant settings in my mutt configuration:
>> set charset = utf-8
>
>Do not set this yourself (unless you really REALLY know what you're
>doing).
I have removed this setting and I this doesn't change a thing in the way
mutt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, February 10 at 12:05 PM, quoth Rejo Zenger:
> Of course, mutt is doing fine. Just recently, I changed the locale
> to be used by mutt (I changed the charset setting)
Changing the $charset setting manually is *usually* a bad idea; mutt
is
Hi there,
Of course, mutt is doing fine. Just recently, I changed the locale to be
used by mutt (I changed the charset setting) because the threads were
incorrectly rendered in the message listing. Since that change, or just
somewhere afterwards, replying to messages with URL's in the body has
be
12 matches
Mail list logo
