Gary thanks for the answer, this is good start for me.
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Hi
I am trying to use this format to search certain folders that are
designed within the variable
This line
:grep -i random $INCLUDES/*
nor this line works
:!grep -i random $INCLUDES/*
but this line inside Cygwin shell works(Mintty in this case)
grep -i random $INCLUDES/*
Windows User env
Chris
I do have Cygwin here and I cannot tell which grep Vim(windows
version) uses to be honest, since I cannot get grep to print the
platform but I believe it is the windows version from Windows Gnu
utilities which has v 2.5 while Cygwin version is 2.6. I have both
greps in my system because I
Gary thank you for very detail follow up on this. It helped me to see
some of the issues.
You are right that I have set up the grepprg in my rc
set grepprg=grep\ -niH
-Cmd.exe
grep -i random %INCLUDES%/*
--works--
- Gvim(win32)
:grep -i random \%INCLUDES\%/*
--works--
This way I am also able
Hi
I want to be able to setup couple different Vims, like for editing,
for projects etc. i want them to be totally separate installations and
have different plugins script base. What would eb the best optimum
way?
thanks
--
You received this message from the vim_use maillist.
Do not top-post!
Hi
I have a command like this
:command MYGREP grep -ir --color ./*
I want to be able to inject a variable to this command. So I want to
use like MYGREP position. But I want the position to appear in
right place. So when it is extended it would be a proper grep command
grep -ir --color position
Charles, thanks for pointing out the right direction. That was helped
me out.
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Ben
In the latest vim C syntax file it is corrected, I mean it does not
highlight double slashes as error. So I presumed that it was a mistake
in the original version
On Mar 3, 5:18 pm, Ben Fritz fritzophre...@gmail.com wrote:
On Mar 2, 4:32 pm, kuru maymunbe...@gmail.com wrote:
Hugh thanks
Hi
Currently when ever I open .c files, // comment lines show up as
errors based on the color syntax. I have tried the latest c.vim from
last November which seems to resolve the issue but that one is
relatively shorter and not as extended as the previous c.vim syntax
file. So I am trying to find
CCommentError, so I diverted it to comment as you have
suggested.
Thanks again. that was great work around. it does not take care of the
root of the problem but it is a great solution
On Mar 2, 11:49 am, Christian Brabandt cbli...@256bit.org wrote:
Hi kuru!
On Mi, 02 M r 2011, kuru wrote
Hi
I know this is not a Gnu Globals forum but I am sure that there are
Gnu Globals users amoung Vim users. I have been trying to setup Gnu
Globals with Vim. I have gone through the Gnu globals documentation
whcih is pretty good, seems to explain most of the stuff. There is one
thing I cannot
11 matches
Mail list logo