Bug: Can't select bottom window by mouse-clicking
Can't select bottom window by mouse-clicking Happens every time. How to reproduce: 1. :set ch=2 wmh=0 wh= don't know if relevant 2. Open at least two horizontally split windows 3. Make some window current, other than the bottom one 4. Click the bottom status line. Actual result: Nothing happens. Expected result: Bottom window should become current, as with ^Wb Additional info: - Selecting by mouse works for any window other than the bottom one. - :version output: VIM - Vi IMproved 7.0 (2006 May 7, compiled Jul 23 2006 22:50:51) Included patches: 1-42 Compiled by [EMAIL PROTECTED] Huge version with GTK2-GNOME GUI. Features included (+) or not (-): +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile -python +quickfix +reltime +rightleft +ruby +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl +terminfo +termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save system vimrc file: $VIM/vimrc user vimrc file: $HOME/.vimrc user exrc file: $HOME/.exrc system gvimrc file: $VIM/gvimrc user gvimrc file: $HOME/.gvimrc system menu file: $VIMRUNTIME/menu.vim fall-back for $VIM: /usr/local/share/vim Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -I/opt/gnome/include/gtk-2.0 -I/opt/gnome/lib/gtk-2.0/include -I/usr/X11R6/include -I/opt/gnome/include/atk-1.0 -I/opt/gnome/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/freetype2/config -I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include -DORBIT2=1 -pthread -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -I/usr/include/libart-2.0 -I/usr/include/libxml2 -I/opt/gnome/include/libgnomeui-2.0 -I/opt/gnome/include/libgnome-2.0 -I/opt/gnome/include/libgnomecanvas-2.0 -I/opt/gnome/include/gtk-2.0 -I/opt/gnome/include/gconf/2 -I/opt/gnome/include/libbonoboui-2.0 -I/opt/gnome/include/glib-2.0 -I/opt/gnome/lib/glib-2.0/include -I/opt/gnome/include/orbit-2.0 -I/opt/gnome/include/libbonobo-2.0 -I/opt/gnome/include/gnome-vfs-2.0 -I/opt/gnome/lib/gnome-vfs-2.0/include -I/opt/gnome/include/bonobo-activation-2.0 -I/opt/gnome/include/pango-1.0 -I/usr/include/freetype2 -I/opt/gnome/lib/gtk-2.0/include -I/usr/X11R6/include -I/opt/gnome/include/atk-1.0 -I/usr/include/freetype2/config -O2 -fno-strength-reduce -Wall -I/usr/X11R6/include -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBUGGING -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.6/i586-linux-thread-multi/CORE -I/usr/include -D_LARGEFILE64_SOURCE=1 -I/usr/lib/ruby/1.8/i686-linux Linking: gcc -L/opt/gnome/lib -L/usr/X11R6/lib -rdynamic -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.8.6/i586-linux-thread-multi/CORE -L/usr/local/lib -o vim -L/opt/gnome/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -L/opt/gnome/lib -L/usr/X11R6/lib -lgnomeui-2 -lbonoboui-2 -lxml2 -lz -lgnomecanvas-2 -lgnome-2 -lpopt -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgnomevfs-2 -lbonobo-2 -lgconf-2 -lbonobo-activation -lORBit-2 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lXt -lncurses -lgpm -Wl,-E -Wl,-rpath,/usr/lib/perl5/5.8.6/i586-linux-thread-multi/CORE /usr/lib/perl5/5.8.6/i586-linux-thread-multi/auto/DynaLoader/DynaLoader.a -L/usr/lib/perl5/5.8.6/i586-linux-thread-multi/CORE -lperl -lutil -lc -L/usr/lib -ltcl8.4 -lieee -lruby -lm Best regards, Tony.
Re: vim server ? security hole?
On 7/28/06, Marc Weber [EMAIL PROTECTED] wrote: In case it's a still a vim issue or we don't wont it it would be easy to add a accept_remote_orders_from_different_user and let vim send not only the command but also the username so the server might check.. I'll try to investigate some more time to get to know wether it's as easy as this to find a running shell and send some keys to it. Wait...can other users send commands to my Vim? Yes, as it turns out, they can. That is definitely a /big/ security issue. Bram, this has to be amended immediately. If other users should be able to connect to a remote Vim, then at least there should be some kind of user/password scheme that the user starting the server can set up. Allowing anyone to connect to another Vim is definitely not good. nikolai
Re: vim server ? security hole?
On 7/28/06, Nikolai Weibull [EMAIL PROTECTED] wrote: On 7/27/06, Bram Moolenaar [EMAIL PROTECTED] wrote: Vim uses the X server for communication. Only users with write access to the X server can send a message to Vim. And if you have write access, you are also able to send keystrokes to another process, thus you can do anything anyway. E.g., by sending keystrokes to an xterm in which a shell is running. That is, I think it works this way. Perhaps someone with more detailed knowledge of X server access restrictions can give a better answer. Actually, you have to explicitly allow the sending of synthetic keystrokes to an xterm (the allowSendEvents resource). Via 'editres protocol', you can remotely manipulate resources of running xterm (because xterm is Xt application). I believe that it is possible to turn remotely this allowSendEvents of xterm (if one has X server access). Unless this allowSendEvents is treated differently than other resources; I did not try to write working example. I don't care, I always run with 'xhost +'. I don't know, but perhaps Vim needs to have something similar. Vim has something similar: gvim --servername disables clientserver in gvim. Yakov
Re: spell does not work for doxygen comments version 7
Bill McCarthy wrote: Carlos Beltran wrote: BTW Sourceforge has change its naming policy. It seems that the link for the cvs is now: http://vim.cvs.sourceforge.net/vim/ The link in the http://www.vim.org/cvs.php is thus incorrent. Annoying, SF keeps changing things... I'll fix the link. CVS hasn't worked here for many months. I go to C:\vim\vim70_cvs and type: cvs -z3 up -PdC I see that the file CVS\root contains: :pserver:[EMAIL PROTECTED]:/cvsroot/vim Does that line need to be changed. If so, to what and do I need to change all 83 of these root files? Simplest is to delete the whole tree and start again with pserver:[EMAIL PROTECTED]:/cvsroot/vim I don't know if there is a CVS command to tell it to use a different server URL. Otherwise you could change them in the CVS directories, I think that works fine. -- hundred-and-one symptoms of being an internet addict: 79. All of your most erotic dreams have a scrollbar at the right side. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\download, build and distribute -- http://www.A-A-P.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org///
ctags for win32
I'm looking to get the latest version of ctags for win32. There doesn't appear to be a binary on sourceforge. Or am I just being dense? Cheers, Brett
Re: ctags for win32
Brett Calcott wrote: I'm looking to get the latest version of ctags for win32. There doesn't appear to be a binary on sourceforge. Or am I just being dense? Cheers, Brett From what I see at Sourceforge, version 5.6 of exuberant ctags isn't yet available for Windows. I suppose you can use version 5.5.4 while waiting for the 5.6 Windows release; or else, you might be able to compile a Cygwin-only version of 5.6. It is not obvious to me whether the 5.5.4 release .zip is source-only or includes the executable but that difference should be a minor problem. See http://sourceforge.net/project/showfiles.php?group_id=6556package_id=6631 Best regards, Tony.
Re: ctags for win32
Hi, I had some problems to send my previous mail to the vim list, sorry if you have already received this mail. Someone on the ctags-users mailing list has posted a ctags win32 binary (topic Binary for Windows NT/2000/XP and OS/2 (version 5.6).), here is the link to this binary built with MSVC 6.0: http://mb9x.ginps.com/files/ctags_w32_5-6.zip Regards, Vissale PS: ctags 5.6 can also be built with MSVC 2005 2006/7/28, A.J.Mechelynck [EMAIL PROTECTED]: Brett Calcott wrote: I'm looking to get the latest version of ctags for win32. There doesn't appear to be a binary on sourceforge. Or am I just being dense? Cheers, Brett From what I see at Sourceforge, version 5.6 of exuberant ctags isn't yet available for Windows. I suppose you can use version 5.5.4 while waiting for the 5.6 Windows release; or else, you might be able to compile a Cygwin-only version of 5.6. It is not obvious to me whether the 5.5.4 release .zip is source-only or includes the executable but that difference should be a minor problem. See http://sourceforge.net/project/showfiles.php?group_id=6556package_id=6631 Best regards, Tony.
Re: get the umlauts right
Tobias Herp wrote:
A.J.Mechelynck [EMAIL PROTECTED] wrote:
Tobias Herp wrote:
I' struggling for quite a while now to get the character encoding right;
What does your Vim say on this file in reply to
:verbose set enc? fenc? fencs?
?
encoding=latin1
fileencoding=
fileencodings=ucs-bom
-- To set 'fileencoding' to something else than what Vim would normally
expect, use the ++enc option to :edit, see :help ++opt.
Doing a :e ++enc=utf8 % helped, thanks!
When opening the file from the commandline, gvim +set enc=utf8 {filename}
works (tested on Windows)
-- To force recognition of a file as Unicode (e.g., UTF-8), use
:setlocal bomb on it; then check that 'fileencoding' is setlocal'ed to
some Unicode encoding (such as utf-8) and save.
This didn't work for me.
-- To force recognition of a file as not UTF-8 but Latin1 (assuming
'fileencodings' [plural] is set to ucs-bom,utf-8,latin1), put a number
of upper-ASCII bytes (bytes 127) near the beginning, maybe in a
comment. If the file is a text file, you can also use it as weird
underlining (e.g. underline your main title with a row of
(pounds
sterling) or of Danish (slashed O's); then :setlocal
fenc=latin1
and save. The following works well in one of my text files:
-
# zim: set fenc=latin1 nomod : £µ
# zim (not vim) above is intentional
-
I didn't understand this dirty little trick completely. Is the set fenc=latin1
nomod of any relevance, then, except as a reminder?
It's just a reminder: by changing zim to vim the line would be a Vim
modeline, but this way Vim doesn't take it as such; what does the
trick is the comment (whose bytes, as encoded in Latin1, are
illegal in UTF-8 and thus trigger the reject side of Vim's UTF-8
encoding-recognition algorithm). Any string of repeated bytes in the
range 128-255 would work just as well IIUC. I wrote a tip at vim-online
a few days ago about this trick:
http://vim.sourceforge.net/tips/tip.php?tip_id=1288
see
:help modeline
:help 'fileencodings'
:help 'fileencoding'
:help 'encoding'
:help encoding-table
Anyway, I finally inserted a line
set fencs=ucs-bom,utf-8,latin1
into my _vimrc file, and everything seams to work fine now. Thanks a lot!
My pleasure.
Best regards,
Tony.
Running python scripts from Vim
Hi I'm looking for a vimscript where I can easily test out my Python code by pressing say F9 or some other function key. I have used the runscript.vim script (http://www.vim.org/scripts/script.php%3Fscript_id=127) This script has some nice things, but the main problem is that when an error happens in the script it is not caught. I would like to use quickfix and :copen to get the errors and to be able to jump to them. Does anything like this exist? Thanks in advance Preben
Re: Running python scripts from Vim
Marc Weber [EMAIL PROTECTED] wrote on 28/07/2006 (13:27) : I can't see your problem. Why not just create some mappings: compiler python set makeprg=python :make mypyfile or :make % ? What's wrong with this? lack of a propper efm. But I just managed to fix an old python compiler script which was buggy on windows. (Found some info in an perl compiler script) It also has and efm which looks to be reasonable for now. I'll have a look at it in the weekend. Now it is only to make a ftplugin with the functionality of runscript so that one can set which file is the master file to run through python. A python vimball would be very nice... (Like the Ada vimball) I have now tried several vim scripts for python to set up vim as a good python IDE. It has taken some time due to that not all scripts are well documented and there are some old buggy scripts that makes other scripts not work. But now it really starts to shape up :-) Thanks Preben
creating a new file in the Explorer
Hi, In the vim Explorer (:Explore), I can create a new directory by pressing 'd' and typing the directoryname. Is there something similar for creating a new, empty file? I've looked through the documentation but couldn't find anything. I now press 'c' and type :new filename, but that's error-prone (I usually forget to press 'c' and end up with a file in the wrong directory). Thanks. cheers, roel
Visual select / paste behaviour
Hi, Take the following example: file file_id=myidc:\test.txt/file When the cursor is on the 'm' of 'myid' and I press 'vw', a word is selected in visual mode. However, the at the end of 'myid' is also selected. How do I change the list of 'word separators'? On a related note, when I have 'myid' selected and I want to replace it with the contents of the yank buffer, I press 'p'. But the original contents of the yank buffer are then replaced my 'myid', i.e. the text that was replaced in the paste operation. How do I change this behaviour? Do I have to write a macro to override the paste behaviour in visual mode or is there another way? Thanks. cheers, roel
Re: Visual select / paste behaviour
Hi, Roel Vanhout wrote: Take the following example: file file_id=myidc:\test.txt/file When the cursor is on the 'm' of 'myid' and I press 'vw', a word is selected in visual mode. However, the at the end of 'myid' is also selected. How do I change the list of 'word separators'? to be exact 'w' in visual word does NOT select a word but it extends the current selection to the START of the next word (for a definition of word see :help word). So in your case 'viw' would be better. This starts visual mode and selects the Inner Word. This works on any letter of myid and does not select the following quote. Regards, Jürgen -- Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. (Calvin)
Re: Visual select / paste behaviour
file file_id=myidc:\test.txt/file When the cursor is on the 'm' of 'myid' and I press 'vw', a word is selected in visual mode. However, the at the end of 'myid' is also selected. How do I change the list of 'word separators'? Well, the answer to your question is that there's a setting called 'iskeyword' to which you can add and from which you can remove characters. However, by default, it doesn't include the double-quote character. What you're seeing is an expression of that range from the drop-point m *up to, but not including* where the cursor is (on the quote). If you follow your vw example with y to yank it, and then paste it elsewhere, you'll see that the selection was accurately just myid, not myid On a related note, when I have 'myid' selected and I want to replace it with the contents of the yank buffer, I press 'p'. But the original contents of the yank buffer are then replaced my 'myid', i.e. the text that was replaced in the paste operation. How do I change this behaviour? The best solution I know is to use _p instead of just p. This sends the deleted text (the stuff you previously had highlighted) into the black-hole register, leaving your default register untouched. Alternatively, register 0 is the last yanked text register, which is unaffected by such deletes--only yanks. Thus, you could use (and easily map) 0p to always paste the last thing you yanked. This has two side effects of which it's best to be aware: It does change your default (unnamed) register to the most recently replaced text; and if you delete something (rather than yank something) with the intent to use it later for overwriting a visual block, you'll get unexpected results, as you're pasting the last *yanked* thing, rather than the last *deleted* thing. For more info, you can read at :help _ :help 0 :help v_p Hope this helps you find a solution to what you're trying to do. -tim
RE: creating a new file in the Explorer
Uhmm. It would be nice also to be able to rename files. Carlos. -Original Message- From: Roel Vanhout [mailto:[EMAIL PROTECTED] Sent: Friday, July 28, 2006 2:38 PM To: vim@vim.org Subject: creating a new file in the Explorer Hi, In the vim Explorer (:Explore), I can create a new directory by pressing 'd' and typing the directoryname. Is there something similar for creating a new, empty file? I've looked through the documentation but couldn't find anything. I now press 'c' and type :new filename, but that's error-prone (I usually forget to press 'c' and end up with a file in the wrong directory). Thanks. cheers, roel
Re: creating a new file in the Explorer
Roel Vanhout wrote: Hi, In the vim Explorer (:Explore), I can create a new directory by pressing 'd' and typing the directoryname. Is there something similar for creating a new, empty file? I've looked through the documentation but couldn't find anything. I now press 'c' and type :new filename, but that's error-prone (I usually forget to press 'c' and end up with a file in the wrong directory). Thanks. cheers, roel :mapF2 :cd %:p:h Bar newSpace will allow you to open a new file in the currently browsed directory, or, if currently not browsing a directory, in the same directory as the current file. (Replace F2 by any other shortcut key you want to use.) The cursor ends up on the command line, ready for you to enter the filename. Hit Enter without a filename to open a [No Name] buffer; hit Esc to cancel. The current dir is set to the dir being browsed (or to the dir of the current file) as a side-effect. If there already is a file or subdirectory by the name you give, you end up editing that file (or browsing that subdirectory) in a new split window. Best regards, Tony.
Re: Visual select / paste behaviour
Tim Chase wrote: file file_id=myidc:\test.txt/file When the cursor is on the 'm' of 'myid' and I press 'vw', a word is selected in visual mode. However, the at the end of 'myid' is also selected. How do I change the list of 'word separators'? Well, the answer to your question is that there's a setting called 'iskeyword' to which you can add and from which you can remove characters. However, by default, it doesn't include the double-quote character. What you're seeing is an expression of that range from the drop-point m *up to, but not including* where the cursor is (on the quote). If you follow your vw example with y to yank it, and then paste it elsewhere, you'll see that the selection was accurately just myid, not myid Thanks, this is indeed the setting I'm looking for. However it seems that the w motion *is* inclusive, at least on my installation. Here's what :set iskeyword says: iskeyword=@,48-57,_,192-255 (which is the default, I did a 'set nocp' to make sure it was reset to the default, as per the docs). Now when I repeat putting the cursor on 'm' and pressing 'w', the is selected, as confirmed by yanking and pasting and seeing 'myid' being pasted. This is not what the documentation says should happen, so I looking around for any mappings of w to something but as far as I can tell, no such mapping is available. For the record, I'm using gvim 7 of may 7th, according to :version. I've tried starting gvim without loading a vimrc, but I get the same behaviour. Anyone else seeing this? Am I picking up side effects from other settings somehow? On a related note, when I have 'myid' selected and I want to replace it with the contents of the yank buffer, I press 'p'. But the original contents of the yank buffer are then replaced my 'myid', i.e. the text that was replaced in the paste operation. How do I change this behaviour? The best solution I know is to use _p For more info, you can read at :help _ :help 0 :help v_p Hope this helps you find a solution to what you're trying to do. Thanks, I'll investigate this, I think I can work something out from here. cheers, roel
Re: creating a new file in the Explorer
A.J.Mechelynck wrote: In the vim Explorer (:Explore), I can create a new directory by pressing 'd' and typing the directoryname. Is there something similar for creating a new, empty file? I've looked through the documentation :mapF2:cd %:p:h Bar newSpace will allow you to open a new file in the currently browsed directory, or, if currently not browsing a directory, in the same directory as the current file. (Replace F2 by any other shortcut key you want to use.) The cursor ends up on the command line, ready for you to enter the filename. Hit Enter without a filename to open a [No Name] buffer; hit Esc to cancel. This is great, thanks. Is there also a way to make this work only in the Explorer window/mode? cheers, roel
Re: Running python scripts from Vim
On Fri, Jul 28, 2006 at 01:46:46PM +0200, Preben Randhol wrote: I have now tried several vim scripts for python to set up vim as a good python IDE. It has taken some time due to that not all scripts are well documented and there are some old buggy scripts that makes other scripts not work. But now it really starts to shape up :-) If you have some time, could you please share this recipe with the list? Thanks! Tom Purl
Re: Visual select / paste behaviour
[Resending this because I noticed that the original mail had been encoded with base64 by either my mail client or a server on the way to the mailing list.] Hi, Roel Vanhout wrote: Take the following example: file file_id=myidc:\test.txt/file When the cursor is on the 'm' of 'myid' and I press 'vw', a word is selected in visual mode. However, the at the end of 'myid' is also selected. How do I change the list of 'word separators'? to be exact 'w' in visual word does NOT select a word but it extends the current selection to the START of the next word (for a definition of word see :help word). So in your case 'viw' would be better. This starts visual mode and selects the Inner Word. This works on any letter of myid and does not select the following quote. Regards, Jürgen -- Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. (Calvin)
Re: creating a new file in the Explorer
Roel Vanhout wrote: In the vim Explorer (:Explore), I can create a new directory by pressing 'd' and typing the directoryname. Is there something similar for creating a new, empty file? I've looked through the documentation but couldn't find anything. I now press 'c' and type :new filename, but that's error-prone (I usually forget to press 'c' and end up with a file in the wrong directory). Thanks. Have you considered having let g:netrw_keepdir= 0 in your .vimrc? That way the current directory (:pwd) will track what netrw uses for the current directory, and so creating a new empty file (:enew, for example) will be made in the directory you're expecting. Regards, Chip Campbell
Re: creating a new file in the Explorer
Carlos Beltran wrote: Uhmm. It would be nice also to be able to rename files. :he netrw-R Regards, Chip Campbell
Re: creating a new file in the Explorer
Roel Vanhout wrote: A.J.Mechelynck wrote: In the vim Explorer (:Explore), I can create a new directory by pressing 'd' and typing the directoryname. Is there something similar for creating a new, empty file? I've looked through the documentation :mapF2:cd %:p:h Bar newSpace will allow you to open a new file in the currently browsed directory, or, if currently not browsing a directory, in the same directory as the current file. (Replace F2 by any other shortcut key you want to use.) The cursor ends up on the command line, ready for you to enter the filename. Hit Enter without a filename to open a [No Name] buffer; hit Esc to cancel. This is great, thanks. Is there also a way to make this work only in the Explorer window/mode? cheers, roel Maybe, but I doubt if it's worth it. Maybe something like (untested) :au BufNew * if isdirectory(amatch) | map buffer F2 :cd %:p:h Bar newSpace| endif which must be typed all on one line. In that previous post, I had tried to create a mapping that would give useful results even if used outside the netrw (Explorer) window. Best regards, Tony.
Re: Running python scripts from Vim
On Fri, Jul 28, 2006 at 01:46:46PM +0200, Preben Randhol wrote: I have now tried several vim scripts for python to set up vim as a good python IDE. It has taken some time due to that not all scripts are well documented and there are some old buggy scripts that makes other scripts not work. But now it really starts to shape up :-) You might be interested in trying out PIDA (http://pida.berlios.de/). James -- GPG Key: 1024D/61326D40 2003-09-02 James Vega [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: spell does not work for doxygen comments version 7
On Fri 28-Jul-06 3:14am -0600, Bram Moolenaar wrote: Bill McCarthy wrote: I see that the file CVS\root contains: :pserver:[EMAIL PROTECTED]:/cvsroot/vim Does that line need to be changed. Simplest is to delete the whole tree and start again with pserver:[EMAIL PROTECTED]:/cvsroot/vim I don't know if there is a CVS command to tell it to use a different server URL. Otherwise you could change them in the CVS directories, I think that works fine. From my vim70_cvs directory, I deleted its files and all subdirectories except the top level CVS subdirctory. I modified the root file to contain the pserver line you gave me above and ran. Worked perfectly! Thanks. -- Best regards, Bill
Re: AsNeeded?
Chip, On Thu 27-Jul-06 8:38am -0600, you wrote: AsNeeded uses the FuncUndefined autocommand to transparently load functions. Commands and maps, unfortunately, are not blessed with such an autocommand. Hence AsNeeded provides: :AN map-or-command :ANX map-or-command Thanks for your (and Marc's) explanations. I believe I understand it. Once I removed taglist.vim from being sourced, AsNeeded appeared to work nicely. However, since I cannot seem to get AsNeeded and taglist to play nice together, I cannot use your plugin. -- Best regards, Bill
Re: Syntax files
On 7/28/06, Max Dyckhoff [EMAIL PROTECTED] wrote:
I have placed all the identifiers on a single line with syn keyword
(type) at the beginning. There are two files of keywords (types and
defines/enumerators), which are 250,000 characters and 650,000
characters respectively ...
The way that I am making use of these files is by sourcing them in
after\syntax\c.vim, which means they are loaded every time I open a
file. This becomes mildly annoying, because the load of the file now
takes 2-3 seconds, thanks to the two massive syn keyword lines.
I made some experiements and found that if, instead of
making one 650-kb long commandline (which indeed
takes ~ 2 sec to process) ... if you put, say, 10 keywords
per 'syn keyword' line, then vim sources such 1MB file in:
fanfares
under 0.1 sec.
Amazing feat on vim's part.
(That's my test of 100,000 keywords in 10,000 lines at
10 keywords per each). Note that even though file becomes
longer ('syn keyword' parts gets repeated),
the sourcing time drops sharply.
Apparently what slowed down vim in the 650-kb-command-line-lengthcase was the
length of one commandline itself. Can it be some
kind of record of commandline length ?
Regarding your request to source your after/syntax/c.vim
only once. This is difficult. Syntax is reset and sourced
again for each opened file. But maybe you reconsider
when you remake the c.vim.
Yakov
Re: Visual select / paste behaviour
On Fri, Jul 28, 2006 at 09:48:21AM EDT, Jürgen Krämer wrote: [Resending this because I noticed that the original mail had been encoded with base64 by either my mail client or a server on the way to the mailing list.] Hi, Roel Vanhout wrote: Take the following example: file file_id=myidc:\test.txt/file When the cursor is on the 'm' of 'myid' and I press 'vw', a word is selected in visual mode. However, the at the end of 'myid' is also selected. How do I change the list of 'word separators'? to be exact 'w' in visual word does NOT select a word but it extends the current selection to the START of the next word (for a definition of word see :help word). So in your case 'viw' would be better. This starts visual mode and selects the Inner Word. This works on any letter of myid and does not select the following quote. cool. Thanks cga
errorlist question
Hi When one use :make and one get a list of errors, is it possible to get vim to display the errors in reverse order? The reason is that python gives the traceback of the error like: Traceback (most recent call last): File unittests/dbfacadeTest.py, line 89, in testFoo self.assertEquals(34, dtid) File /usr/lib/python2.2/unittest.py, line 286, in failUnlessEqual raise self.failureException, \ AssertionError: 34 != 33 Usually it is not in the first file that the error is, but the last. I know that in the compiler script one can put a filter to reverse the error message, but I'm looking for a way to reverse it after it has been prosessed through the errorformat and not before. That is not like what was done here: http://mail.python.org/pipermail/python-list/2005-May/282760.html The reason is that the error parsing gets more messy IMHO. Thanks in advance Preben
Vim book
Since a bit has changed in Vim7; does anyone know of a book (in English) in the works for it? :Robert
Re: Clickable error messages
Marc Weber wrote: :Robert See :h quickfix ;) Brief: :compiler perl :set makeprg=perl :make test.pl) If you want to add options to perl use set makeprg=perl\ --option\ blah (escape whitespaces) The quickfix cycle might remove some output.. depending on errorformat. I was waiting for this question because :!perl foo doesn't do what you want :) See also :h compiler If you don't want to look at scrolling lines try my runinbackground script.. (http://www.vim.org/scripts/script.php?script_id=1582) I would also suggest to have some quick glances at :h topics basic editing, advanced editing... Much to read.. or hang around in #vim on irc.freenode.net. You can learn much there... You don't have to read everything but it should give you an idea of what is there .. ;) To took me over a year to learn many features of vim and then think about how can I really fast open the files I need ... and so on Just ask again we'll point to corresponding documentation. Marc Thanks for the info. For some background I used to use the perl-support plugin but it isn't working on OSX Tiger so I thought I would just create a simple perl-utils one that I could add quick functions to and then assign accelerators (i.e. \rr runs it, \rc checks it, \rx criticizes etc.). I have this: function! PerlRun(...) execute !perl . expand(%) endfunction function! PerlCheck(...) execute !perl -cw . expand(%) endfunction These work command! -nargs=* PerlRun call PerlRun() command! -nargs=* PerlCheck call PerlCheck() These aren't working map buffer silent Leaderrr Esc:call PerlRun()CR imap buffer silent Leaderrr Esc:call PerlRun()CR map buffer silent Leaderrc Esc:call PerlCheck()CR imap buffer silent Leaderrc Esc:call PerlCheck()CR I was hoping it would just a little more to get clickable errors. :Robert
Re: Vim book
Robert Hicks wrote: Since a bit has changed in Vim7; does anyone know of a book (in English) in the works for it? You might take a look at http://en.wikibooks.org/wiki/ Learning_vi:Vim. (As for the book plans, I have no idea.) -- Benjamin D. Esham [EMAIL PROTECTED] | AIM: bdesham128 | Jabber: same as e-mail • Still using Internet Explorer? Firefox is newer, more secure, and has better support for standards. http://www.getfirefox.com
