Hi
Syntax highlighting with vim-7.4.580 can be very slow with valgrind
file types. For example, try to open the attached valgrind2.log file
using:
$ vim -u NONE -c 'syntax on' -c 'setfiletype valgrind' valgrind2.log
Notice 2 problems:
1) syntax highlighting is _very_ slow. It takes about 20
Hi Dominique!
On Do, 15 Jan 2015, Dominique Pellé wrote:
Is there a 3000 characters limit in the regexp engine or in syntax
highlighting engine? I could not find any such limit in the source code.
Could that be the synmaxcol setting?
Best,
Christian
--
Alles auf der Welt läßt sich finden,
Hi Bram!
On 2015-01-14 Wednesday at 17:52 +0100 Bram Moolenaar wrote:
Patch 7.4.576
Problem:Redrawing problem with 'relativenumber' and 'linebreak'.
Solution: Temporarily reset 'linebreak' and restore it in more places.
(Christian Brabandt)
This hunk intentionally dropped
Roland Eggner wrote:
On 2015-01-14 Wednesday at 17:52 +0100 Bram Moolenaar wrote:
Patch 7.4.576
Problem:Redrawing problem with 'relativenumber' and 'linebreak'.
Solution: Temporarily reset 'linebreak' and restore it in more places.
(Christian Brabandt)
This hunk
On Mi, 05 Nov 2014, Christian Brabandt wrote:
I'll include the update for now at the usual place:
https://github.com/chrisbra/vim-mq-patches/blob/master/var_tabstops
Updated the patch for v7.4.579
(attached and available at above URL).
Best,
Christian
--
Was aber ist deine Pflicht? Die
Comment #4 on issue 312 by gilad.ar...@gmail.com: word wrapping messed up
when entering Insert mode with 'c' or 's'
https://code.google.com/p/vim/issues/detail?id=312
Verified with 7.4.580, problem is gone. Thanks!
--
You received this message because this project is configured to send all
Comment #6 on issue 313 by fritzoph...@gmail.com: pedit changes cursor
position when BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
I discovered today that although the cursor position is thankfully fixed by
the patch, there is still an error message that
Hi Christian!
On 2015-01-15 Thursday at 23:02 +0100 Christian Brabandt wrote:
On Do, 15 Jan 2015, Roland Eggner wrote:
On 2015-01-14 Wednesday at 17:52 +0100 Bram Moolenaar wrote:
Patch 7.4.576
Problem:Redrawing problem with 'relativenumber' and 'linebreak'.
Solution:
Thank you very much for your quick and detailed answer.
Indeed I've got a mapping jk -- Esc. So most of the findings are
explained very well.
The only thing I still don't get is why the issue can't be seen in gvim.
Regards,
P. Mattern
--
--
You received this message from the vim_dev
Hi,
Peter Mattern schrieb am 15.01.2015 um 23:15:
Thank you very much for your quick and detailed answer.
Indeed I've got a mapping jk -- Esc. So most of the findings are
explained very well.
The only thing I still don't get is why the issue can't be seen in gvim.
I don't do much work
Am 2015-01-16 00:33, schrieb Roland Eggner:
The first entry, already deleted:
Patch to fix relative numbers. (Christian Brabandt, 2014 Nov 17)
Update Nov 26.
That one is not fixed yet (and has not been merged).
It is fixed by the patch attached at that message:
Comment #7 on issue 313 by vega.ja...@gmail.com: pedit changes cursor
position when BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
The error is expected since you're trying to :edit a modified buffer.
--
You received this message because this project is
On Tuesday, January 6, 2015 at 6:15:50 PM UTC-8, h_east wrote:
Hi list,
2015/1/7(Wed) 4:09:31 UTC+9 h_east:
Nice. Perhaps I think that We need a little more modification such an
attached a patch url.
https://gist.github.com/h-east/be555467ddfc3dfb8d54
I updated Gist. (Add line#19)
Comment #8 on issue 313 by fritzoph...@gmail.com: pedit changes cursor
position when BufReadPre autocmd defined
https://code.google.com/p/vim/issues/detail?id=313
Except the buffer is already loaded so it is more like a split. AFAIK there
is no way to open a preview window on the current
Hi tux.,
2015/1/15 Thu 8:02:35 UTC+9 tux. wrote:
Ken Takata schrob am Mittwoch, 14. Januar 2015 um 23:52 Zeit:
Did you set RUBY_VER and RUBY_VER_LONG properly?
MSVC 2010, RUBY_VER = 22, RUBY_VER_LONG = 2.2.0:
I can reproduce Cesar's error.
Please make sure that you are using Ruby
On Thursday, January 15, 2015 at 7:29:16 PM UTC+9, Barry Arthur wrote:
Vimple (https://github.com/dahu/vimple) offers:
:echo string#range('a', 'z')
Well, I don't want plugin. I want builtin function.
FYI, vital.vim is also having char_range
Vimple (https://github.com/dahu/vimple) offers:
:echo string#range('a', 'z')
--
--
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
---
You received this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15-Jan-2015 12:24, mattn wrote:
Well, I don't want plugin. I want builtin function.
Can you demonstrate that this is needed frequently? Which common tasks
would benefit from this? (And why would a short library function not
suffice?)
The only
Am 2015-01-15 10:15, schrieb Ken Takata:
Please make sure that you are using Ruby 2.2's header files.
I use Ruby 2.2.0 compiled with MSVC 2010 by myself. :-)
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For
19 matches
Mail list logo
