Re: gVim and Cygwin
Robert Schols wrote: [...] I use the UnxUtils package: http://unxutils.sourceforge.net/ It includes all of the commands I need and accepts forward slashes as well as backslashes. I use these commands from the standard precompiled gvim.exe from vim.org. I have cygwin as well, but it is later in my %PATH%. Although technically not an answer to your question, I think this is the best solution to your problem. Best regards, Robert PS: Actually I use the Labrat Toolkit which includes the UnxUtils package, but labrattech.com seems to have issues with php syntax at the moment. When they are up and running again you must check this out. When I was on Windows, I tried the unxutils package, but I had some problems with it, I don't remember which ones. Apparently it works for some people, so let those go on using it. For people like me, happily there is another set of Unix-like programs which work under native Windows, viz. the GnuWin32 utilities (available as a SourceForge project). I used to have GnuWin32 late in my PATH (after any Micro$oft programs of the same name such as sort.exe) and Cygwin not in the PATH at all (except of course in the terminal window running Cygwin bash, where it came early in the $PATH). Best regards, Tony. -- "A wizard cannot do everything; a fact most magicians are reticent to admit, let alone discuss with prospective clients. Still, the fact remains that there are certain objects, and people, that are, for one reason or another, completely immune to any direct magical spell. It is for this group of beings that the magician learns the subtleties of using indirect spells. It also does no harm, in dealing with these matters, to carry a large club near your person at all times." -- The Teachings of Ebenezum, Volume VIII
RE: gVim and Cygwin
> -Original Message- > From: Waters, Bill [mailto:[EMAIL PROTECTED] > Sent: Friday, March 30, 2007 18:06 > To: vim@vim.org > Subject: gVim and Cygwin > > > Does anyone have experience with running gVim and using > Cygwin commands (ex. indent)? I would prefer not to run vim > in a Cygwin terminal, unless someone has all of the > configurations needed (syntax highlighting, etc) to have that > act like gVim. I use the UnxUtils package: http://unxutils.sourceforge.net/ It includes all of the commands I need and accepts forward slashes as well as backslashes. I use these commands from the standard precompiled gvim.exe from vim.org. I have cygwin as well, but it is later in my %PATH%. Although technically not an answer to your question, I think this is the best solution to your problem. Best regards, Robert PS: Actually I use the Labrat Toolkit which includes the UnxUtils package, but labrattech.com seems to have issues with php syntax at the moment. When they are up and running again you must check this out.
Re: gVim and Cygwin
On 30-Mar-2007 21:23, A.J.Mechelynck wrote: OTOH, since (IIRC) builds of Vim available on the Cygwin site are usually console builds, to get a Cygwin/X11 build of gvim you would have to compile it yourself. Actually, an X11 gvim *is* available using Cygwin's setup.exe. It's not installed by default, but it is listed, under the 'Editors' category. - Michael
Re: gVim and Cygwin
David Fishburn wrote:
-Original Message-
From: A.J.Mechelynck [mailto:[EMAIL PROTECTED]
Sent: Friday, March 30, 2007 6:42 PM
To: Charles E Campbell Jr
Cc: Waters, Bill; vim@vim.org
Subject: Re: gVim and Cygwin
Charles E Campbell Jr wrote:
Waters, Bill wrote:
Does anyone have experience with running gVim and using Cygwin
commands (ex. indent)? I would prefer not to run vim in a Cygwin
terminal, unless someone has all of the configurations
needed (syntax
highlighting, etc) to have that act like gVim.
I generally compile both gvim and vim under cygwin, and haven't run
into any problems. I haven't used indent, though. The problems I
generally have had have been with Windows' paths and trying to get
netrw to understand them properly, but that's not because
of gvim and cygwin.
If you already have cygwin, just get vim 7.0 source, and go to its
source directory.
gmake -f Make_cyg.mak
will make gvim.exe by default. Edit Make_cyg.mak, and
change GUI=yes
to GUI=no, and type the same command above. That way you'll get
vim.exe. Its really quite straightforward!
Regards,
Chip Campbell
Make_cyg.mak uses Cygwin tools to (cross-) compile a
native-Windows Vim or gvim which doesn't need Cygwin to run
and doesn't understand the POSIX paths of cygwin. It won't
interface easily with Cygwin bash (or any other Cygwin
program for that matter).
To compile a Unix-like "Vim for Cygwin" you must use the
top-level Makefile or the src/Makefile which will invoke a
configure step. If configure finds the necessary headers and
libraries it may compile a GUI version of Vim, which will
need Cygwin to run, and X11 to display a GUI.
Hmm, based on your response and Gary's (libncurses-devel) and this post:
http://www.cygwin.com/ml/cygwin/2003-06/msg00886.html
I ran the following:
cd /c/OpenSrc/vim7/src
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--libexecdir='$(sbindir)' \
--localstatedir=/var \
--datadir='$(prefix)/share' \
--enable-multibyte \
--without-x \
--enable-gui=no
This results in:
./configure: line 3: $'\r': command not found
auto/configure: line 11: $'\r': command not found
auto/configure: line 19: syntax error near unexpected token `elif'
auto/configure: line 19: `elif test -n "${BASH_VERSION+set}" && (set -o
posix) >'dev/null 2>&1; then
./configure: line 6: $'\r': command not found
./configure: line 11: syntax error: unexpected end of file
I have never tried this before, I am wondering if it is related to dos line
endings?
Could be. Try converting all of those to Unix line endings, e.g. with
something like (untested)
make distclean
vim -u NONE -N -cmd "set ffs= ff=dos" src/* -c "bufdo setlocal ff=unix|w" -c q
I pulled the source from a win32 SVN client. It is the same directory I
compile for win32 from.
Any suggestions?
Thanks,
Dave
Best regards,
Tony.
--
Brain, v. [as in "to brain"]:
To rebuke bluntly, but not pointedly; to dispel a source of
error in an opponent.
-- Ambrose Bierce, "The Devil's Dictionary"
Re: gVim and Cygwin
Waters, Bill wrote: Does anyone have experience with running gVim and using Cygwin commands (ex. indent)? I would prefer not to run vim in a Cygwin terminal, unless someone has all of the configurations needed (syntax highlighting, etc) to have that act like gVim. Thanks, Bill I do use gVim and cygwin. For using the cygwin bash shell instead of the regular Windows DOS prompt, I use the following in my _vimrc: :set shell=c:\cygwin\cygwin.bat The only problem I have is that I have to type the command twice. The first time opens the shell, the second will insert the result of the command. For example to insert the current date, I do the following: :r!date date exit On my Mac OS X box, I can just type :r!date
Re: gVim and Cygwin
On 2007-03-30, David Fishburn <[EMAIL PROTECTED]> wrote:
>
> > -Original Message-
> > From: A.J.Mechelynck [mailto:[EMAIL PROTECTED]
> > Sent: Friday, March 30, 2007 6:42 PM
> > To compile a Unix-like "Vim for Cygwin" you must use the
> > top-level Makefile or the src/Makefile which will invoke a
> > configure step. If configure finds the necessary headers and
> > libraries it may compile a GUI version of Vim, which will
> > need Cygwin to run, and X11 to display a GUI.
>
> Hmm, based on your response and Gary's (libncurses-devel) and this post:
> http://www.cygwin.com/ml/cygwin/2003-06/msg00886.html
>
> I ran the following:
> cd /c/OpenSrc/vim7/src
> ./configure \
> --prefix=/usr \
> --sysconfdir=/etc \
> --libexecdir='$(sbindir)' \
> --localstatedir=/var \
> --datadir='$(prefix)/share' \
> --enable-multibyte \
> --without-x \
> --enable-gui=no
>
> This results in:
> ./configure: line 3: $'\r': command not found
> auto/configure: line 11: $'\r': command not found
> auto/configure: line 19: syntax error near unexpected token `elif'
> auto/configure: line 19: `elif test -n "${BASH_VERSION+set}" && (set -o
> posix) >'dev/null 2>&1; then
> ./configure: line 6: $'\r': command not found
> ./configure: line 11: syntax error: unexpected end of file
>
>
> I have never tried this before, I am wondering if it is related to dos line
> endings?
>
> I pulled the source from a win32 SVN client. It is the same directory I
> compile for win32 from.
>
> Any suggestions?
I haven't had this problem myself, but from what I've seen posted to
the cygwin list, this looks like a line-ending problem. You can be
pretty sure it didn't come from any file installed with setup.exe
unless you edited some file with WordPad, for example, that changes
LF endings to CR-LF.
Something else that can mess you up is using WinZip to unzip a
package. While the option can be changed, WizZip's default behavior
is to change all text file line endings to CR-LF.
The 'file' command will show you the type of line endings that each
file has, and 'd2u' will convert CR-LF endings to LF.
Regards,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Mobile Broadband Division
| Spokane, Washington, USA
RE: gVim and Cygwin
> -Original Message-
> From: A.J.Mechelynck [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 30, 2007 6:42 PM
> To: Charles E Campbell Jr
> Cc: Waters, Bill; vim@vim.org
> Subject: Re: gVim and Cygwin
>
> Charles E Campbell Jr wrote:
> > Waters, Bill wrote:
> >
> >> Does anyone have experience with running gVim and using Cygwin
> >> commands (ex. indent)? I would prefer not to run vim in a Cygwin
> >> terminal, unless someone has all of the configurations
> needed (syntax
> >> highlighting, etc) to have that act like gVim.
> >>
> >>
> > I generally compile both gvim and vim under cygwin, and haven't run
> > into any problems. I haven't used indent, though. The problems I
> > generally have had have been with Windows' paths and trying to get
> > netrw to understand them properly, but that's not because
> of gvim and cygwin.
> >
> > If you already have cygwin, just get vim 7.0 source, and go to its
> > source directory.
> >
> > gmake -f Make_cyg.mak
> >
> > will make gvim.exe by default. Edit Make_cyg.mak, and
> change GUI=yes
> > to GUI=no, and type the same command above. That way you'll get
> > vim.exe. Its really quite straightforward!
> >
> > Regards,
> > Chip Campbell
> >
>
> Make_cyg.mak uses Cygwin tools to (cross-) compile a
> native-Windows Vim or gvim which doesn't need Cygwin to run
> and doesn't understand the POSIX paths of cygwin. It won't
> interface easily with Cygwin bash (or any other Cygwin
> program for that matter).
>
> To compile a Unix-like "Vim for Cygwin" you must use the
> top-level Makefile or the src/Makefile which will invoke a
> configure step. If configure finds the necessary headers and
> libraries it may compile a GUI version of Vim, which will
> need Cygwin to run, and X11 to display a GUI.
Hmm, based on your response and Gary's (libncurses-devel) and this post:
http://www.cygwin.com/ml/cygwin/2003-06/msg00886.html
I ran the following:
cd /c/OpenSrc/vim7/src
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--libexecdir='$(sbindir)' \
--localstatedir=/var \
--datadir='$(prefix)/share' \
--enable-multibyte \
--without-x \
--enable-gui=no
This results in:
./configure: line 3: $'\r': command not found
auto/configure: line 11: $'\r': command not found
auto/configure: line 19: syntax error near unexpected token `elif'
auto/configure: line 19: `elif test -n "${BASH_VERSION+set}" && (set -o
posix) >'dev/null 2>&1; then
./configure: line 6: $'\r': command not found
./configure: line 11: syntax error: unexpected end of file
I have never tried this before, I am wondering if it is related to dos line
endings?
I pulled the source from a win32 SVN client. It is the same directory I
compile for win32 from.
Any suggestions?
Thanks,
Dave
Re: gVim and Cygwin
Charles E Campbell Jr wrote: Waters, Bill wrote: Does anyone have experience with running gVim and using Cygwin commands (ex. indent)? I would prefer not to run vim in a Cygwin terminal, unless someone has all of the configurations needed (syntax highlighting, etc) to have that act like gVim. I generally compile both gvim and vim under cygwin, and haven't run into any problems. I haven't used indent, though. The problems I generally have had have been with Windows' paths and trying to get netrw to understand them properly, but that's not because of gvim and cygwin. If you already have cygwin, just get vim 7.0 source, and go to its source directory. gmake -f Make_cyg.mak will make gvim.exe by default. Edit Make_cyg.mak, and change GUI=yes to GUI=no, and type the same command above. That way you'll get vim.exe. Its really quite straightforward! Regards, Chip Campbell Make_cyg.mak uses Cygwin tools to (cross-) compile a native-Windows Vim or gvim which doesn't need Cygwin to run and doesn't understand the POSIX paths of cygwin. It won't interface easily with Cygwin bash (or any other Cygwin program for that matter). To compile a Unix-like "Vim for Cygwin" you must use the top-level Makefile or the src/Makefile which will invoke a configure step. If configure finds the necessary headers and libraries it may compile a GUI version of Vim, which will need Cygwin to run, and X11 to display a GUI. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 153. You find yourself staring at your "inbox" waiting for new e-mail to arrive.
Re: gVim and Cygwin
On 2007-03-30, Charles E Campbell Jr <[EMAIL PROTECTED]> wrote: > Waters, Bill wrote: > > > Does anyone have experience with running gVim and using Cygwin commands > > (ex. indent)? I would prefer not to run vim in a Cygwin terminal, unless > > someone has all of the configurations needed (syntax highlighting, etc) to > > have that act like gVim. > > > > > I generally compile both gvim and vim under cygwin, and haven't run into > any problems. I haven't used indent, though. The problems I generally > have had have been with Windows' paths and trying to get netrw to > understand them properly, but that's not because of gvim and cygwin. > > If you already have cygwin, just get vim 7.0 source, and go to its > source directory. > > gmake -f Make_cyg.mak > > will make gvim.exe by default. Edit Make_cyg.mak, and change GUI=yes > to GUI=no, and type the same command above. That way you'll get > vim.exe. Its really quite straightforward! To build a console vim that used color, I had to also install the Cygwin libncurses-devel package. HTH, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division | Spokane, Washington, USA
Re: gVim and Cygwin
Waters, Bill wrote: Does anyone have experience with running gVim and using Cygwin commands (ex. indent)? I would prefer not to run vim in a Cygwin terminal, unless someone has all of the configurations needed (syntax highlighting, etc) to have that act like gVim. I generally compile both gvim and vim under cygwin, and haven't run into any problems. I haven't used indent, though. The problems I generally have had have been with Windows' paths and trying to get netrw to understand them properly, but that's not because of gvim and cygwin. If you already have cygwin, just get vim 7.0 source, and go to its source directory. gmake -f Make_cyg.mak will make gvim.exe by default. Edit Make_cyg.mak, and change GUI=yes to GUI=no, and type the same command above. That way you'll get vim.exe. Its really quite straightforward! Regards, Chip Campbell
Re: gVim and Cygwin
Cc to list. Next time, please use bottom-posting or inter-posting in preference to top-posting, and "Reply to All" or "Reply to List" in preference to "Reply to Sender". ben lieb wrote: I've had no real problems. I use cygwin. I type 'startx' to run the x terminal. Then I run 'gvim' from that. As far as 'indent', it is not a bash command, it is a program that may have to be installed with the cygwin package manager. Either way, I don't have file or path translation problems. It doesn't, if invoked from bash or from some other cygwin program (including a Cygwin build of console Vim or a Cygwin/X11 build of gvim). If invoked from a Windows-native build of gvim, the user would have to make sure that what gvim thinks of as "C:\Documents and Settings\johndoe\foobar.c" gets translated to /home/johndoe/foobar.c or /cygdrive/c/Documents\ and\ Settings/johndoe/foobar.c -- or even /cygdrive/c/DOCUME~1/johndoe/foobar.c -- when invoking Cygwin indent. OTOH, since (IIRC) builds of Vim available on the Cygwin site are usually console builds, to get a Cygwin/X11 build of gvim you would have to compile it yourself. Best regards, Tony. -- "Being disintegrated makes me ve-ry an-gry!"
Re: gVim and Cygwin
Waters, Bill wrote: Does anyone have experience with running gVim and using Cygwin commands (ex. indent)? I would prefer not to run vim in a Cygwin terminal, unless someone has all of the configurations needed (syntax highlighting, etc) to have that act like gVim. Thanks, Bill Running gvim from Cygwin is much harder than running console Vim-for-Cygwin in a Cygwin bash terminal, because (unless you want to solve the endless problems of interfacing a Windows gvim [which expects a Dos-like filesystem architecture] with a Cygwin shell [which expects a POSIX filesystem architecture]), you'll have to compile a version of gvim with some flavour of X11 GUI, and display through a Cygwin X11 server. To use individual Cygwin commands in a Windows environment, all disk paths must be translated back and forth. See "man cygpath" under Cygwin. Best regards, Tony. -- You can only live once, but if you do it right, once is enough.
gVim and Cygwin
Does anyone have experience with running gVim and using Cygwin commands (ex. indent)? I would prefer not to run vim in a Cygwin terminal, unless someone has all of the configurations needed (syntax highlighting, etc) to have that act like gVim. Thanks, Bill
