Re: mutt to show hi-bit chars once & for all?

Hi Russell,

Am 2005-09-17 03:37:30, schrieb Russell Hoover:

> # Never do Quoted-Printable encoding on 8-bit characters:
>       set  allow_8bit
> 
>       set  charset="us-ascii:iso-8859-1:utf-8"
>  set  send_charset="us-ascii:iso-8859-1:utf-8"
> 
> 
> In my .zshenv:
> 
> # export LC_ALL=en_US.UTF-8      <--- ( commented-out )
> export LC_CTYPE=en_US.UTF-8
> 
> Those are the only relevant settings I can think of
> right now.

You have broken locale.

Because it is   en_US.utf8

      and not   en_US.UTF-8

Greetings
Michelle

--

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/

Re: mutt to show hi-bit chars once & for all?

On Sat, 15 Oct 2005 the mental interface of
Michelle Konzack told:

> Hi Russell,
> 
> Am 2005-09-17 03:37:30, schrieb Russell Hoover:
> 
> > # Never do Quoted-Printable encoding on 8-bit characters:
> >       set  allow_8bit
> > 
> >       set  charset="us-ascii:iso-8859-1:utf-8"
> >  set  send_charset="us-ascii:iso-8859-1:utf-8"
> > 
> > 
> > In my .zshenv:
> > 
> > # export LC_ALL=en_US.UTF-8      <--- ( commented-out )
> > export LC_CTYPE=en_US.UTF-8
> > 
> > Those are the only relevant settings I can think of
> > right now.
> 
> You have broken locale.

No

> Because it is   en_US.utf8
> 
>       and not   en_US.UTF-8

Re: mutt to show hi-bit chars once & for all?

On Sat, Oct 15, 2005 at 04:22:24PM +0200, Michelle Konzack wrote:
> Hi Russell,
> 
> Am 2005-09-17 03:37:30, schrieb Russell Hoover:
> > # export LC_ALL=en_US.UTF-8      <--- ( commented-out )
> > export LC_CTYPE=en_US.UTF-8
> > 
> > Those are the only relevant settings I can think of
> > right now.
> 
> You have broken locale.
> 
> Because it is   en_US.utf8
> 
>       and not   en_US.UTF-8

Well, I'm not sure about debian systems, but en_US.UTF-8 is the
default locale installed by redhat-based systems and that works just
fine.  I seem to remember trying to use .utf8 instead of .UTF-8, so
that I could use the same environment files on all systems I use, and
finding that some things broke.  That's despite the fact that
en_US.utf8 shows up in the output of locale -a, and en_US.UTF-8 does
not.

Anyway, en_US.UTF-8 works just fine, at least on redhat-based systems.

--

-- 
Derek D. Martin    http://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in

Re: IMAP woes

Hallo Thomas,

Am 2005-09-22 03:44:51, schrieb Thomas Zehetbauer:
> First I would like to say that I have just come back to mutt after some 
> years of using Ximian Evolution and even trying Thunderbird.



> or have the "mailboxes" view use short names (without $folder) and show 
> the hierarchy (=A\n\t=A/B\n=C).

ACK

> Additionally I think I have found two bugs in the browser:
> 
> When browsing IMAP folders, they are sorted uppercase letters first:
> A -> B -> C -> a -> b -> c
> Maybe this is the unsorted list as supplied by the IMAP server, because 
> the sort order is corrected if I sort again (<sort>a).

I am using de_DE <at> euro and the sorting is A a B b C c.
Maybe you should setup correctly your environement?

> Renaming IMAP folders is even worse as no space character can be entered 
> and the / is not recognized as a hierarchy separator (imap_delim_chars).

You can cange it...

> Finally I would like to say that the date input format should also be 
> made configurable. DD/MM/YYYY is prone to confusion with MM/DD/YYYY in 

Re: url_handler.sh email

Hi Aris,

Am 2005-09-29 16:49:12, schrieb Arias Hung:
> How would I state url_handler.sh REGEX variable to also include normal 
> email addresses that appear in the body of the message that doesn't have a 
> mailto: pretag?
> 
> I could have sworn that urlview was suppose to handle normal u <at> d type mail 
> regex's by default but it doesn't seem to be included in the default system 
> urlview.

Attached my script

> Thanks for any help anyone can offer.

Greetings
Michelle

--

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/3/88452356    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

write_bcc and fcc

For users who use Exim or other MTAs that don't strip bcc headers,
normally you must set write_bcc=no so that your bcc headers won't show
up in messages unintentionally.  However this also has the effect of
preventing the Bcc line from showing up in your saved mail.

I've written a patch against the latest CVS so that the Bcc line is
always written to the fcc (saved mailbox) regardless of the value of
$write_bcc which allows you to see who your Bcc recipients were when
reviewing your sent mail.  I suspect it will also apply against any
recent version of mutt, since the affected code probably hasn't
changed in a long time.  I've tested it with no problems, but feel
free to provide feedback if you have trouble with it.  

The patch is attached.

--

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

diff -r -u mutt-cvs-2005-10-15/headers.c mutt-cvs-2005-10-15.ddm/headers.c
--- mutt-cvs-2005-10-15/headers.c	2005-09-17 16:46:10.000000000 -0400
+++ mutt-cvs-2005-10-15.ddm/headers.c	2005-10-15 13:05:49.000000000 -0400
@@ -52,7 +52,7 @@
   }

   mutt_env_to_local (msg->env);

Re: IMAP woes

On 2005-10-15 | 19:21:54, Michelle Konzack wrote:
>> When browsing IMAP folders, they are sorted uppercase letters first:
>> A -> B -> C -> a -> b -> c
>> Maybe this is the unsorted list as supplied by the IMAP server, because 
>> the sort order is corrected if I sort again (<sort>a).
>
>I am using de_DE <at> euro and the sorting is A a B b C c.
>Maybe you should setup correctly your environement?

Do you think it changes my environment when I press "oa" (sOrt Alpha)? 
The problem is, that sort_browser is ignored for IMAP folders.

>> Renaming IMAP folders is even worse as no space character can be entered 
>> and the / is not recognized as a hierarchy separator (imap_delim_chars).
>
>You can cange it...

No, you can't, imap_delim_chars is IGNORED there, that is what I am 
complaining about.

>> Finally I would like to say that the date input format should also be 
>> made configurable. DD/MM/YYYY is prone to confusion with MM/DD/YYYY in 
>> english speaking countries. ISO 8601 recommends YYYY-MM-DD but this will 
>> not be compatible with the current range syntax.
>
>???  Do you have read the mutt-manual ?

Maybe you would better read some books on the grammar of the english 
language before answering mails. You failed to understand three of five 
points I have been making.