This is the mail archive of the
mailing list for the Cygwin project.
- From: "Crescioli, Phil" <Phil dot Crescioli at gd-ais dot com>
- To: <cygwin at cygwin dot com>
- Cc: <offby1 at blarg dot net>
- Date: Wed, 17 Mar 2004 12:44:33 -0500
- Subject: RE: GVIM
I took your bash shell vi->gvim converter and re-wrote it
for placement in my ~/.tcshrc.
if ($?tcsh) then
if ("$TERM" == "cygwin") then
echo "Setting VI to kickoff GVIM within a cygwin window"
if (-x "C:/vim/vim62/gvim.exe") then
alias vi "C:/vim/vim62/gvim.exe"
Thanks for the tip!
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Friday, March 12, 2004 9:51 AM
To: Crescioli, Phil
Subject: Re: GVIM
>>>>> "Phil" == Crescioli, Phil <Phil.Crescioli@gd-ais.com> writes:
Phil> Hello all, Why is only VIM and not GVIM included with the
Phil> Cygwin package? I'd love to use GVIM straight from a Cygwin
Cygwin packages whatever software someone has bothered to port to
Cygwin. Apparently nobody has ported gvim. Go ahead and do it
As it happens, I use gvim with Cygwin, and it's fine. I had to
install Cygwin and gvim separately, of course, but neither
installation is difficult.
To further the illusion of gvim being "part of" Cygwin, I've put this
shell function definition in ~/.bashrc:
if [ "$OSTYPE" = "cygwin" ]; then
if [ -x "/c/vim/vim62/gvim.exe" ]; then
Thus, when I type `vi foo' in a Cygwin shell, I actually run gvim.
Always code as if the guy who ends up maintaining your code will
be a violent psychopath who knows where you live. John F. Woods
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html