Hi,
bootleq wrote:
2011/9/5 James Vega james...@jamessan.com mailto:james...@jamessan.com
On Sun, Sep 04, 2011 at 10:47:53AM +0800, bootleq wrote:
About the automatically added jump:
It' reasonable when undoing a single change.
But if we do many changes at one
Thank you, I can keep jumplist unchanged now.
But back to my first message, the cursor still silently move to first
changed line.
2011/9/5 Jürgen Krämer jottka...@googlemail.com
Hi,
bootleq wrote:
2011/9/5 James Vega james...@jamessan.com mailto:james...@jamessan.com
On Sun,
Hi all,
The following code is highlighted incorrectly when using the cpp filetype:
#if defined FOO
#elif defined BAR
#endif
The part defined BAR is not highlighted, while defined FOO is.
AFAICT, my runtime files are up to date.
I don't know much about Vim syntax files, so I can't tell where
Hi François!
On Mo, 05 Sep 2011, François Ingelrest wrote:
Hi all,
The following code is highlighted incorrectly when using the cpp filetype:
#if defined FOO
#elif defined BAR
#endif
The part defined BAR is not highlighted, while defined FOO is.
AFAICT, my runtime files are up to
with this patch, the snipMate plugin won't work correctly with auto
completio popup.
After applying this patch, the AutoComplPop will popup a list of
snippets for current filetype. This is a little bit annoying. So, I
have to revert to previous one.
On Aug 28, 10:02 pm, Bram Moolenaar
... but what I proposed was to try something simpler, see if it worked as it
was
supposed ...
A minimal example you mean; thank you for pointing me in this way.
Well, after some playing it seems the minimal example is:
:set statusline=%(%#ErrorMsg#xxx%*%)abcde
that is, grouping is used
Hi.
I can't reproduce it.
Please show me
* version of ACP
* version of snipMate
* what the patch of ACP? only GetSnipsInCurrentScope?
* what keys did you type?
Thanks.
On Monday, September 5, 2011 8:29:36 PM UTC+9, 驼峰 wrote:
with this patch, the snipMate plugin won't work correctly with auto
It looks like someone has changed the logic of the longest match in vim
autocompletion. Now it tries to do the longest match after each new
letter entered. And there are some ugly bugs which causes it to
segfault the vim. Not mentioning that it's also very slow now. Looks
like it calls
Patch 7.3.294 (after 7.3.289)
Problem:Patch 289 causes more problems than it solves.
Solution: Rever the patch untill a better solution is found.
Files: src/edit.c
*** ../vim-7.3.293/src/edit.c 2011-08-28 16:02:23.0 +0200
--- src/edit.c 2011-09-05 20:07:49.0 +0200
Some guy calling himself no.snile.face wrote:
[BTW: please use your real name on this maillist]
It looks like someone has changed the logic of the longest match in vim
autocompletion. Now it tries to do the longest match after each new
letter entered. And there are some ugly bugs which
s/Rever /Revert /i
--
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.vim.org/maillist.php
Hi Bram.
I want to know policy of patch including.
Patch#289 is a fix for vim's incomplete feature.
Some plugins has redundant script lines to avoid it. Those are in
unatural ways, makes many lines and waste developer times. Of course,
I
understand that patch#289 causes some troubles for some
patch 289.
Repro steps:
1. install acp and snipMate.
2. open vim and new a buffer.
3. file aa.cpp
4. type Ex at the beginning of line.
all the snippets of C file will be shown.
On Sep 6, 12:51 am, mattn mattn...@gmail.com wrote:
Hi.
I can't reproduce it.
Please show me
* version of ACP
*
BTW, the environments:
acp version: 2.14.1
snipMate version: 0.83
only change snipMate.vim to include GetSnipsInCurrentScope.
--
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
What is your point?
* Showing all snippets is wrong?
* or else?
On Tuesday, September 6, 2011 10:13:21 AM UTC+9, 驼峰 wrote:
patch 289.
Repro steps:
1. install acp and snipMate.
2. open vim and new a buffer.
3. file aa.cpp
4. type Ex at the beginning of line.
all the snippets of C
here is some sample of c.snippets.
# main()
snippet main
int main(int argc, const char *argv[])
{
${1}
return 0;
}
snippet mainn
int main(void)
{
${1}
return 0;
}
# #include ...
snippet
Sorry, I'm not export of snippets.vim, so please explain WHAT IS WRONG.
What should be shown?
What is correct behavior?
And what is wrong?
On Tuesday, September 6, 2011 10:23:18 AM UTC+9, 驼峰 wrote:
here is some sample of c.snippets.
# main()
snippet main
int main(int argc, const char
sorry for the confusion.
When I typing Ex, acp will show all the snipMate triggers for
current file type. This is not expected. The expected behavior is: acp
should only show popup for content included in current buffer instead
of all other triggers for current file type.
Is it clear?
--
Just, I could reproduce it. ;)
Thanks.
Vim did not work correctly to call completefunc since patch7.3.298 .
If leading characters are changed after showing popup, completefunc should
be called in fact.
But completefunc hadn't called.
This is bug of vim that Muraoka pointed.
Thus, acp just need
19 matches
Mail list logo
