88882Re: utf8 BOM
- Apr 2, 2008Tony,
Can you show how you set your custom status line to include that
additional info? Thanks for all of the information.
On Apr 1, 11:25 pm, Tony Mechelynck <antoine.mechely...@...>
> bill lam wrote:--~--~---------~--~----~------------~-------~--~----~
> > Tony Mechelynck wrote:
> >> The default behaviour for existing files is to leave it unchanged. The
> >> default for new files depends on the global setting of 'bomb' (which is
> >> off by default, but I use
> >> setglobal bomb
> > Tony,
> > Thank you for detail answer. I need to write BOM only in some particular cases
> > so that I'll just leaved it as setglobal nobomb.
> > regards,
> Since I don't need to avoid the BOM except in special cases (such as
> executable scripts, where the #! shebang isn't recognised if it is
> preceded by a BOM, and most of my scripts are in Latin1 anyway) I leave
> it on for UTF-8 files. My custom statusline (which displays, in addition
> to the usual stuff, the file's encoding and BOM status) thus
> discriminates between:
> - files in 7-bit US-ASCII, seen as UTF-8 without BOM
> - files in Latin1 with characters above 0x7F, seen as Latin1
> - "true" UTF-8 files, seen as UTF-8 with BOM.
> Best regards,
> The sum of the Universe is zero.
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
- << Previous post in topic Next post in topic >>