On Mon, Oct 11, 2010 at 01:01:48AM +0800, H Xu wrote:
> Hello Bram,
> The way to reproduce it is simple: open a new file:
> vim test.txt
>
> test.txt must not exist.
> Then input some letters and use ":w" to save the file. now check the
> value of "fileencoding": it is empty, while it should be so
Hello Bram,
The way to reproduce it is simple: open a new file:
vim test.txt
test.txt must not exist.
Then input some letters and use ":w" to save the file. now check the
value of "fileencoding": it is empty, while it should be some value.
I don't think this is what intended to be. Thank you.
Ho
H Xu wrote:
> Does this bug get any chance to be fixed? Thanks.
This is not a bug. Works as intended.
> On 10/1/10, Tony Mechelynck wrote:
> > On 01/10/10 03:39, H Xu wrote:
> >> Hello,
> >>
> >> The value of "fileencoding" does not change after saving a new file,
> >> until reopen the file.
Does this bug get any chance to be fixed? Thanks.
On 10/1/10, Tony Mechelynck wrote:
> On 01/10/10 03:39, H Xu wrote:
>> Hello,
>>
>> The value of "fileencoding" does not change after saving a new file,
>> until reopen the file.
>>
>> Regards,
>> Hong Xu
>> 10/01/2010
>>
>
> I can reproduce this
On 01/10/10 03:39, H Xu wrote:
Hello,
The value of "fileencoding" does not change after saving a new file,
until reopen the file.
Regards,
Hong Xu
10/01/2010
I can reproduce this bug, as follows: with 'encoding' set to "utf-8",
'fileencoding' (locally) empty, no character above U+00FF in th
Hello,
The value of "fileencoding" does not change after saving a new file,
until reopen the file.
Regards,
Hong Xu
10/01/2010
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.v
