On 20/03/09 14:11, Matt Wozniski wrote:
>
> On Fri, Mar 20, 2009 at 1:17 AM, Tony Mechelynck wrote:
>>
>> On 17/03/09 02:01, pansz wrote:
>>>
>>> Tony Mechelynck 写道:
Personally, I use "setglobal bomb" in my ~/.vimrc. Not sure if it's
"good practice",
>>>
>>> As far as I know gcc wil
On Fri, Mar 20, 2009 at 1:17 AM, Tony Mechelynck wrote:
>
> On 17/03/09 02:01, pansz wrote:
>>
>> Tony Mechelynck 写道:
>>>
>>> Personally, I use "setglobal bomb" in my ~/.vimrc. Not sure if it's
>>> "good practice",
>>
>> As far as I know gcc will not compile any file with a utf-8 bomb. so I
>> don
On 17/03/09 02:01, pansz wrote:
>
> Tony Mechelynck 写道:
>>
>> Personally, I use "setglobal bomb" in my ~/.vimrc. Not sure if it's
>> "good practice",
>
> As far as I know gcc will not compile any file with a utf-8 bomb. so I
> don't think :setglobal bomb is a good practice unless you never use gcc
bill lam 写道:
> I guess under linux if you choose utf-8 in locale, everything should
> already assume to be utf8. And I don't think any command tools (such
> as head sort) will generate bomb on output or expect bomb in
> stdin/stdout. That being said, I guess utf-8 bomb would be more
> relevant i
On Tue, 17 Mar 2009, pansz wrote:
>
> Tony Mechelynck 写道:
> >
> > Personally, I use "setglobal bomb" in my ~/.vimrc. Not sure if it's
> > "good practice",
>
> As far as I know gcc will not compile any file with a utf-8 bomb. so I
> don't think :setglobal bomb is a good practice unless you ne
Tony Mechelynck 写道:
>
> Personally, I use "setglobal bomb" in my ~/.vimrc. Not sure if it's
> "good practice",
As far as I know gcc will not compile any file with a utf-8 bomb. so I
don't think :setglobal bomb is a good practice unless you never use gcc
to compile your C source code.
Please
On 16/03/09 14:49, Maxim Kim wrote:
>
>
> On 16 мар, 16:20, Tony Mechelynck
> wrote:
>> ...
>> Note that altering any of these three options in an undo_ftplugin line
>> is courting disaster: Vim has a separate mechanism to detect these
>> options' values when opening an existing file, and the resu
On 16 мар, 16:20, Tony Mechelynck
wrote:
> ...
> Note that altering any of these three options in an undo_ftplugin line
> is courting disaster: Vim has a separate mechanism to detect these
> options' values when opening an existing file, and the results are
> usually correct; for new files, you
On 16/03/09 13:55, Maxim Kim wrote:
>
> Hi,
>
> I have a (ft)plugin that overrides filetype of .wiki extension from
> flexwiki to vimwiki. Everything seems quite good except for a state of
> just opened buffer that is in 'changed' one.
> As far as I can see FlexWiki ftplugin does :setlocal bomb co
Hi,
I have a (ft)plugin that overrides filetype of .wiki extension from
flexwiki to vimwiki. Everything seems quite good except for a state of
just opened buffer that is in 'changed' one.
As far as I can see FlexWiki ftplugin does :setlocal bomb command that
puts vim's buffer in a 'changed' state
10 matches
Mail list logo