Re: [PATCH] <create-alias> writes to $alias_file in $config_charset

To: Mutt dev ml <mutt-dev@xxxxxxxx>
Subject: Re: [PATCH] <create-alias> writes to $alias_file in $config_charset
From: Thomas Roessler <roessler@xxxxxxxxxxxxxxxxxx>
Date: Fri, 4 Aug 2006 14:48:15 +0200
In-reply-to: <20060804124333.GB4582@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Mutt dev ml <mutt-dev@xxxxxxxx>
References: <20060727110428.GA22308@xxxxxxx> <20060804091555.GA27088@xxxxxxx> <20060804124333.GB4582@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.12 (2006-07-18)

On 2006-08-04 12:43:33 +0000, Rocco Rutte wrote:

> I think your assumption that _current_ $config_charset is
> the encoding for the alias file may be wrong for some cases.
> If you do it like this I think you sooner or later get a bug
> report for mutt writing the alias file with current
> $config_charset.

> My idea is to make mutt expect RfC2047-encoding in the alias
> file and let it convert to/from it for reading and writing.

That sounds reasonable.

Another thing to do might be to write an explicit "set
content_charset into the aliases file -- not particularly nice,
though.

-- 
Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.

References:
- [PATCH] <create-alias> writes to $alias_file in $config_charset
  - From: Alain Bench
- Re: [PATCH] <create-alias> writes to $alias_file in $config_charset
  - From: Alain Bench
- Re: [PATCH] <create-alias> writes to $alias_file in $config_charset
  - From: Rocco Rutte

Prev by Date: Re: [PATCH] <create-alias> writes to $alias_file in $config_charset
Next by Date: Re: mutt/2355: Mutt can't be built with a separate build dir and read-only source dir
Previous by thread: Re: [PATCH] <create-alias> writes to $alias_file in $config_charset
Next by thread: Re: [PATCH] <create-alias> writes to $alias_file in $config_charset
Index(es):
- Date
- Thread