Crash of module (haskell) snippet

[Vincent B.]

I got an error when I try to fire the module snippet of haskell,
replacement is not made and many errors arise on the command line.

How can I fix it?

[dr-dr xp]

what's your operation system? and vim version?

what is the first error arised? And give me your .vimrc file.

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

[Vincent B.]

Hello
This morning I've dug the problem and found a conflict with one of
my other installed plugin :
- searchfold 0.7
Both plugins use a function called F(), so making the whole thing
crash. For the moment, I've removed the searchfold plugin, but it
would be nice to get a workaround one way or another.

I've noticed another problem, after using a snippet, I can't see my
command line anymore. I can type in it, and use it, but in blind
mode... Is it normal?

On Sep 17, 4:52 am, dr-dr xp <drdr...@gmail.com> wrote:
> what's your operation system? and vim version?
>
> what is the first error arised? And give me your .vimrc file.
>

[dr-dr xp]

Thank you Vincent for the information about this bug :).  I used 'F' as local function reference I think. Maybe I was wrong.

The command line problem, I did not have ever seen it. What is your .vimrc setting?. And what about using command before template rendering finished? I'm not sure when command line disappears, when template triggered or finished?

And do you use ruler or statusline? XPT creates a fake statusline or ruler. it may cover cmdline.

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

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

[tyru]

hi.

> I've noticed another problem, after using a snippet, I can't see my
> command line anymore. I can type in it, and use it, but in blind
> mode... Is it normal?

I also met this bug.
my .vimrc is here:
http://github.com/tyru/dotfiles/blob/master/.vimrc

it is so long that I will show only xptemplate's setting.
my setting is only this line.

let xptemplate_key = '<C-t>'

[tyru]

> I'm not sure when command line disappears, when template triggered or
> finished?

when template finished.

> And do you use ruler or statusline? XPT creates a fake statusline or ruler.
> it may cover cmdline.

I use both ruler and statusline.


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

[Vincent B.]

Hmm,
I use statusline, regarding the statsline, my .vimrc contain :

set statusline=%F%m%r%h%w\ [%{&ff}:%{&enc}:%Y]\ [ASCII=\%03.3b:0x\
%02.2B]%=Pos=%l,%02v\ -\ %p%%\/%L
set laststatus=2

The --INSERT-- information also disapear. But beside of that, I find
the new highlighting really neat :)

On Sep 17, 12:32 pm, dr-dr xp <drdr...@gmail.com> wrote:
> Thank you Vincent for the information about this bug :). I used 'F' as
> local function reference I think. Maybe I was wrong.
>
> The command line problem, I did not have ever seen it. What is your .vimrc
> setting?. And what about using command before template rendering finished?
> I'm not sure when command line disappears, when template triggered or
> finished?
>
> And do you use ruler or statusline? XPT creates a fake statusline or ruler.
> it may cover cmdline.
>

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

[dr-dr xp]

Can not reproduce this problem in my ubuntu box. Tyru use Windows right?

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

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

[tyru]

no.
that problem occurs on Linux(CentOS) and Vim 7.2.
now I tested also on Windows and Vim 7.1, it does not appear.

my statusline is here:
-------------------------------------
set statusline=%f%m%r%h%w\ [%{&fenc}][%{&ff}]\ [%p%%][%l/%L]\
[%{ShrinkPath('%:p:h',20)}]

func! ShrinkPath( path, maxwidth )
let path = expand( a:path )

" split current directory into 'dirs'.
if has( 'win32' )
let sep = "\\"
else
let sep = "/"
endif
let dirs = reverse( split( path, sep ) ) " 後ろから参照

let path_str = ''
for dir in dirs
if path_str == ''
let path_str = dir . path_str
else
let path_str = dir . sep . path_str
endif

if strlen( path_str ) > a:maxwidth
let path_str = strpart( path_str, strlen( path_str ) -
a:maxwidth - 3 )
let path_str = "..." . path_str
break
endif
endfor

return path_str
endfunc
-------------------------------------

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

[tyru]

I also tested on Ubuntu :)
...and surprisingly, that problem does NOT occur on Ubuntu's Vim.

Ubuntu's Vim version is 7.2, included patches: 1-79.
CentOS Vim is 7.2, included patches: 1-259.
and recently I built Vim from subversion's latest source on CentOS.

so maybe, this is the bug of latest version of Vim...?


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

[Vincent B.]

Hmm well maybe,
I got vim 7.2 with patches 1-234 under windows, so it may be due to a
bug in vim between 79 & 234 :-/

On Sep 17, 1:49 pm, tyru <tyru....@gmail.com> wrote:
> I also tested on Ubuntu :)
> ...and surprisingly, that problem does NOT occur on Ubuntu's Vim.
>
> Ubuntu's Vim version is 7.2, included patches: 1-79.
> CentOS Vim is 7.2, included patches: 1-259.
> and recently I built Vim from subversion's latest source on CentOS.
>
> so maybe, this is the bug of latest version of Vim...?
>

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

>
> > Can not reproduce this problem in my ubuntu box. Tyru use Windows right?
>

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

[dr-dr xp]

Well.. then just ignore this problem?

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

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

[dr-dr xp]

My vim version is:
Included patches: 1, 3-4, 7-9, 11, 13-17, 19-26, 29-31, 34-44, 47, 50-56, 58-64, 66-73, 75, 77-92, 94-107, 109, 202, 234-235, 237

And works well till now.

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

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

[tyru]

on CentOS, I installed older Vim 7.0 from yum.
and that behavior like disappearing statusline does not appear.
all goes well.

> Well.. then just ignore this problem?

I think you should send this bug vim-dev mailing list.


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

[Vincent B.]

I've searched the patches, and the patches which may be related are :
095, 112, 119 and 163

The 119 may be the nearest

On Sep 17, 2:08 pm, tyru <tyru....@gmail.com> wrote:
> on CentOS, I installed older Vim 7.0 from yum.
> and that behavior like disappearing statusline does not appear.
> all goes well.
>
> > Well.. then just ignore this problem?
>
> I think you should send this bug vim-dev mailing list.
>

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

>
> > Well.. then just ignore this problem?
>

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

>
> >> I also tested on Ubuntu :)
> >> ...and surprisingly, that problem does NOT occur on Ubuntu's Vim.
>
> >> Ubuntu's Vim version is 7.2, included patches: 1-79.
> >> CentOS Vim is 7.2, included patches: 1-259.
> >> and recently I built Vim from subversion's latest source on CentOS.
>
> >> so maybe, this is the bug of latest version of Vim...?
>

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

> >> > Can not reproduce this problem in my ubuntu box. Tyru use Windows right?
>

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

[Vincent B.]

I've found a workaround to the "blindness", if vim show an error
message in the command line, it seem to restore the correct behavior,
so typing :
echoe ""
remove the problem. It may be worth to add it

On Sep 17, 1:55 pm, dr-dr xp <drdr...@gmail.com> wrote:
> Well.. then just ignore this problem?
>

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

>
>
>
>
>
> > I also tested on Ubuntu :)
> > ...and surprisingly, that problem does NOT occur on Ubuntu's Vim.
>
> > Ubuntu's Vim version is 7.2, included patches: 1-79.
> > CentOS Vim is 7.2, included patches: 1-259.
> > and recently I built Vim from subversion's latest source on CentOS.
>
> > so maybe, this is the bug of latest version of Vim...?
>

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

> > > Can not reproduce this problem in my ubuntu box. Tyru use Windows right?
>

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

[tyru]

when I was finding the part which can reproduce this Vim bug from xptemplate,
I was confused to the problem that this bug disappeared...
I had been inserting 'echoerr "..."' all around.
so Vim's bug would not appeared :D


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

[dr-dr xp]

A bit problem, echoe prints out function call stack and prompt to wait for a <ENTER> pressed.
what about echom?

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

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

[dr-dr xp]

I mean, echoe in function.

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

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

[Vincent B.]

Hmm i've tried echo, echohl, echom without any success, only echoe
seem to "chocke" the command line and restore the first behaviour

On 17 sep, 15:21, dr-dr xp <drdr...@gmail.com> wrote:
> A bit problem, echoe prints out function call stack and prompt to wait for a
> <ENTER> pressed.
> what about echom?
>

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

[tyru]

trapping an error with "try ~ endtry" also does not work.
it seems to be necessary to display an error to command line...


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

[tyru]

in this case, ignoring this version's Vim is the better way, I think...


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

[dr-dr xp]

I've committed a patched version to /src.

It may helps, but there still be an about 5 seconds delay until command line displays --inser--.

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

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

[dr-dr xp]

well..forget this issure.

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

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

[dr-dr xp]

Thank all of you help

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

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