Comments on: Using Vim under Cygwin

By: martianpackets

martianpackets — Mon, 12 Sep 2011 21:23:44 +0000

so I took it to the next level. I went to my most-used linux shell, grabbed my .vimrc file, and scp’d it into my cygwin ~/ folder. Now I am in business!

By: martianpackets

martianpackets — Mon, 12 Sep 2011 21:18:30 +0000

creating a blank .vimrc file in ~/ to make cygwin-installed vim or gvim behave correctly, is the most brilliant idea I’ve seen so far in 2011.

By: dude

dude — Sat, 20 Aug 2011 04:33:55 +0000

Greg is right
touch.exe ~/.vimrc
and you don’t need to install the other vim, cygwin vim suddenly starts working just fine!!

By: Lucas

Lucas — Thu, 12 Feb 2009 15:23:16 +0000

Thanks Gregg! Worked just fine!

By: Gregg

Gregg — Tue, 03 Feb 2009 06:29:31 +0000

I experienced several issues using vim ( ex – pressing “i” didn’t put it into INSERT mode ), i created a blank file ~/.vimrc and everything worked great.

By: TidyTim

TidyTim — Wed, 18 Jul 2007 15:55:55 +0000

The script as given above will only edit one file. What if you want to edit several files? What if you want to edit several files and start all open in their own frame? If you add the “-o” switch cypath will take it as a option so it probably produce an error and it won’t get passed to Vim.

Here’s the original script:

“/cygdrive/c/Program Files/Vim/vim63/vim.exe” `cygpath -w $1`

Here’s a more useful variation (assuming the Bash shell):

“/cygdrive…/vim.exe” $(cygpath -w — $*) &

Cygpath ignores options after the “–”.

By: Luc Hermitte

Luc Hermitte — Fri, 30 Sep 2005 00:00:44 +0000

Hello.

I do not really like to post such plain advertizes, but I think the script I’m maintening, cyg-wrapper.sh, could solve both your problems. (If I understand how the blog works, just click on my name to access to the script).

Regarding Vim, look at the example given on the web page. Regarding cvs, declare -m as a binary-argument. BTW, Vim plugin, cvsmenu, is quite addictive — though I have used it only on Solaris.

NB: As cyg-wrapper is just a bash script, it may take some time when to many filenames need to be converted.

HTH.

By: Dr.M

Dr.M — Sat, 16 Apr 2005 05:52:53 +0000

cat ~/.bashrc

vi(){ # windows.
vifile=${@:-$vifile}; # use last file or argv
vifile=$(cygpath -m $@) # dos paths
c:/bin32/gvim $vifile &
}

I too just started using cygwin and tortoise-cvs.

By: Daniel Lemire

Daniel Lemire — Fri, 18 Feb 2005 19:01:58 +0000

Thanks. Indeed a good alternative.

I knew about the “-m” command, but also, under windows, one can use Tortoise CVS, you then have a nice GUI to take care of all your CVS trouble. But I remain a command line freak. So I should get in the habit of using -m, it is probably faster in the long run anyhow.

By: Zbigniew Lukasiak

Zbigniew Lukasiak — Fri, 18 Feb 2005 10:00:09 +0000

-m message

Use message as log information, instead of invoking an editor.

Available with the following commands: add, commit and import.

From cvs man page.

By: Zbigniew Lukasiak

Zbigniew Lukasiak — Fri, 18 Feb 2005 09:53:47 +0000

You can use the -m ‘log_message’ option for the commit to enter the comments.