On 2009-12-04, James Kanze wrote:
> On Dec 3, 7:30 pm, Gary Johnson <[email protected]> wrote:
> > On 2009-12-03, James Kanze wrote:
> > > :args ! egrep -l 'some string' *.{h,cpp}
> > Are you sure this used to work under Unix?
>
> I don't have access to a Unix machine at present, so I can't
> verify, but I am pretty sure that I've done this under Unix.
> Andy's post, however, suggests that I might have been using a
> different syntax, so that's likely the problem.
Until Andy's post I didn't know about backtick expansion within vim.
That's really handy.
> > Are you using Cygwin's vim or Windows' vim? While you _can_
> > use Cygwin's bash from Windows' vim, I don't recommend it.
> > Sooner or later you will run into a problem, usually with path
> > names. IMO, it's just not worth the hassle. If you want to
> > use vim as you would on Unix, use Cygwin's vim.
>
> I'm using the Windows build of vim. I'm also only using parts
> of Cygwin; for various reasons, many of the utilities also come
> from direct Windows ports. And I am having problems with the
> filenames. Not just from vim. What I'll probably end up doing
> is using direct Windows ports for everything, since I can't
> avoid using some Windows programs (e.g. cl), which expect
> Windows filenames, and the CygWin version of some of the tools
> (e.g. make) isn't as up to date as I'd like.
>
> Not relevant to this group, but why do CygWin and MSys insist on
> using only their version of filenames. All it does is make them
> unduly difficult to use. (If I didn't need to use Windows
> programs as well, there'd be no problem. But if I didn't need
> to use Windows programs, I'd just install Linux and be done with
> it.)
The goal of Cygwin is to create a POSIX or Linux-like environment
that runs on Windows. This is different from providing a Unix-like
tool set that runs on Windows. The advantages to Cygwin's approach
are that programs written for Linux will compile and run without
modification under Cygwin and Cygwin's bash command line behaves
exactly as bash does on Linux. The disadvantage is that Cygwin
programs don't integrate seamlessly with Windows programs. It's a
tradeoff. In some situations, using a tool set such as GNUWin32 is
a better choice.
Regards,
Gary
--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
