On Sat, Aug 26, 2006 at 06:49:23PM +0200, Alain Bench wrote:
>
> I generally recommend to disable auto-sensing in Vim when called by
> Mutt, by unsetting $fileencodings. But I don't know how it will interact
> with your specific $encoding and $termencoding settings. Perhaps will
> you be force
On Sat, Aug 26, 2006 at 06:12:14PM +0200, Adeodato Simó wrote:
>
> True. Note that even with $edit_charset, you'd have the same problem.
If I could tell mutt to save the file as utf-8 when editing, this should
work.
> Maybe you can resolve it with this in ~/.vimrc (and keeping your macro):
>
>
On Saturday, August 26, 2006 at 11:02:55 +0200, Kurt Roeckx wrote:
> vim is set up to try utf-8 first, and if it fails fall back to
> iso-8859-1.
This Vim smart charset auto-sensing is a great feature, outside of
Mutt. For Mutt, by design, the $editor must be dumb, and use only the
charset o
On Saturday, August 26, 2006 at 12:54:01 +0200, Kurt Roeckx wrote:
> On Sat, Aug 26, 2006 at 11:47:47AM +0200, Alain Bench wrote:
>> I close this Debian bug as duplicate [of upstream/1317]
> The proper way would be to set it as forwarded, since it's not
> actually solved.
Humm... Really forw
Hi Kyle,
On Friday, August 25, 2006 at 20:28:46 -0400, Kyle Wheeler wrote:
> Mutt degrades the charset to the weakest one necessary. In other
> words, if the characters that you use in your file are all valid
> iso-8859-1 characters, then mutt will treat the file as iso-8859-1.
> This is general
* Kurt Roeckx [Sat, 26 Aug 2006 11:18:38 +0200]:
> What I did was tell vim that it should internally store things in utf-8
> by setting "encoding=utf-8". This also has as effect that it changes
> the default for fileencodings to "ucs-bom,utf-8,latin1". The value of
> encoding is also based on th
On Sat, Aug 26, 2006 at 11:47:47AM +0200, Alain Bench wrote:
>
> What you ask would make sense in some situations (like Mutt in a L1
> term calling gvim in UTF, and such), and is already on the upstream Mutt
> wishlist/1317: "Add config var edit_charset".
That would work for me. Specially if
package mutt
severity 384642 wishlist
close 384642
thanks
Hello Kurt, and thanks for the report.
On Friday, August 25, 2006 at 19:09:32 +0200, Kurt Roeckx wrote:
> I'm using a latin1 terminal, but I've set up vim to use utf-8 files by
> default, but fall back to latin1. Vim also shows latin1 o
On Sat, Aug 26, 2006 at 03:15:21AM +0200, Adeodato Simó wrote:
> > I'm using a latin1 terminal, but I've set up vim to use utf-8 files by
> > default, but fall back to latin1. Vim also shows latin1 on the screen.
> > But I can't seem to get mutt and vim to agree on the charset for the
> > file bei
On Fri, Aug 25, 2006 at 08:28:46PM -0400, Kyle Wheeler wrote:
> On Friday, August 25 at 07:09 PM, quoth Kurt Roeckx:
> >So, I was reading the documentation, and it seems that the only
> >thing that I should consider changing seems to be file_charset.
> >I've tried setting that to various things
(Alain, I'm Cc'ing you in case you'd like to send some insight in our
direction. :-)
* Kurt Roeckx [Fri, 25 Aug 2006 19:09:32 +0200]:
> Hi,
Hey Kurt,
> I'm using a latin1 terminal, but I've set up vim to use utf-8 files by
> default, but fall back to latin1. Vim also shows latin1 on the screen
On Friday, August 25 at 07:09 PM, quoth Kurt Roeckx:
So, I was reading the documentation, and it seems that the only
thing that I should consider changing seems to be file_charset.
I've tried setting that to various things like just "utf-8", or
"utf-8:iso-8859-1", but it doesn't seem to be cha
Package: mutt
Version: 1.5.9-2sarge2
Hi,
I'm using a latin1 terminal, but I've set up vim to use utf-8 files by
default, but fall back to latin1. Vim also shows latin1 on the screen.
But I can't seem to get mutt and vim to agree on the charset for the
file being used.
When I start a new mail:
I
13 matches
Mail list logo
