Re: how to enable mouse in vim of cygwin
> yes, I like this way. But when I open the vim, it is extremely slow, > it needs about half minute to open a file, what is the problem? try 'vim -X' Yakov yes, it works, thanks! sun
Re: Favorite little-known feature
> What is your favorite little-known Vim feature?
One person's "little-known" feature is another person's
life-blood. :)
There are dark corners and abuses of Ex commands that I exercise
on a regular basis without thinking--when I mention them in an
answer on the list, I occasionally get a "wow, I didn't know that
about Vim" response.
Things like:
-using "*" to repeat the ex-range "'<,'>" so you don't have to
retype type 5 chars
:*s/foo/bar
is the same as
:'<,'>s/foo/bar
-doing complex things with ":g"/":v" commands and the ranges that
follow
-text objects. If you don't know 'em, learn 'em!
-dark corners of the regexp engine...especially back-references
if you've never used them before; and the power of the ":s"
command, along with the "\=" replacement for expression evaluation.
-the ability to sort a range/file by a found regexp rather than
just from the beginning of the line, or a fixed-column offset
Many of the "little-known" features are somewhat obvious upon
thinking about it, but it takes the little push of "Oh, I didn't
know you could combine X with Y and get such powerful behaviors!"
Vim's "{count}{operator}{motion}" syntax means that if you learn
a new {operator}, you can apply pretty much every {motion} you
know to that command. And vice-versa, if you learn a new
{motion}, suddenly you can start using it with all the
{operator}s that you already have.
Those are some of my top items. Many folks know them and use
them regularly, but they're definitely indicators of a "vim power
user".
To read up,
:help cpo-star
:help :g
:help :range
:help :sort
:help text-objects
:help sub-replace-special
:help motion.txt
:help operator
:help motion
-tim
Re: search pattern on sed or grep
Tim Chase wrote: C:\Temp> find /? No patterns other than fixed text Since Windows 2000, there is also the findstr command. It is not as clever as grep, but it supports patterns and is able to efficiently handle big files. In Vim: :helpgrep findstr At Windows command prompt: findstr /? John
Favorite little-known feature
Every once in a while, I discover (either through help files or this list) a relatively little-known feature of vim which really enhances my computing experience. The most recent occurrence of this (thanks to "A.J.Mechelynck) is the netrw feature (:help netrw) which allows one to edit a file over a network connection in a local copy of vim. Wonderful! What is your favorite little-known Vim feature?
Re: how to get gvim to open a file over ssh?
ben lieb wrote: In ubuntu linux: I have a remote (ssh) connection through nautilus (gui file manager). When I right-click a file, I can open, edit and save the file in "text editor" without any problem. When I open the file in gvim, it is empty. What can I do to solve this? Thanks for any help Method I: Edit a local copy, and download/upload it as a separate step. Method II: see :help netrw.txt :help netrw-start :help netrw-scp :help netrw-externapp :help netrw-read :help netrw-write IIUC, in this case every transfer requires inputting a username and password -- at least if you cannot configure the server and client yourself, see :help netrw-listhack Best regards, Tony. -- If little green men land in your back yard, hide any little green women you've got in the house. -- Mike Harding, "The Armchair Anarchist's Almanac"
how to get gvim to open a file over ssh?
In ubuntu linux: I have a remote (ssh) connection through nautilus (gui file manager). When I right-click a file, I can open, edit and save the file in "text editor" without any problem. When I open the file in gvim, it is empty. What can I do to solve this? Thanks for any help
Re: how to enable mouse in vim of cygwin
Gary Johnson wrote: On 2007-05-04, Albie Janse van Rensburg <[EMAIL PROTECTED]> wrote: A.J.Mechelynck wrote: sun wrote: I'm using cygwin and rxvt. It works quite well, since you don't need to start an X server for the application - it just runs. Put the following in your cygwin launcher (cygwin_rxvt.bat for me): > @echo off > C: > chdir C:\cygwin\bin > set SHELL=/bin/bash > rxvt -ls -sr -sl 1500 -fn "Lucida ConsoleP-12" -bg black -fg grey and in your .bashrc: > export TERM="rxvt-cygwin-native" your mouse should work fine with rxvt (mine does!) Cheers Now I can use mouse to jump from one split window to another under rxvx, but how to resize one? I can't do it by mouse in my case, can you? You should be able to drag the status lines and vertical dividers to resize the split windows. I can confirm that this seems to not work, using the cygwin Vim version when run in rxvt. Tab-switching and window selection does work, however. First, thank you to Yakov for the "set mouse=a" suggestion. I've had that in my Unix .vimrc for so long and didn't need in it in my Windows _vimrc for gvim that I forgot about needing it when the mouse didn't work in my Cygwin vim. That fixed the problem completely for the case where I run an xterm on a Linux machine, ssh to my Windows machine, and run Cygwin vim on that Windows machine through that xterm. However, as Sun and Albie have reported, it doesn't fix the whole problem when running Cywin vim in a non-X rxvt running on the Windows machine: I can split a window and select the active window with the mouse, but I still cannot drag the status line. Regards, Gary Just noticed something on this Linux machine: - In gvim I can drag the status line with no problem; - In the linux console (/dev/tty, pure text non-X), with +mouse_gpm and the gpm daemon running, I can too; - In konsole (with +mouse_xterm and $TERM=xterm) I can't. I can select an area by dragging the mouse, but the highlight only appears when I release the button (in gvim and /dev/tty it appears as soon as the mouse moves with Button 1 depressed). It's hard to tell what happens: I might think that Vim-in-xterm only gets mouse events when a button is released: apparently, it never feels mouse moves, and doesn't see a buttondown as long as the buttonup hasn't happened... Clicking (mousedown+mouseup) on a statusline selects the corresponding window, but there's no way I can drag that statusbar -- or the vertical separation between vertically split windows. On the contrary, both gvim and vim-in-non-X-terminal obviously get the buttondowns, drags and buttonups as soon as they happen. Best regards, Tony. -- "I can't complain, but sometimes I still do." -- Joe Walsh
Re: how to enable mouse in vim of cygwin
On 5/4/07, sun <[EMAIL PROTECTED]> wrote: > I'm using cygwin and rxvt. It works quite well, since you don't need to > start an X server for the application - it just runs. > > Put the following in your cygwin launcher (cygwin_rxvt.bat for me): > > > @echo off > > C: > > chdir C:\cygwin\bin > > set SHELL=/bin/bash > > rxvt -ls -sr -sl 1500 -fn "Lucida ConsoleP-12" -bg black -fg grey > > and in your .bashrc: > > > export TERM="rxvt-cygwin-native" > > your mouse should work fine with rxvt (mine does!) > > Cheers yes, I like this way. But when I open the vim, it is extremely slow, it needs about half minute to open a file, what is the problem? try 'vim -X' Yakov
Re: how to enable mouse in vim of cygwin
On 2007-05-04, Albie Janse van Rensburg <[EMAIL PROTECTED]> wrote: > A.J.Mechelynck wrote: > > sun wrote: > >>> I'm using cygwin and rxvt. It works quite well, since you don't need to > >>> start an X server for the application - it just runs. > >>> > >>> Put the following in your cygwin launcher (cygwin_rxvt.bat for me): > >>> > >>> > @echo off > >>> > C: > >>> > chdir C:\cygwin\bin > >>> > set SHELL=/bin/bash > >>> > rxvt -ls -sr -sl 1500 -fn "Lucida ConsoleP-12" -bg black -fg grey > >>> > >>> and in your .bashrc: > >>> > >>> > export TERM="rxvt-cygwin-native" > >>> > >>> your mouse should work fine with rxvt (mine does!) > >>> > >>> Cheers > >> > >> Now I can use mouse to jump from one split window to another under > >> rxvx, but how to resize one? I can't do it by mouse in my case, can > >> you? > > You should be able to drag the status lines and vertical dividers to resize > > the split windows. > I can confirm that this seems to not work, using the cygwin Vim version when > run in rxvt. Tab-switching and window selection does work, however. First, thank you to Yakov for the "set mouse=a" suggestion. I've had that in my Unix .vimrc for so long and didn't need in it in my Windows _vimrc for gvim that I forgot about needing it when the mouse didn't work in my Cygwin vim. That fixed the problem completely for the case where I run an xterm on a Linux machine, ssh to my Windows machine, and run Cygwin vim on that Windows machine through that xterm. However, as Sun and Albie have reported, it doesn't fix the whole problem when running Cywin vim in a non-X rxvt running on the Windows machine: I can split a window and select the active window with the mouse, but I still cannot drag the status line. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: Vim stalls when I try to enable syntax on vimrc (Cream
A.J.Mechelynck wrote: Albie Janse van Rensburg wrote: Steve Hall wrote: From: Albie Janse van Rensburg, Fri, May 04, 2007 6:35 am I recently decided to try out the Cream build (sans Cream) of Vim, with all the new patches (from http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). Now, I seem to be unable to edit my vimrc without bringing Vim to a complete halt! Sound like the age-old and infamous TCL with Cygwin problem: http://tech.groups.yahoo.com/group/vim/message/78505 http://tech.groups.yahoo.com/group/vim/message/78506 (solution) Yep, that's it. I should have mentioned I am using cygwin, I guess. Why does this bug appear on the patched version of Vim, but not the unpatched v7.0? Thanks for the pointer. Another workaround is never to use from Cygwin bash a Vim binary for native-Windows (and never use Vim-for-Cygwin except from within Cygwin). If your Cygwin /bin and /usr/bin aren't in the non-Cygwin PATH, then Vim-for-Windows will find TCL-for-Windows. Since they are added in front at Cygwin bash startup, Vim-for-Cygwin will find TCL-for-Cygwin first. (Vim-for-Windows will, for instance, be vim.exe and gvim.exe from the directory C:\Program Files\Vim\vim70, which is their $VIMRUNTIME. Vim-for-Cygwin will be, for instance, /usr/bin/vim.exe with its $VIMRUNTIME at /usr/share/vim/vim70/.) Vhy isn't it present in Bram's 7.0.000? Err... isn't the latter compiled without TCL support? Then it never looks for a TCL dll. Best regards, Tony. *facepalm* Of course, that all makes sense. I just removed the c:\cygwin\bin directory from my user path, and everything is back to normal. IMHO, this is the better solution, allowing me to use TCL (one day) when I want to, without interfering in an "artificial" way. Thank you very much for the input. -- Albie Janse van Rensburg ~ http://morph.telspace.co.za Please don't send me any MS Word or Powerpoint attachments unless it's absolutely neccessary - send simply text. http://www.gnu.org/philosophy/no-word-attachments.html Well, he thought, since neither Aristotelian Logic nor the disciplines of Science seemed to offer much hope, it's time to go beyond them... Drawing a few deep even breaths, he entered a mental state practiced only by Masters of the Universal Way of Zen. In it his mind floated freely, able to rummage at will among the bits and pieces of data he had absorbed, undistracted by any outside disturbances. Logical structures no longer inhibited him. Pre-conceptions, prejudices, ordinary human standards vanished. All things, those previously trivial as well as those once thought important, became absolutely equal by acquiring an absolute value, revealing relationships not evident to ordinary vision. Like beads strung on a string of their own meaning, each thing pointed to its own common ground of existence, shared by all. Finally, each began to melt into each, staying itself while becoming all others. And Mind no longer contemplated Problem, but became Problem, destroying Subject-Object by becoming them. Time passed, unheeded. Eventually, there was a tentative stirring, then a decisive one, and Nakamura arose, a smile on his face and the light of laughter in his eyes. -- Wayfarer
Re: search pattern on sed or grep
Tim Chase wrote: grep 'rs10946498' chr6.txt | grep -v 'rs10946498.*rs10946498' > out.txt Sed might allow it in one pass with something like sed -e '/rs10946398/!d' -e '/rs10946398.*rs10946398/d' chr6.txt > out.txt Still try to migrate from Windows to linux, but hopefully will done it someday! Since you have a fixed pattern (as Tony mentioned about using fgrep), you can do at least the first variant in native windows/dos with C:\Temp> find "rs10946398" chr6.txt > out.txt without the need for sed/grep at all. The dos "find" command is a bit like "grep" with all the cool functionality removed. The resulting file would hopefully be small enough that vim/ed could handle the resulting out.txt file. You can learn more by issuing C:\Temp> find /? No patterns other than fixed text, but sometimes that's all you need. And 640k oughta be enough for anyone ;) -tim (now only running Windows at work, but Linux, OpenBSD and Mac OS X at home) I never thought of using find under cmd. I'm not very into computers but as long as I remember cmd (and DOS) generally can handle data of 640K at one batch meaning that it would need many hours (even days) to execute the above command for a 3.5GB file. Anyway a test is always better than a hypothesis, so I started a cmd prompt and run the code. I did this as soon as I got your e-mail. It now have passed 5-6 mins and still no result (I monitor the out.txt filesize as well). sed finished iin about 70secs, so probably cmd will take alot of hours. Nikos
Re: search pattern on sed or grep
>> grep 'rs10946498' chr6.txt | grep -v 'rs10946498.*rs10946498' > >> out.txt >> >> Sed might allow it in one pass with something like >> >> sed -e '/rs10946398/!d' -e '/rs10946398.*rs10946398/d' >> chr6.txt > out.txt > > Still try to migrate from Windows to linux, but hopefully will done it > someday! Since you have a fixed pattern (as Tony mentioned about using fgrep), you can do at least the first variant in native windows/dos with C:\Temp> find "rs10946398" chr6.txt > out.txt without the need for sed/grep at all. The dos "find" command is a bit like "grep" with all the cool functionality removed. The resulting file would hopefully be small enough that vim/ed could handle the resulting out.txt file. You can learn more by issuing C:\Temp> find /? No patterns other than fixed text, but sometimes that's all you need. And 640k oughta be enough for anyone ;) -tim (now only running Windows at work, but Linux, OpenBSD and Mac OS X at home)
Re: question about insert mode and zz
shawn bright wrote: Hey there all, i really dig the zz function to get me in the middle of the screen. i was wondering if there were an insert mode ability to do the same thing. So if i am writing a long function and get to the bottom of the screen i can move where i am at to the middle of the screen while still in insert mode? Others have covered various sorts of maps; however, if you really like having that cursor in the middle of the screen, I suggest setting the scrolloff option. ex. set scrolloff=999 will always keep the current line in the middle of the screen. If you like some wiggle room, try ex. set scrolloff=5 Regards, Chip Campbell
Re: search pattern on sed or grep
Nikolaos A. Patsopoulos wrote: > Hi all, > > I'm very sorry to bother the list with this problem but I've been > searching in the web the couples hours to find an answer and still > haven't find any. > > The problem is that I have a txt file of 3.5GB containing all the info > of Human chromosome 6. I want to save into one another file all lines > that have the pattern rs10946398 (occurring only ones). I know that vi > cannot handle files so big. I used ed in Fedora5 but this too cannot > stream it. I hope that grep or sed can do this but cannot figure how to. > I tried the following for sed but doesn't work: > > sed '/rs10946398/p' chr6.txt pattern="rs10946398" LANG=C sed -n "/$pattern.*$pattern/T;/$pattern/p" < chr6.txt Pádraig.
Re: search pattern on sed or grep
A.J.Mechelynck wrote: Nikolaos A. Patsopoulos wrote: Hi all, I'm very sorry to bother the list with this problem but I've been searching in the web the couples hours to find an answer and still haven't find any. The problem is that I have a txt file of 3.5GB containing all the info of Human chromosome 6. I want to save into one another file all lines that have the pattern rs10946398 (occurring only ones). I know that vi cannot handle files so big. I used ed in Fedora5 but this too cannot stream it. I hope that grep or sed can do this but cannot figure how to. I tried the following for sed but doesn't work: sed '/rs10946398/p' chr6.txt Can someone help? Thank in advance, Nikos grep rs10946398 < chr6.txt > chr6.extract.txt Grep is a filter, remember? It takes its input from stdin, writes its output on stdout, and the regexp is on the command-line. The output consists of all input lines matching the pattern. Since in this case the pattern is a fixed string, we can also use fgrep (or grep -F) instead of grep. Best regards, Tony. Thanks, I found also the solution with sed: sed -n '/rs10946398/p' chr6.txt >o.txt Thanks, Nikos
Re: search pattern on sed or grep
> I'm very sorry to bother the list with this problem but I've been
> searching in the web the couples hours to find an answer and still
> haven't find any.
It's a common sed problem and in the FAQ
http://sed.sourceforge.net/sed1line.txt
(scan for the "emulates grep" bit)
Fortunately, the vim list has a lot of friendly regexp wonks like
myself :)
> The problem is that I have a txt file of 3.5GB containing all the info
> of Human chromosome 6. I want to save into one another file all lines
> that have the pattern rs10946398 (occurring only ones). I know that vi
> cannot handle files so big. I used ed in Fedora5 but this too cannot
> stream it. I hope that grep or sed can do this but cannot figure how to.
> I tried the following for sed but doesn't work:
>
> sed '/rs10946398/p' chr6.txt
>
> Can someone help?
you should be able to use
grep 'rs10946498' chr6.txt > out.txt
or either of the sed variants:
sed -n '/rs10946398/p' chr6.txt > out.txt
sed '/rs10946398/!d' chr6.txt > out.txt
If you misspelled and meant "occurring only once", you can then
post-process the above with
grep 'rs10946498' chr6.txt | grep -v 'rs10946498.*rs10946498' >
out.txt
Sed might allow it in one pass with something like
sed -e '/rs10946398/!d' -e '/rs10946398.*rs10946398/d'
chr6.txt > out.txt
The first sed variant (-n) doesn't print anything ('-n') unless
it matches the pattern. The 2nd sed variant deletes lines that
don't match the given pattern ("!d") akin to a ":v" command in vim.
I suspect that neither vi/vim nor ed streams the file and that
both suffer similar problems in that they try to map the whole
3.5GB file into memory which is a cruel thing to do to an OS. :)
If you just want lines with the pattern in it, I'd use the grep
command. If you want lines with the pattern in it once and only
once, I'd go with the last sed command.
My $0.02
-tim
Re: search pattern on sed or grep
Nikolaos A. Patsopoulos wrote: Hi all, I'm very sorry to bother the list with this problem but I've been searching in the web the couples hours to find an answer and still haven't find any. The problem is that I have a txt file of 3.5GB containing all the info of Human chromosome 6. I want to save into one another file all lines that have the pattern rs10946398 (occurring only ones). I know that vi cannot handle files so big. I used ed in Fedora5 but this too cannot stream it. I hope that grep or sed can do this but cannot figure how to. I tried the following for sed but doesn't work: sed '/rs10946398/p' chr6.txt Can someone help? Thank in advance, Nikos grep rs10946398 < chr6.txt > chr6.extract.txt Grep is a filter, remember? It takes its input from stdin, writes its output on stdout, and the regexp is on the command-line. The output consists of all input lines matching the pattern. Since in this case the pattern is a fixed string, we can also use fgrep (or grep -F) instead of grep. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 213. Your kids start referring to you as "that guy in front of the monitor."
RE: question about insert mode and zz
I know that a function key is a single key, but touch-typists might find it faster to map it to something like zz so they don't have to actually take their hands off the home keys to get to the mapping. I've set the leader on my system to the comma instead of the backslash, so it's even faster for me to hit ,zz (which I can do without looking) than to look at the keyboard while I move my hand off the home keys to get to the function key. Here's another one I use (not mine, but I'm afraid I don't remember who suggested it) occasionally: map zz :let &scrolloff=999-&scrolloff:set scrolloff? Hitting \zz (or ,zz for me) changes the scrolloff to a really large number (well, it toggles between the large number and the original value, which for me is 3). The behaviour? The cursor line is always smack in the middle of the screen. Hitting \zz again restores the original behaviour. Hope this helps, Salman. > -Original Message- > From: A.J.Mechelynck [mailto:[EMAIL PROTECTED] > Sent: Friday, May 04, 2007 11:28 AM > To: shawn bright > Cc: vimlist > Subject: Re: question about insert mode and zz > > shawn bright wrote: > > Hey there all, > > i really dig the zz function to get me in the middle of the screen. > > i was wondering if there were an insert mode ability to do > the same thing. > > So if i am writing a long function and get to the bottom of > the screen > > i can move where i am at to the middle of the screen while still in > > insert mode? > > > > thanks for any tips > > shawn > > > > Ctrl-O zz > > see ":help i_CTRL-O" (that's control-oh, not control-zero). > > Or if you're lazy: > > :imap zz > > then F9 does it. > > > Best regards, > Tony. > -- > The years of peak mental activity are undoubtedly between the > ages of four and eighteen. At four we know all the > questions, at eighteen all the answers. >
Re: question about insert mode and zz
shawn bright wrote: Hey there all, i really dig the zz function to get me in the middle of the screen. i was wondering if there were an insert mode ability to do the same thing. So if i am writing a long function and get to the bottom of the screen i can move where i am at to the middle of the screen while still in insert mode? thanks for any tips shawn Ctrl-O zz see ":help i_CTRL-O" (that's control-oh, not control-zero). Or if you're lazy: :imap zz then F9 does it. Best regards, Tony. -- The years of peak mental activity are undoubtedly between the ages of four and eighteen. At four we know all the questions, at eighteen all the answers.
search pattern on sed or grep
Hi all, I'm very sorry to bother the list with this problem but I've been searching in the web the couples hours to find an answer and still haven't find any. The problem is that I have a txt file of 3.5GB containing all the info of Human chromosome 6. I want to save into one another file all lines that have the pattern rs10946398 (occurring only ones). I know that vi cannot handle files so big. I used ed in Fedora5 but this too cannot stream it. I hope that grep or sed can do this but cannot figure how to. I tried the following for sed but doesn't work: sed '/rs10946398/p' chr6.txt Can someone help? Thank in advance, Nikos
Re: Vim stalls when I try to enable syntax on vimrc (Cream
Albie Janse van Rensburg wrote: Steve Hall wrote: From: Albie Janse van Rensburg, Fri, May 04, 2007 6:35 am I recently decided to try out the Cream build (sans Cream) of Vim, with all the new patches (from http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). Now, I seem to be unable to edit my vimrc without bringing Vim to a complete halt! Sound like the age-old and infamous TCL with Cygwin problem: http://tech.groups.yahoo.com/group/vim/message/78505 http://tech.groups.yahoo.com/group/vim/message/78506 (solution) Yep, that's it. I should have mentioned I am using cygwin, I guess. Why does this bug appear on the patched version of Vim, but not the unpatched v7.0? Thanks for the pointer. Another workaround is never to use from Cygwin bash a Vim binary for native-Windows (and never use Vim-for-Cygwin except from within Cygwin). If your Cygwin /bin and /usr/bin aren't in the non-Cygwin PATH, then Vim-for-Windows will find TCL-for-Windows. Since they are added in front at Cygwin bash startup, Vim-for-Cygwin will find TCL-for-Cygwin first. (Vim-for-Windows will, for instance, be vim.exe and gvim.exe from the directory C:\Program Files\Vim\vim70, which is their $VIMRUNTIME. Vim-for-Cygwin will be, for instance, /usr/bin/vim.exe with its $VIMRUNTIME at /usr/share/vim/vim70/.) Vhy isn't it present in Bram's 7.0.000? Err... isn't the latter compiled without TCL support? Then it never looks for a TCL dll. Best regards, Tony. -- Frobnitz, pl. Frobnitzem (frob'nitsm) n.: An unspecified physical object, a widget. Also refers to electronic black boxes. This rare form is usually abbreviated to FROTZ, or more commonly to FROB. Also used are FROBNULE, FROBULE, and FROBNODULE. Starting perhaps in 1979, FROBBOZ (fruh-bahz'), pl. FROBBOTZIM, has also become very popular, largely due to its exposure via the Adventure spin-off called Zork (Dungeon). These can also be applied to non-physical objects, such as data structures.
Re: question about insert mode and zz
yep, that helps, just did the map, exactly what i was looking for, thanks shawn On 5/4/07, Tim Chase <[EMAIL PROTECTED]> wrote: > i really dig the zz function to get me in the middle of the screen. > i was wondering if there were an insert mode ability to do the same thing. > So if i am writing a long function and get to the bottom of the screen > i can move where i am at to the middle of the screen while still in > insert mode? You can use control+o (that's an "oh" not a "zero") followed by zz which will enter normal-mode for one command (your "zz") and then return you to where you were in insert mode. I do exactly this on a regular basis. I started with the old-school "z." (in original vi) instead of "zz" (a vim extension) and was irked that it didn't keep my position...until I learned of zz. I now regularly use zz/zt/zb instead of the old z./z/z- commands. The above can be mapped if you do it often enough to warrant a single keypress...something like :inoremap zz If you want to read about this "temporary normal mode", you can read the scant details at :help i_ctrl-o HTH, -tim
Re: A nice efm for javac
Thanks for that, I am using the efm but finds it drops the first line of the first error. errorformat=%Z%f:%l: %m,%A%p^,%-G%*[^sl]%.%# version 7.0.122 javac 1.6.0 other wise it's marked improvement. Yours faithfully, Warren Crossing Michael F. Lamb wrote: > I like to keep the name in, so that when later changes > are suggested we know who wrote the original. I don't mind that either :) >>after the pointer line. That way, the unused error >>text between doesn't break vim's notion of a >>"multi-line message" and also doesn't force us to >>include it as a "continuation of a multi-line >>message." > > Thanks for the update. Only the last two items changed, > right? Correct. (Erm, I must have thought I was about to make many more changes... sorry, the pedantry was unintentional.) :)
Re: question about insert mode and zz
> i really dig the zz function to get me in the middle of the screen. > i was wondering if there were an insert mode ability to do the same thing. > So if i am writing a long function and get to the bottom of the screen > i can move where i am at to the middle of the screen while still in > insert mode? You can use control+o (that's an "oh" not a "zero") followed by zz which will enter normal-mode for one command (your "zz") and then return you to where you were in insert mode. I do exactly this on a regular basis. I started with the old-school "z." (in original vi) instead of "zz" (a vim extension) and was irked that it didn't keep my position...until I learned of zz. I now regularly use zz/zt/zb instead of the old z./z/z- commands. The above can be mapped if you do it often enough to warrant a single keypress...something like :inoremap zz If you want to read about this "temporary normal mode", you can read the scant details at :help i_ctrl-o HTH, -tim
Re: Vim stalls when I try to enable syntax on vimrc (Cream
Steve Hall wrote: From: Albie Janse van Rensburg, Fri, May 04, 2007 6:35 am I recently decided to try out the Cream build (sans Cream) of Vim, with all the new patches (from http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). Now, I seem to be unable to edit my vimrc without bringing Vim to a complete halt! Sound like the age-old and infamous TCL with Cygwin problem: http://tech.groups.yahoo.com/group/vim/message/78505 http://tech.groups.yahoo.com/group/vim/message/78506 (solution) Yep, that's it. I should have mentioned I am using cygwin, I guess. Why does this bug appear on the patched version of Vim, but not the unpatched v7.0? Thanks for the pointer. -- Albie Janse van Rensburg ~ http://morph.telspace.co.za Please don't send me any MS Word or Powerpoint attachments unless it's absolutely neccessary - send simply text. http://www.gnu.org/philosophy/no-word-attachments.html Great acts are made up of small deeds. -- Lao Tsu
Re: Absolute tag paths in Win32
Well, this problem was explained as part of an earlier email thread. I warmly recommend to use 'upward' search for your tag file. After setting it that way, tagging works like a charm for me. Read the following thread. It will give an answer to your question: http://tech.groups.yahoo.com/group/vim/message/78303 Regards, Zarko Coklin > Hello! > > I seem to be having some difficulty in using tag files for a C project. > I've done some searching on the maillist with no progress. I'm working > under Win32, and here's what I have in my _vimrc > > set tags+=c:\Projects\some_folder_name_here\tags > > When I explore to a folder deeper into the tree (e.g. > c:\Projects\some_folder_name_here\some_other\something.c) and try to > jump to a tag, it complains that no tag file was found - and hence no tags. > > However, if I 'cd' into the c:\Projects\some_folder_name_here\ , and > then 'e' the file from that directory, I can properly jump to the tag. > Some of this source code is deeply nested in folders, so this becomes a > bit of a nuisance to do. > > When I print tags by :set tags , it prints out the correct paths (the > defaults) and my additional path seperated by commas. > > Thanks for your time in advance, > > - Eric Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097
Re: Vim stalls when I try to enable syntax on vimrc (Cream
A.J.Mechelynck wrote: Albie Janse van Rensburg wrote: Hi all I recently decided to try out the Cream build (sans Cream) of Vim, with all the new patches (from http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). Now, I seem to be unable to edit my vimrc without bringing Vim to a complete halt! I am unable to break out of it, and the only way to close Vim is by killing the process (leaving all my buffers' temp files still lying around, etc. Not very graceful). I suspect the problem lies with the Vim filetype syntax highlighting, since I do not get the problem when I have syntax off, or syntax on while editing other filetypes. When I reverted to the "official" Vim build for Windows (compiled May 7 2006), the problem disappeared. Is there anyone on this list that uses the Cream (sans Cream) build of Vim, and can someone confirm/help solve the problem? Albie gvim --version (of the Cream build): VIM - Vi IMproved 7.0 (2006 May 7, compiled May 3 2007 17:13:26) MS-Windows 32 bit GUI version with OLE support Included patches: 1-241 Compiled by [EMAIL PROTECTED] Big version with 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 +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang +mzscheme/dyn +netbeans_intg +ole -osfiletype +path_extra +perl/dyn -postscript +printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save -xpm_w32 system vimrc file: "$VIM\vimrc" user vimrc file: "$HOME\_vimrc" 2nd user vimrc file: "$VIM\_vimrc" user exrc file: "$HOME\_exrc" 2nd user exrc file: "$VIM\_exrc" system gvimrc file: "$VIM\gvimrc" user gvimrc file: "$HOME\_gvimrc" 2nd user gvimrc file: "$VIM\_gvimrc" system menu file: "$VIMRUNTIME\menu.vim" Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG 1. Check (by looking near the top of the files) the versions of the following files, all of which contribute to vimscript highlighting (and are sourced whenever a *.vim file is opened with ":filetype plugin indent on" and "syntax on"): -- $VIMRUNTIME/ftplugin/vim.vim " Vim filetype plugin " Language:Vim " Maintainer:Bram Moolenaar <[EMAIL PROTECTED]> " Last Change:2006 Sep 26 -- -- $VIMRUNTIME/indent/vim.vim " Vim indent file " Language:Vim script " Maintainer:Bram Moolenaar <[EMAIL PROTECTED]> " Last Change:2005 Jul 06 -- -- $VIMRUNTIME/syntax/vim.vim " Vim syntax file " Language:Vim 7.0 script " Maintainer:Dr. Charles E. Campbell, Jr. <[EMAIL PROTECTED]> " Last Change:April 25, 2007 " Version:7.0-62 -- -- $VIMRUNTIME/syntax/perl.vim " Vim syntax file " Language:Perl " Maintainer:Nick Hibma <[EMAIL PROTECTED]> " Last Change:2006 November 23 " Location:http://www.van-laarhoven.org/vim/syntax/perl.vim -- -- $VIMRUNTIME/syntax/ruby.vim " Vim syntax file " Language:Ruby " Maintainer:Doug Kearns <[EMAIL PROTECTED]> " Info:$Id: ruby.vim,v 1.118 2007/03/02 05:40:49 tpope Exp $ " URL:http://vim-ruby.rubyforge.org " Anon CVS:See above site " Release Coordinator:Doug Kearns <[EMAIL PROTECTED]> " " " Previous Maintainer:Mirko Nasato " Thanks to perl.vim authors, and to Reimer Behrends. :-) (MN) " -- -- $VIMRUNTIME/syntax/python.vim " Vim syntax file " Language:Python " Maintainer:Neil Schemenauer <[EMAIL PROTECTED]> " Updated:2006-10-15 "Added Python 2.4 features 2006 May 4 (Dmitry Vasiliev) -- -- $VIMRUNTIME/syntax/tcl.vim " Vim syntax file " Language:TCL/TK " Maintainer:Brett Cannon <[EMAIL PROTECTED]> " (previously Dean Copsey <[EMAIL PROTECTED]>) "(previously Matt Neumann <[EMAIL PROTECTED]>) "(previously Allan Kelly <[EMAIL PROTECTED]>) " Original:Robin Becker <[EMAIL PROTECTED]> " Last Change:2006 Nov 17 " " Keywords TODO: format clock click anchor -- -- $VIMRUNTIME/syntax/scheme.vim " Vim syntax file
RE: Vim stalls when I try to enable syntax on vimrc (Cream
From: Albie Janse van Rensburg, Fri, May 04, 2007 6:35 am > > I recently decided to try out the Cream build (sans Cream) of Vim, > with all the new patches (from > http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). > > Now, I seem to be unable to edit my vimrc without bringing Vim to a > complete halt! Sound like the age-old and infamous TCL with Cygwin problem: http://tech.groups.yahoo.com/group/vim/message/78505 http://tech.groups.yahoo.com/group/vim/message/78506 (solution) -- Steve Hall [ digitect dancingpaper com ]
question about insert mode and zz
Hey there all, i really dig the zz function to get me in the middle of the screen. i was wondering if there were an insert mode ability to do the same thing. So if i am writing a long function and get to the bottom of the screen i can move where i am at to the middle of the screen while still in insert mode? thanks for any tips shawn
mail plugin and hexdump file cause endless loop in vim 7
Hi! I've hit one interesting problem. When I've tried to send in an email large hexdump (around 50K) the vim entered endless loop with 100% CPU usage. I could terminate this loop by hitting Ctrl-C, but as soon as I've tried to move to the long line the same thing happened again. Since I could manipulated this file with vim without mail ftplugin, I came to conclusion that the problem has something to do with that plugin. The file in question is located at http://vandal.sdf-eu.org/hexdump.txt To reproduce the problem I did the following steps bash$ vim mutt-vandal-1001-25710-908 :new hexdump.txt 2yy :q p At this point vim freezes and top reports that it uses 100% CPU. Just in case. I use ~/.vim/ftplugin/mail.vim with set fo-=l Can anyone else try and see if the same thing happens? I'm running 64-bit linux Here's the output of version :version VIM - Vi IMproved 7.0 (2006 May 7, compiled Apr 27 2007 16:11:48) Included patches: 1-233 Compiled by [EMAIL PROTECTED] Normal version with GTK2 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/share/vim" Compilation: gcc-3.4 -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -DXTHREADS -D_REENTRANT -DXUSE_M TSAFE_API -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/X11R6/include -I/usr/include/at k-1.0 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/freetype2/config -I/usr/inclu de/glib-2.0 -I/usr/lib/glib-2.0/include -O2 -march=athlon64 -I/usr/X11R6/include Linking: gcc-3.4 -L/usr/lib64 -L/usr/X11R6/lib64 -L/usr/local/lib -o vim -Wl,--export-dynamic -L/usr/lib64 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0 -lXt -lncurses -lgpm -- Minds, like parachutes, function best when open
Re: Vim stalls when I try to enable syntax on vimrc (Cream
Albie Janse van Rensburg wrote: Hi all I recently decided to try out the Cream build (sans Cream) of Vim, with all the new patches (from http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). Now, I seem to be unable to edit my vimrc without bringing Vim to a complete halt! I am unable to break out of it, and the only way to close Vim is by killing the process (leaving all my buffers' temp files still lying around, etc. Not very graceful). I suspect the problem lies with the Vim filetype syntax highlighting, since I do not get the problem when I have syntax off, or syntax on while editing other filetypes. When I reverted to the "official" Vim build for Windows (compiled May 7 2006), the problem disappeared. Is there anyone on this list that uses the Cream (sans Cream) build of Vim, and can someone confirm/help solve the problem? Albie gvim --version (of the Cream build): VIM - Vi IMproved 7.0 (2006 May 7, compiled May 3 2007 17:13:26) MS-Windows 32 bit GUI version with OLE support Included patches: 1-241 Compiled by [EMAIL PROTECTED] Big version with 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 +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang +mzscheme/dyn +netbeans_intg +ole -osfiletype +path_extra +perl/dyn -postscript +printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save -xpm_w32 system vimrc file: "$VIM\vimrc" user vimrc file: "$HOME\_vimrc" 2nd user vimrc file: "$VIM\_vimrc" user exrc file: "$HOME\_exrc" 2nd user exrc file: "$VIM\_exrc" system gvimrc file: "$VIM\gvimrc" user gvimrc file: "$HOME\_gvimrc" 2nd user gvimrc file: "$VIM\_gvimrc" system menu file: "$VIMRUNTIME\menu.vim" Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG 1. Check (by looking near the top of the files) the versions of the following files, all of which contribute to vimscript highlighting (and are sourced whenever a *.vim file is opened with ":filetype plugin indent on" and "syntax on"): -- $VIMRUNTIME/ftplugin/vim.vim " Vim filetype plugin " Language:Vim " Maintainer: Bram Moolenaar <[EMAIL PROTECTED]> " Last Change: 2006 Sep 26 -- -- $VIMRUNTIME/indent/vim.vim " Vim indent file " Language:Vim script " Maintainer: Bram Moolenaar <[EMAIL PROTECTED]> " Last Change: 2005 Jul 06 -- -- $VIMRUNTIME/syntax/vim.vim " Vim syntax file " Language:Vim 7.0 script " Maintainer: Dr. Charles E. Campbell, Jr. <[EMAIL PROTECTED]> " Last Change: April 25, 2007 " Version: 7.0-62 -- -- $VIMRUNTIME/syntax/perl.vim " Vim syntax file " Language:Perl " Maintainer: Nick Hibma <[EMAIL PROTECTED]> " Last Change: 2006 November 23 " Location:http://www.van-laarhoven.org/vim/syntax/perl.vim -- -- $VIMRUNTIME/syntax/ruby.vim " Vim syntax file " Language:Ruby " Maintainer: Doug Kearns <[EMAIL PROTECTED]> " Info:$Id: ruby.vim,v 1.118 2007/03/02 05:40:49 tpope Exp $ " URL: http://vim-ruby.rubyforge.org " Anon CVS:See above site " Release Coordinator: Doug Kearns <[EMAIL PROTECTED]> " " " Previous Maintainer: Mirko Nasato " Thanks to perl.vim authors, and to Reimer Behrends. :-) (MN) " -- -- $VIMRUNTIME/syntax/python.vim " Vim syntax file " Language:Python " Maintainer: Neil Schemenauer <[EMAIL PROTECTED]> " Updated: 2006-10-15 " Added Python 2.4 features 2006 May 4 (Dmitry Vasiliev) -- -- $VIMRUNTIME/syntax/tcl.vim " Vim syntax file " Language:TCL/TK " Maintainer: Brett Cannon <[EMAIL PROTECTED]> " (previously Dean Copsey <[EMAIL PROTECTED]>) " (previously Matt Neumann <[EMAIL PROTECTED]>) " (previously Allan Kelly <[EMAIL PROTECTED]>) " Original:Robin Becker <[EMAIL PROTECTED]> " Last Change: 2006 Nov 17 " " Keywords TODO: format clock click anchor -- -
Vim stalls when I try to enable syntax on vimrc (Cream
Hi all I recently decided to try out the Cream build (sans Cream) of Vim, with all the new patches (from http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721). Now, I seem to be unable to edit my vimrc without bringing Vim to a complete halt! I am unable to break out of it, and the only way to close Vim is by killing the process (leaving all my buffers' temp files still lying around, etc. Not very graceful). I suspect the problem lies with the Vim filetype syntax highlighting, since I do not get the problem when I have syntax off, or syntax on while editing other filetypes. When I reverted to the "official" Vim build for Windows (compiled May 7 2006), the problem disappeared. Is there anyone on this list that uses the Cream (sans Cream) build of Vim, and can someone confirm/help solve the problem? Albie gvim --version (of the Cream build): VIM - Vi IMproved 7.0 (2006 May 7, compiled May 3 2007 17:13:26) MS-Windows 32 bit GUI version with OLE support Included patches: 1-241 Compiled by [EMAIL PROTECTED] Big version with 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 +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu +mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang +mzscheme/dyn +netbeans_intg +ole -osfiletype +path_extra +perl/dyn -postscript +printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +title +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save -xpm_w32 system vimrc file: "$VIM\vimrc" user vimrc file: "$HOME\_vimrc" 2nd user vimrc file: "$VIM\_vimrc" user exrc file: "$HOME\_exrc" 2nd user exrc file: "$VIM\_exrc" system gvimrc file: "$VIM\gvimrc" user gvimrc file: "$HOME\_gvimrc" 2nd user gvimrc file: "$VIM\_gvimrc" system menu file: "$VIMRUNTIME\menu.vim" Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG -- Albie Janse van Rensburg ~ http://morph.telspace.co.za Please don't send me any MS Word or Powerpoint attachments unless it's absolutely neccessary - send simply text. http://www.gnu.org/philosophy/no-word-attachments.html Depend on the rabbit's foot if you will, but remember, it didn't help the rabbit. -- R. E. Shay
Re: how to enable mouse in vim of cygwin
A.J.Mechelynck wrote: sun wrote: I'm using cygwin and rxvt. It works quite well, since you don't need to start an X server for the application - it just runs. Put the following in your cygwin launcher (cygwin_rxvt.bat for me): > @echo off > C: > chdir C:\cygwin\bin > set SHELL=/bin/bash > rxvt -ls -sr -sl 1500 -fn "Lucida ConsoleP-12" -bg black -fg grey and in your .bashrc: > export TERM="rxvt-cygwin-native" your mouse should work fine with rxvt (mine does!) Cheers Now I can use mouse to jump from one split window to another under rxvx, but how to resize one? I can't do it by mouse in my case, can you? sun You should be able to drag the status lines and vertical dividers to resize the split windows. Best regards, Tony; I can confirm that this seems to not work, using the cygwin Vim version when run in rxvt. Tab-switching and window selection does work, however. :version VIM - Vi IMproved 7.0 (2006 May 7, compiled Oct 10 2006 10:07:11) Included patches: 1-122 Compiled by [EMAIL PROTECTED] Huge version without 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 +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 -xterm_clipboard -xterm_save system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -g -O2 Linking: gcc -L/usr/local/lib -o vim.exe -lncurses -liconv -lintl settings: :set --- Options --- background=dark laststatus=2mouse=a scroll=14 ttyfast ttymouse=xterm window=59 statusline=%<%1*=== %5*%f%1*%( === %4*%h%1*%)%( === %4*%m%1*%)%( === %4*%r%1*%) ===% %2*%b(0x%B)%1* === %3*%l,%c%V%1* === %5*%P%1* ===%0* viminfo=!,'20,<50,s10,h -- Albie Janse van Rensburg ~ http://morph.telspace.co.za Please don't send me any MS Word or Powerpoint attachments unless it's absolutely neccessary - send simply text. http://www.gnu.org/philosophy/no-word-attachments.html For fast-acting relief, try slowing down.
Re: how to enable mouse in vim of cygwin
sun wrote: I'm using cygwin and rxvt. It works quite well, since you don't need to start an X server for the application - it just runs. Put the following in your cygwin launcher (cygwin_rxvt.bat for me): > @echo off > C: > chdir C:\cygwin\bin > set SHELL=/bin/bash > rxvt -ls -sr -sl 1500 -fn "Lucida ConsoleP-12" -bg black -fg grey and in your .bashrc: > export TERM="rxvt-cygwin-native" your mouse should work fine with rxvt (mine does!) Cheers Now I can use mouse to jump from one split window to another under rxvx, but how to resize one? I can't do it by mouse in my case, can you? sun You should be able to drag the status lines and vertical dividers to resize the split windows. Best regards, Tony; -- hundred-and-one symptoms of being an internet addict: 212. Your Internet group window has more icons than your Accessories window.
