Bug fix : hidden command line after snippet rendering.

[dr-dr xp]

committed versions in /src and /dist

Thank you guys helping on tracking this bug. ^0^

--
要了几天饱饭就不记得西北风啥味了

[C. Coutinho]

On Sun, Sep 27, 2009 at 09:23:25PM +0800, dr-dr xp wrote:
> committed versions in /src and /dist
>
> Thank you guys helping on tracking this bug. ^0^

Works great.

Cheers,

[dr-dr xp]

: D

--
要了几天饱饭就不记得西北风啥味了

[tyru]

It works well too.
Thanks, drdr.

2009/9/27 dr-dr xp <drd...@gmail.com>:

[dr-dr xp]

: D.

2009/9/28 tyru <tyru...@gmail.com>

--
要了几天饱饭就不记得西北风啥味了

[Vincent B.]

Yes, It's working really well now, congratulations. By curiosity, what
was causing this nasty bug?

On 27 sep, 18:27, dr-dr xp <drdr...@gmail.com> wrote:
> : D.
>
> 2009/9/28 tyru <tyru....@gmail.com>

>
>
>
>
>
> > It works well too.
> > Thanks, drdr.
>

> > 2009/9/27 dr-dr xp <drdr...@gmail.com>:

[dr-dr xp]

‘silent some-command' throws an error but it is caught by try-catch. It seems like that vim keeps staying in "silent mode".

2009/9/28 Vincent B. <twin...@gmail.com>

--
要了几天饱饭就不记得西北风啥味了

[tyru]

Very slow response but I could reproduce the bug.

----- code -----
func! s:foo()
throw 'exception'
endfunc

func! Foo()
try
silent s:foo()
catch
" nop.
endtry
endfunc
----- code -----

":call Foo()" makes Vim stay 'silent mode' as you said.
you can decide whether you send the bug report to vim_dev group as
'hidden command line bug' with this code, or not :)

2009/9/28 dr-dr xp <drd...@gmail.com>:

[dr-dr xp]

I didn't get this bug, except within a (French?) version of vim Vincent sent me. And it is not the latest patched version.

Not sure if it's been fixed in the latest version.

2009/9/29 tyru <tyru...@gmail.com>

--
要了几天饱饭就不记得西北风啥味了

[Vincent B.]

Well the version I've directed you to is a "standard" vim compiled
with the latest patches from the vim mailing list, there's no language
specific bits into it. I've tested the test against the latest vim's
build (7.2.264) and I still get the bug, it may be worth reporting it
to vim_dev .

If nobody wanna report it, I can do it

On 29 sep, 17:56, dr-dr xp <drdr...@gmail.com> wrote:
> I didn't get this bug, except within a (French?) version of vim Vincent sent
> me. And it is not the latest patched version.
>
> Not sure if it's been fixed in the latest version.
>

> 2009/9/29 tyru <tyru....@gmail.com>

>
>
>
>
>
> > Very slow response but I could reproduce the bug.
>
> > ----- code -----
> > func! s:foo()
> > throw 'exception'
> > endfunc
>
> > func! Foo()
> > try
> > silent s:foo()
> > catch
> > " nop.
> > endtry
> > endfunc
> > ----- code -----
>
> > ":call Foo()" makes Vim stay 'silent mode' as you said.
> > you can decide whether you send the bug report to vim_dev group as
> > 'hidden command line bug' with this code, or not :)
>

> > 2009/9/28 dr-dr xp <drdr...@gmail.com>:
> > > 'silent some-command' throws an error but it is caught by try-catch. It

> > > seems like that vim keeps staying in "silent mode".
>

> > > 2009/9/28 Vincent B. <twins...@gmail.com>

[Vincent B.]

Woops, I just saw dr-dr xp question on vim-dev :]

[tyru]

I'm seeing this.
http://groups.google.com/group/vim_dev/browse_thread/thread/331e0c8baeeaef78?hl=en

as Andy Wokula says, ":silent call s:foo()" is right vim script syntax. sorry...
and I found that ":silent call s:foo()" does NOT cause hidden command
line problem.
so what Andy Wokula says is certainly right but certainly there is
this bug. as seeing this group.
to ensure that the bug certainly exists, showing one of the related
posts in xptemplate is good idea, maybe...

related posts in xptemplate google group:
http://groups.google.com/group/xptemplate/browse_thread/thread/a55134d70ef3f29c?hl=en
http://groups.google.com/group/xptemplate/browse_thread/thread/8417ecb6402ee53d?hl=en


I'm finding the another atom code of reproducing the bug...


2009/9/30 Vincent B. <twin...@gmail.com>:

[tyru]

silent call s:foo() == 1
also causes this problem but this is also not right vim script, though...

2009/9/30 tyru <tyru...@gmail.com>:

[dr-dr xp]

Maybe error from 'throw' statement does not cause this bug. but a real vim error does.
I my script, I was trying to unmap a key stroke in that didn't exist in silent mode.

2009/9/30 tyru <tyru...@gmail.com>

--
要了几天饱饭就不记得西北风啥味了

[dr-dr xp]

In my Windows Chinese-simplified I installed this version but the menus are all garbled characters. So I made a guess :)

2009/9/30 Vincent B. <twin...@gmail.com>

--
要了几天饱饭就不记得西北风啥味了

[tyru]

> Maybe error from 'throw' statement does not cause this bug. but a real vim error does.
> I my script, I was trying to unmap a key stroke in that didn't exist in silent mode.

oh, I got it.
and I understood why "silent s:foo()" causes this bug.
because that is not valid statement, that makes Vim stay 'silent mode'.
I see...

---- code ----
func! s:foo(arg)
foobarbaz
endfunc

func! Foo()
try
silent call s:foo()
catch
" nop.
endtry
endfunc
---- code ----

this successfully causes hidden command line bug :)


2009/9/30 dr-dr xp <drd...@gmail.com>:

[tyru]

> this successfully causes hidden command line bug :)

if command 'foobarbaz' is not defined.

2009/9/30 tyru <tyru...@gmail.com>: