Hi Dominique,
I've noticed that pasting a large amount of text in the
Ex command line of Vim-7.3.444 (huge) is very slow.
Performances is quadratic with the number of characters
pasted.
Attached patch speeds it up.
About once a month I will accidentally paste a complete document into
Hi Bram,
Please see the attached patch to fix a simple typo in doc/mlang.txt
(`you can use the this command' should be `you can use this command').
- Peter
--
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
On 26-12-11 10:55, Tony Mechelynck wrote:
Well, why not use a GTK2/Gnome2 Vim GUI? I use that on openSUSE Linux,
and it compiles like a breeze. I'm sure the needed development packages
exist on your Ubuntu distro just like they exist on my openSUSE. I've
seen Ubuntu/Debian users post a oneline
Hi all,
I'm enhancing the syntax/markdown.vim script [1] to support the new text
concealing feature introduced in Vim 7.3. Amongst other things the new
syntax script uses the cchar= option to render list bullets with a
proper Unicode bullet character and common HTML entities as the
Hi all,
Somehow Vim.org doesn't properly initialize cookies or something—I'm not
sure what—and every attempt at logging in just goes back to the login
page (or was it the home page? previously visited page?) /Sometimes/ it
actually succeeds for me, and I don't know why.
This seems to be
Hi Adam,
Awesome, Peter!
Did this ever make it upstream? I've been a big fan of conceal with
other languages (HTML, LaTeX), it would be great to get this patched
into Vim proper.
Sorry for taking a while to respond. No I never specifically submitted
the syntax script for inclusion anywhere,
Hi Peter,
I'm looking for patch #15: Correctly indent wrapped lines in
particular.
The URL is apparently supposed to be
http://groups.google.com/group/vim_dev/web/vim-patches
as referenced by [1], [2] and [3]. That URL simply redirects to
https://groups.google.com/group/vim_dev?hl=en which
Like Ingo I'm sorry I can't get more specific, but that's kind of the
problem: This issue is really hard to diagnose properly because it basically…
seems like syntax folding has some horrible worst case performance which
only shows once in a while, in large buffers, but once it manifests you can
Anyway in the worst case I'll just disable syntax folding for buffers
where line('$') 1000 holds. At least then I still get to enjoy all of
the other goodies Vim has to offer. I'm definitely not switching back to
an IDE :-P. I'll keep vim-dev up to date in case I make any progress on
this issue.
Have you tried the advice at
http://vim.wikia.com/wiki/Keep_folds_closed_while_inserting_text?
It's obviously not originally meant to speed things up, but has that
nice side effect.
I use this tip, and yet occasionally encounter such slowdowns (often when
editing large Vim scripts (ft=vim)).
Have you tried the advice at
http://vim.wikia.com/wiki/Keep_folds_closed_while_inserting_text?
I use this tip, and yet occasionally encounter such slowdowns (often
whenediting large Vim scripts (ft=vim)). There's noticeable delay in
moving the cursor, and insert-completion (i_CTRL-N) is also
By the way, this is other topic, I noticed while testing tag search, tag
completion (i_CTRL-X_CTRL-]) shows !_TAG_XXX tag name. I think that it
should be hidden because it is not useful information.
I've been bothered by the same thing, it would be nice to hide these
entries.
- Peter
--
Please make gVim store ones history when one has multiple instances
open.
I am not sure I understand, what exactly you want. However I believe,
what you want can already be achieved using the :wviminfo command.
See for example here:
http://vimhelp.appspot.com/vim_faq.txt.html#faq-17.3
That's
Please make gVim store ones history when one has multiple instances
open.
I am not sure I understand, what exactly you want. However I believe,
what you want can already be achieved using the :wviminfo command.
See for example here:
http://vimhelp.appspot.com/vim_faq.txt.html#faq-17.3
That's
a good test case for the line wrapping bug, if
indeed it is considered a bug and can be fixed with reasonable effort (I
suppose if concealing can make full screen lines disappear that might
complicate Vim's drawing code significantly...)
- Peter Odding
syntax spell toplevel
setlocal
abbreviated commands
have priority over other commands (:e always means :edit, no matter
which commands starting with :e have been defined)
Good luck if you decide to go through with writing a Vim script parser!
I suspect that your best starting point would be :help eval.txt.
- Peter Odding
--
You
setlocal isk+=@
endif
endif
You can try to reset the iskeyword option after loading the syntax
script to see if that fixes the problem with the following command:
:set iskeywordvim
- Peter Odding
PS. I've never liked how iskeyword is overloaded to have twenty
different meanings; this has
to a small percentage of Vim users because Vim has been ported
to dozens of platforms. Why do you feel the default Vim configuration
should respect $XDG_CONFIG_HOME? (or am I misinterpreting you?)
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
text folding probably won't have it enabled anyway and thus
won't be bothered by the addition.
- Peter Odding
--
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
starts up a lot quicker;
it gives the Exxx: Too many syntax groups about ten seconds after
starting Vim, where previously it would hang for about a minute before
responding.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text
and now it crashes directly after the minute of unresponsiveness, i.e. I
don't need to scroll around to reproduce the crash. I'm attaching a
backtrace.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
reached the bitmap part of the
XPM file Vim crashed. I've tried a few times and it crashes every time,
but only after reaching the bitmap part.
- Peter Odding
--
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
Hi all,
While reading through usr_41.txt I found a typo, please see the attached
patch (based on the latest runtime files from Mercurial).
- Peter Odding
--
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
command and this works fine in
command arguments. In fact using it from the command line was one of my
main use cases because it enables me to do this:
$ gvim note:todo
And I have my to-do list in front of me :-)
- Peter Odding
* https://github.com/xolox/vim-notes/blob/master/notes.vim#L60
Hi Guopeng,
Attached is a Dutch translation of the installer messages. I checked the
Dutch NSIS language file which says its encoded in codepage 1252, so I
saved the attached file in Vim using :write ++enc=cp1252.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do
Patch 7.3.072
Problem:Can't complete file names while ignoring case.
Solution: Add 'wildignorecase'.
Thanks for this patch Bram. This is one of the few things I've missed
every day since I started using Vim some years ago. I just recompiled to
try the patch and it works great!
-
you can preprocess the word list to add variants with
curly quotes or someone could write a Vim patch that automatically does
this internally (a better solution but more complex).
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
Hi Bram,
I just updated my Vim installation to 7.3.027 and can confirm that patch
7.3.025 fixes the problem described in my bug report. Thanks!
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Hi Benjamin,
I've tried your patch and it fixes the problem for me. Thanks a lot!
Without the patch I used to encounter this bug every hour or so...
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
:
$ vim -u NONE --noplugin -NS mksession-E16-bug.vim
I'm also attaching a patch against the latest Vim 7.3 which fixes the
problem for me, however I don't know whether it's the best approach.
- Peter Odding
* http://www.vim.org/scripts/script.php?script_id=3150
--
You received this message from
Hi Carlo,
I can confirm that the much simpler regex you posted also crashes Vim
(in the same way) and that your patch fixes the segmentation fault.
Thanks for taking the time to look into this and posting your patch!
Cheers,
- Peter Odding
--
You received this message from the vim_dev
reasoning about
this but regmatch() is far too complex for my comprehension at the
moment :-)
- Peter Odding
function! s:VimCrashOnRegexEval(tags)
let patterns = []
let short = s:IgnoreHTML('s') . s:IgnoreHTML(':')
let long = s:IgnoreHTML('lt;') . s:IgnoreHTML('[Ss][Ii][Dd]') .
s:IgnoreHTML
is related to which files are published...
- Peter Odding
[1]
http://groups.google.com/group/vim_use/browse_thread/thread/54c88aba79f8b42e/
[2] http://peterodding.com/code/vim/publish/
[3] I followed the instructions in :help debug.txt but didn't realize
that enabling -g doesn't disable strip
(probably an automatic command). This means I get to go through the
whole manual binary search by disabling blocks of code and checking
whether it still crashes ritual. I'll get back to you in a few days
once I've checked every permutation of interacting code in my Vim
profile :-(
- Peter
?!).
- Peter Odding
--
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
viminfo-anonymized
Description: Binary data
just disable modelines for
files that try to set the 'lines' and/or 'columns' options.
- Peter Odding
--
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
.
- Peter Odding
[1] http://peterodding.com/code/vim/lua-inspect/
[2] http://lua-users.org/wiki/LuaInspect
--
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
in insert mode.
Next time paste is broken I'll check whether either of the mappings you
mentioned still works. That would be a good motivation to finally switch
to Vim's cut/copy/paste mappings full time :-)
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post
files don't show up in the output of tagsfiles() and are ignored by
Vim when the 'tags' option is changed by a Vim plug-in automatically.
- Peter Odding
--
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
from the other application (though the paste still
blocks Vim for a while which is extra frustrating).
- Peter Odding
--
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
commands, however they really are supported for user defined commands so
maybe they should be mentioned in the documentation. Attached is a patch
to runtime/doc/map.txt.
- Peter Odding
PS. With my proposed patch map.txt doesn't mention that these values
depend on Vim's +feature-list because
Hi Lech,
After applying your patch I let the shell script below run for 100
iterations and I didn't experience a single crash. Thanks for writing
and posting the patch so quickly!
- Peter Odding
--
ITERATION=1
while gvim -u NONE -U NONE -N --noplugin -S crash.vim example.py
do
sleep 1
with clipboard integration enabled and while this is a great
feature when it works, it also seems to eat my paste buffer once in a
while...
- Peter Odding
--
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
I've tested this with the latest Vim 7.3, that is VIM - Vi IMproved 7.3
(2010 Aug 15, compiled Aug 16 2010 00:25:03). In case this can't be
easily reproduced I've also attached the file backtrace.txt whose
contents are (sometimes) printed to my console when Vim crashes.
- Peter Odding
:-)
- Peter Odding
* http://en.wikipedia.org/wiki/Mojibake
--
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 list,
I just got an E432 error and consulted the documentation which contains
a typo. I've attached a patch against the latest vim-7.3e updated today.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
'\Plug'
\Plug
What Bram is talking about is that the result of \Plug isn't a valid
regular expression because of the embedded special key.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
/ variants) but this might be
too complex?
- Peter Odding
PS. Thanks Dominique and Christian for the patches you've posted, I've
always been annoyed that :setfiletype doesn't support completion :-)
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below
than an hour ago.
- Peter Odding
--
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
diff -r acfb7eddf13c runtime/plugin/tarPlugin.vim
--- a/runtime/plugin
didn't think to check on your
website because the file in question doesn't contain a link to it. I
didn't intent to change one of your scripts behind your back though.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
for file type completion.
- Peter Odding
--
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
intentional, in which case it seems appropriate IMHO
to mention this behavior near :help 'tags' or :help 'suffixesadd'.
- Peter Odding
--
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
version of the netrw plug-in* but now
it's broken in a different way...:
$ vim -u NONE -U NONE -c ':edit http://www.vim.org/'
http://www.vim.org/; Illegal file name
Can anyone tell me how to fix this? Thanks in advance :-)
- Peter Odding
* http://mysite.verizon.net/astronaut/vim
a bug.
- Peter Odding
--
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
gave above, apparently because Vim starts in compatible
mode. Unfortunately given the command line below Vim still starts with
the same gibberish I described in my first e-mail:
vim -u NONE -U NONE -N -c 'let rtp = $VIMRUNTIME | runtime!
plugin/**/*.vim | edit http://www.vim.org/'
- Peter
.
Cheers,
- Peter Odding
--
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
use the following Vim script code to achieve this effect:
:let @/ = 'this is your search pattern'
Documentation for :let @/ = syntax is at :help :let-@
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
.
- Peter Odding
--
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
.
- Peter Odding
A folding expression that folds contiguous pathnames based on common prefix.
function! FoldDirs_Expr(lnum)
let a = split(getline(a:lnum - 1), '/')
let b = split(getline(a:lnum), '/')
let i = 0
while i len(a) i len(b) a[i] == b[i]
let i += 1
endwhile
return i
commands using :! in the wrong working directory...)
Is :drop supposed to ignore the 'autochdir' option or should it be
fixed? I tested with the latest Vim 7.3 and the command line gvim -u
NONE -U NONE --noplugin -N --cmd 'set acd'.
- Peter Odding
--
You received this message from the vim_dev
should be netrwPlugin.vim instead? Attached is a patch that
fixes this.
- Peter Odding
--
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
diff -r e95106e347f6
full screen lines disappear that might
complicate Vim's drawing code significantly...)
- Peter Odding
syntax spell toplevel
setlocal conceallevel=2
runtime! syntax/html.vim
# Headings
syntax match mkdHeading /^#.*/ contains=mkdCode,mkdInlineLink,mkdRefLink
syntax match mkdHeadingMarker /^#\+\s
Bram Moolenaar wrote:
That's easy to fix. I'll do that now.
Great, thanks!
- Peter Odding
--
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
visible the moment :set nomh is done?
I'm using Vim 7.2 (huge) including patches 1-444 and the GTK2-GNOME GUI.
- Peter Odding
* http://synergy2.sourceforge.net/
--
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
in the foreground, thereby stealing Vim's input focus anyway. I
just checked it though and it works perfectly, well almost anyway, the
command prompt window is of course still listed in the task bar.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type
for these g:loaded_* variables until all
plug-ins have been loaded (use the VimEnter autocmd or just test at
runtime).
If the above doesn't help because you really only want to check specific
functions, can't you just call them and catch any E117 errors?
- Peter Odding
--
You received this message from
Hi again tyru,
In case you didn't know / haven't found it yet, you can use the stridx()
function instead: stridx(foo \Plug bar, \Plug) = 0 evaluates to
true.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
and recompiling Vim I can no longer
reproduce the problem described above, however I must admit that I
failed to reliably reproduce the problem in the first place, it would
just occur once in a while when I was testing my session plug-in.
- Peter Odding
--
You received this message from the vim_dev
platforms are now apparently supported!
- Peter Odding
--
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
diff -uNr vim-7.2/runtime/doc/eval.txt{.orig,}
--- vim
up now :-)
- Peter Odding
--
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
of :confirm quit would be more useful for those
few users who bother to use the tab page label context-menu. I realize
this is a minor detail in a keyboard oriented application but Vim is so
good that I can only find details to disagree with ;-)
- Peter Odding
--
You received this message from
. So I'd
check that out before diving too deep into the Vim sources...
- Peter Odding
--
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
be more
specific in what can go wrong?!
- Peter Odding
--
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
Bram Moolenaar wrote:
Patch 7.2.443
Problem:Using taglist() on a tag file with duplicate fields generates an
internal error. (Peter Odding)
Solution: Check for duplicate field names.
Files: src/eval.c, src/proto/eval.pro, src/tag.c
I just updated and recompiled Vim
also the attached screenshot of me executing Ctags from inside Vim
using the system() function, where a command prompt window is clearly
visible while ctags is executing.
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
monitor
on UNIX.
- Peter Odding
--
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
it yourself before trying the plug-in :-)
Thanks for your time,
- Peter Odding
* http://www.vim.org/scripts/script.php?script_id=3114
--
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
checked in my Windows XP SP3 VM and the
command prompt disappears in an instant both with Internet Explorer 8 as
well as Mozilla Firefox 3.6 as the default web browser. I guess that
makes the openurl() function inside the DLL moot :-)
- Peter Odding
* http://vimdoc.sourceforge.net/htmldoc/gui_w32
that corrects this problem
and I've also changed the test instructions to more accurately reflect
the goals of the execute() implementation, you can find both at:
http://www.vim.org/scripts/script.php?script_id=3123
- Peter Odding
--
You received this message from the vim_dev maillist.
Do
.
:endtry
calling taglist()
catched Vim(call):E685: Internal error: hash_add()
Or did I miss another way to do this? By the way, thanks for the time
and effort you're putting into this problem and Vim in general :-)
- Peter Odding
--
You received this message from the vim_dev maillist.
Do not top-post
over my screen :-)
Since you mentioned you can reproduce the problem (and I just saw a mail
by Lech Lorens stating the same) I guess there's no point in polluting
vim_dev with a 900K attachment.
Thanks for your work on Vim!
- Peter Odding
--
You received this message from the vim_dev maillist
. Is this easy to implement
in Vim and do others agree this is a more sensible thing to do?
Thanks for your time,
- Peter Odding
--
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
text and then start the completion because that would
get very annoying very quickly :-)
- Peter Odding
--
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
file to someone who's willing to analyze this problem but I'm not
happy with posting the file on a public mailing list either :-)
Does anyone have suggestions?
Thanks in advance,
- Peter Odding
PS. This is with a freshly compiled 7.2 with patches = 442.
* http://www.vim.org/scripts
with the plug-in to www.vim.org but if
you're interested the README is a bit more readable on my homepage:
* http://www.vim.org/scripts/script.php?script_id=2252
* http://peterodding.com/code/vim/publish/
I hope this somewhat resembles what you had in mind. Have fun! :-)
- Peter Odding
--
You
can finally unlearn Ctrl-Shift-V + Enter when switching between
Vim and OpenOffice :-)
- Peter Odding
--
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
-in :-\
Does anyone know when the service might be available again?
Thanks,
- Peter Odding
--
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
that probably wouldn't be very useful, because you intended
to use remote_foreground(). However wmctrl can also match windows by
their id and title string.
Hope this helps.
- Peter Odding
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org
of the text cursor is off by as many characters as
are backwrapped on the previous virtual lines. It's a shame because I
rather liked the goal of the breakindent patch :-(.
- Peter Odding
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist
are output to PHP, nothing more. So the syntax
highlighting shown by Vim is correct and apparently the Topstyle editor
does the wrong thing here.
- Peter Odding
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http
90 matches
Mail list logo
