Re: [PATCH v2] commit, status: #comment diff output in verbose mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Mar 17, 2011 at 09:01:33AM +0100, Michael J Gruber wrote:

> > Yuck. You may be literally feeding different charsets into a single
> > buffer of the editor. The best you could do is something like:
> > 
> >   au BufNewFile,BufRead COMMIT_EDITMSG set fenc=utf-8
>
> [...]
>
> Though I'm wondering whether we should do something about it in general
> (we assume utf8 commit messages, don't we), at least in doc. Your
> suggestion above does make things safer (so that you don't screw up the
> commit message accidentally) and would make a good patch to vim's
> filetype.vim

Being perfectly content with ASCII for my native language, I am not a
good person to judge. But I wonder how common your situation is. That
is, your files are all in latin1, but you continue to use utf8 for your
commit messages. Perhaps an easier solution would just be to tell git
that you want to make commit messages in latin1?

-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]