On Sat, Oct 29, 2016 at 11:35 PM, Ben Fritz wrote:
> On Tuesday, October 11, 2016 at 5:17:33 AM UTC-5, Gabriele wrote:
>> On 10/10/2016 17.42, Ben Fritz wrote:
>> > To detect this automatically, be sure that you have "set
>> > encoding=utf-8", "setglobal bomb", and "set
>> > fileencodings=ucs-bomb
On Tuesday, October 11, 2016 at 5:17:33 AM UTC-5, Gabriele wrote:
> On 10/10/2016 17.42, Ben Fritz wrote:
> > To detect this automatically, be sure that you have "set
> > encoding=utf-8", "setglobal bomb", and "set
> > fileencodings=ucs-bomb,utf-8,latin1" or similar in your .vimrc.
> > http://vi
see my corrected additional lines for Wordpad compatibility at the end of this
posting
The results of my test are:
Edit existing files with VIM are written back in the same UTF/UNICODE/ANSI code
as originally.
Creating a new file differs
Notepad accepts all characters e.g. by paste text from a
On 11/10/2016 17.36, aroc...@vex.net wrote:
On my system the global bomb setting is not used if I don't also add
"setlocal bomb<" or "set bomb<".
Don't even think about discussing this anywhere near an airport! :-)*
Yeah, better add "set nobomb" to your notebook's vimrc :-)
--
--
You receiv
On 11/10/2016 16.47, Erhy wrote:
I will accept the converted message because
saving the file, the converted message appears again
and the resulting BOMB is the same.
I found out that [converted] only means "conversion from 'fileencoding'
to 'encoding' done" (insert.txt help), so it doesn't rea
On 11/10/2016 16.30, Gabriele Fava wrote:
If you want that the UTF-16 files be left in that encoding you'll have
to add that as well to the 'fileencodings' (before latin1).
I was wrong, if you have ucs-bom at the start of fileencodings it will
detect UTF-16 encodings as well, set the 'fileencodi
Thanks all for discussing and the joke.
The repeated mails detected by Gabriele
were created because I want to correct them (delete and asnwere again)
Erhy
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
> On my system the global bomb setting is not used if I don't also add
> "setlocal bomb<" or "set bomb<".
>
Don't even think about discussing this anywhere near an airport! :-)*
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are
Am Dienstag, 11. Oktober 2016 16:31:46 UTC+2 schrieb Gabriele Fava:
> You posted the same settings in the last 3 mails.
>
> Anyway, the only problem you are still having is the [converted] message?
> I don't get it, are you sure that the files you're opening are really in
> UTF-8?
> Note that the
You posted the same settings in the last 3 mails.
Anyway, the only problem you are still having is the [converted] message?
I don't get it, are you sure that the files you're opening are really in
UTF-8?
Note that the Windows' Notepad saves in UTF-16 if you select "Unicode"
as Encoding.
Actuall
now I inserted the lines below in my _vimrc.
it works well, although the message
converted
appears.
I detected, that VIM allways append a
0D 0A
at the end, if there wasn't such,
solved with
set nofixendofline
Erhy
if has("multi_byte")
echomsg "has MULTIBYTE"
if &termencoding == ""
let &
now I inserted the lines below in my _vimrc.
it works well, although the message
converted
appears.
I detected, that VIM allways append a
0D 0A
at the end, if there wasn't such,
perhaps for this a other setting is responsible.
Erhy
if has("multi_byte")
echomsg "has MULTIBYTE"
if &termencod
now I inserted the lines below in my _vimrc,
but if I open an UTF file and saved with another filename UTF bomb is not
applied
Erhy
if has("multi_byte")
echomsg "has MULTIBYTE"
if &termencoding == ""
let &termencoding = &encoding
endif
setglobal encoding=utf-8
set encoding<
setglo
On 10/10/2016 17.42, Ben Fritz wrote:
To detect this automatically, be sure that you have "set
encoding=utf-8", "setglobal bomb", and "set
fileencodings=ucs-bomb,utf-8,latin1" or similar in your .vimrc.
http://vim.wikia.com/wiki/Working_with_Unicode
Can you tell me if you intentionally used
I'm confused about the message
converted,
if I open a file
Erhy
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because y
On Monday, October 10, 2016 at 10:33:26 AM UTC-5, Erhy wrote:
> Hello,
> for administer Windows I would like to use gVIM.
> But there are some UTF encoded files.
> Opening such files gVim decoded them and save the without BOMB.
> Are there setting to have the same behavior as Windows notepad?
> Tha
Hello,
for administer Windows I would like to use gVIM.
But there are some UTF encoded files.
Opening such files gVim decoded them and save the without BOMB.
Are there setting to have the same behavior as Windows notepad?
Thank you for tips
Erhy
--
--
You received this message from the "vim_use"
17 matches
Mail list logo
