quoting urls in replies

[Rejo Zenger]

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
become somewhat cumbersome.

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!

Of course, this is not what I want. I don't really understand what does
introduce this magic. Anyone does?

Possibly relevant settings in my mutt configuration:

set charset = utf-8
set escape  = ~
set editor  = 'vim -c "set tw=72 fo+=aw smartindent" +2'
set indent_string   = ">"
set use_8bitmime= no

Anyone? Thanks in advance!



-- 
Rejo Zenger .  . 0x75FC50F3 . 
GPG encrypted e-mail prefered. 


signature.asc
Description: Digital signature

Re: quoting urls in replies

[Kyle Wheeler]

-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 very good at figuring out what the correct value for that setting 
should be. If you're having a problem, something else will probably be 
more effective.

Keep in mind that $charset tells mutt what characters it's allowed to 
display. This has nothing to do with the email, and has everything to 
do with your terminal. Usually this is controlled via the $LANG 
environment variable (or the $LC_* variables, if you want more 
precision). The reason for this is that many components of your 
system, in addition to mutt, need to know this information (for 
example, your termcap library needs to know).

If you truly do have a terminal that is capable of displaying UTF-8 
output (and has that option turned on), then you should probably set 
your LANG to be something ending in ".utf8". For example, I use a LANG 
setting of "en_US.UTF-8". Find out what your options are by running 
the program `locale -a`.

> because the threads were incorrectly rendered in the message 
> listing.

This sounds more likely to be a problem that would be solved by using 
the $assumed_charset setting (which is intended to help address the 
rather common problem of incorrectly encoded email).

> 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).

> set escape  = ~ 
> set editor  = 'vim -c "set tw=72 fo+=aw smartindent" +2' 
> set indent_string   = ">" 
> set use_8bitmime= no

The rest of these are pretty typical.

If you normally correspond with people who speak English or another 
western-European language, you probably want to start by adding this 
line to your muttrc:

 set assumed_charset = "cp1252"

If you want to be more comprehensive, add these as well:

 charset-hook ^unknown-8bit$   windows-1252
 charset-hook ^x-user-defined$ windows-1252
 charset-hook ^iso-8859-1$ windows-1252
 charset-hook ^us-ascii$   windows-1252
 charset-hook ^none$   windows-1252
 charset-hook ^iso-8859-8-u$   iso-8859-8
 charset-hook ^gb2312$ gb18030

~Kyle
- -- 
I prefer to be called "EVIL GENIUS!"
 -- Jumba, from "Lilo & Stitch"
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkmRlVUACgkQBkIOoMqOI16jcwCg+JlovV/+3a2GJatcnYWviqiq
lXwAoN4jjx9AHKPUariHopxagQNQW0oW
=pC2B
-END PGP SIGNATURE-

Re: sidebar patch for 1.5.19

[Elimar Riesebieter]

* Cristóbal Palmer [090206 16:51 -0500]
> On Fri, Feb 06, 2009 at 10:12:39AM +0300, Andrey Zhidenkov wrote:
> > Is there a sidebar patch for 1.5.19 version? Where can I get it?
> 
> I vaguely remember the debian package maintainer saying that he was
> working on mutt-patched to get it working for .19, but that there was
> a lot of work to be done before that would work. Can't seem to find
> that email, though.

You can find an inoffical package (i386|amd64|ppc) including
sidebar, indexcolor, tokyocabinett  and sources here:
deb  http://www.lxtec.de/debarchiv unstable main
deb-src  http://www.lxtec.de/debarchiv unstable main

Elimar


-- 
  The path to source is always uphill!
-unknown-


signature.asc
Description: Digital signature

Re: quoting urls in replies

[Rejo Zenger]

++ 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 shows the threads. So, this is no longer an issue (on itself). 

What does remain is the original problem: why is it that in replies the 
URI's are mangled? 





-- 
Rejo Zenger .  . 0x75FC50F3 . 
GPG encrypted e-mail prefered. 


signature.asc
Description: Digital signature

Re: quoting urls in replies

[Kyle Wheeler]

-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 rather herculean task of providing everybody 
with the character set it expects, to the best that mutt understands 
what they're expecting. For example, it has to convert everything into 
a character set that the terminal can understand. When replying, it 
has to convert into a character set that your editor will understand. 
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 converting from 
things like html.

As an example, some folks use html rendering programs (like 
development versions elinks) that, when rendering HTML, can include 
ANSI color codes. This can be quite convenient when viewing emails 
inline, but when using that same program to provide text to your 
editor, those color codes might be misinterpreted. As far as I know, 
mutt tries to do the right thing there, but my point is that 
constructing messages for replying can be a more complicated thing 
than we realize. Figuring out exactly how the process breaks down when 
something goes awry requires knowing exactly what you're asking mutt 
to do.

I'm giving you generalities here, because I don't know the specifics 
of your setup or the emails you're replying to. But does that help?

~Kyle
- -- 
No man goes so high as he who knows not where he is going.
-- Cromwell
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkmRslAACgkQBkIOoMqOI16lbACcCXuY4w1v9HWLELhJf05T1cOx
9YwAn3ZDbYtUawC8xrT8Jw6EQaEcT/Fr
=y+bc
-END PGP SIGNATURE-

Re: quoting urls in replies

[Rocco Rutte]

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!

Of course, this is not what I want. I don't really understand what does
introduce this magic. Anyone does?


The second form of the URL looks like it contains ansi-escape sequences
to control text attributes like bold text. Mutt can properly render this
kind of text so the URL looks "normal." What you see in the editor is
what it really looks like. If you got such URLs, there's nothing you can
do about it.

Just out of curiosity, who sends ansi-escaped URLs? Does this always
happen (I hope not)?

Rocco

Re: quoting urls in replies

[Gary Johnson]

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, replying to messages with URL's in the body has
> become somewhat cumbersome.
> 
> 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!
> 
> Of course, this is not what I want. I don't really understand what does
> introduce this magic. Anyone does?

The URL is being underlined by the technique of printing an
underscore, backspacing, then overstriking with the character to be
underlined.  Mutt's built-in pager understands that technique and
will display such sequences in color, or perhaps underlined,
depending on your terminal.  (It displays on my rxvt in color.)

That sequence was probably in the original message, but you weren't
aware of it because mutt's pager handled it.  Your editor, on the
other hand, either doesn't understand such sequences or presents
them to you as raw sequences anyway because, after all, it is an
editor.

One solution would be to filter such lines in your editor through
the external command "col -b".  Another would be to execute a
command such as this one for vim:

:%s/_\b//g

If that sequence was not in the original message, it must have been
added by some program you are using to convert from the original
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.

HTH,
Gary

encoding in replies

[Jan-Herbert Damm]

Hello everybody,

I suspect I have a similar encoding problem like the one discussed today. (in
the thread: "quoting urls in replies". It might be trivial and i apologize if
it is. I did try to RTFM and i have been pondering this with growing
desperation:

The problem in short: When I write mails with german umlauts to myself, I get
them back with the umlauts displayed as questionmarks.
 
I use vim to write my mails (i tell mutt to use it via an entry "export
EDITOR=/usr/bin/vim" in .bashrc) when I write the mail umlauts are displayed
nicely. but if I postpone the message and resume writing afterwords the
umlauts are allready gone. (I guess that has to to with mutt opening a new
tmp-file). 

The output of ":set all" in vim shows among other things "encoding=utf-8"
The output of "locale" in bash:
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

No "$charset" ist set in .muttrc

And one more really strange thing: 
All of this happens on a custom gnome desktop environment. If I switch to a
Terminal without X. Bash displays all the capitalized umlauts and the small
a-umlaut but not the small u-umlaut and the small o-umlaut, it simply 
presents a space instead (whereas vim or mutt show some graphical characters 
that I have never seen before for these and only for these umlauts) 

I am aware that I might have explained all this badly. That is because i don't
understand the problem. If somebody can tell me the right RTFMs to read i will
happily do that homework first. 

Thanks 

jan 
-- 

Was lange g?rt wird endlich Wut.

how to revert an attachment when composing

[bill lam]

When composing new mails, I can use "a" to add attachments. However I
cannot find any hot-key to revert an attachment (do not attach that
attachment).  Is there any way to do it?

Thanks.

-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩036 王昌齡  塞上曲
蟬鳴空桑林  八月蕭關道  出塞復入塞  處處黃蘆草
從來幽并客  皆向沙場老  莫學遊俠兒  矜誇紫騮好

Re: how to revert an attachment when composing

[Nicolas Sebrecht]

On Wed, Feb 11, 2009 at 10:03:27AM +0800, bill lam wrote:
> 
> When composing new mails, I can use "a" to add attachments. However I
> cannot find any hot-key to revert an attachment (do not attach that
> attachment).  Is there any way to do it?

D ?

-- 
Nicolas Sebrecht

Re: how to revert an attachment when composing

[Cristóbal Palmer]

On Wed, Feb 11, 2009 at 10:03:27AM +0800, bill lam wrote:
> When composing new mails, I can use "a" to add attachments. However I
> cannot find any hot-key to revert an attachment (do not attach that
> attachment).  Is there any way to do it?

with the attachment highlighted:

D

Cheers,
-- 
Cristóbal Palmer
ibiblio.org systems administrator
cdla.unc.edu research assistant

Re: how to revert an attachment when composing

[Noah Sheppard]

> with the attachment highlighted:
> 
> D

No, that lets you set a description (at least for me, and I have not
remapped the D key in my muttrc.

-- 
Noah Sheppard
Assistant Computer Resource Manager
Taylor University CSE Department
nshep...@cse.taylor.edu

Re: how to revert an attachment when composing

[Noah Sheppard]

> > with the attachment highlighted:
> > 
> > D
> 
> No, that lets you set a description (at least for me, and I have not
> remapped the D key in my muttrc.
Retract previous comment, I was hitting 'd' rather than 'D'.

Thanks, Cristóbal.
-- 
Noah Sheppard
Assistant Computer Resource Manager
Taylor University CSE Department
nshep...@cse.taylor.edu

Re: how to revert an attachment when composing

[bill lam]

> with the attachment highlighted:
> 
> D

Thanks Cristóbal, Nicolas.

That is called 'detach', no wonder I searched TFM for 'attach' and
could not locate it.

-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩149 司空曙  賊平後送人北歸
世亂同南去  時清獨北還  他鄉生白髮  舊國見青山
曉月過殘壘  繁星宿故關  寒禽與衰草  處處伴愁顏

Re: encoding in replies

[Derek Martin]

On Tue, Feb 10, 2009 at 08:08:39PM +0100, Jan-Herbert Damm wrote:
> The problem in short: When I write mails with german umlauts to myself, I get
> them back with the umlauts displayed as questionmarks.

Here's a clue:

> 
> Was lange g?rt wird endlich Wut.

The third word in the second line contains a character which is not
present in the character set used to encode this message, or it
contains one which can not be translated to UTF-8.

I checked the charset of the message, and it was listed as:

  Content-Type: text/plain; charset=iso-8859-1 

What's the value of send_charset?

Whatever the case, you seem to have a charset mismatch somewhere
between your terminal, your editor, and mutt.  Your locale settings
seem fine, which suggests to me that maybe your send_charset does not
include a character set which contains the characters you need... But
I think there are still other possibilities too.

-- 
Derek D. Martinhttp://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.



pgpYNmgAAr2TD.pgp
Description: PGP signature