Tony Mechelynck wrote:
> On 01/07/08 02:39, Ben Schmidt wrote:
>> Bram Moolenaar wrote:
>>> Ben Schmidt wrote:
>>>
>>>> Tony Mechelynck wrote:
>>>>> On 30/06/08 07:01, momodi wrote:
>>>>>> hi
>>>>>> my OS is ubuntu8.04
>>>>>> I installed vim7.2a
>>>>>> but when I open gvim and select Startup Setting.
>>>>>> gvim open a new MYVIMRC file to me.
>>>>>> why?
>>>>>>
>>>>>> when I use vim7.1 gvim will open my .vimrc file to me, which at
>>>>>> ~/.vimrc
>>>>> $MYVIMRC points to the vimrc Vim used in this session, but for some
>>>>> reason that menu entry doesn't resolve the environment variable.
>>>> This is a bug recently introduced with all the security fixes. I sent
>>>> Bram a patch about a fortnight ago, but he evidently hasn't accepted it
>>>> or made a similar modification yet. Here's the patch again:
>>>>
>>>> diff -r 503e0d426e7a runtime/menu.vim
>>>> --- a/runtime/menu.vim Mon Jun 16 00:45:14 2008 +1000
>>>> +++ b/runtime/menu.vim Tue Jun 17 00:23:57 2008 +1000
>>>> @@ -187,17 +187,17 @@
>>>>
>>>>    fun! s:EditVimrc()
>>>>      if $MYVIMRC != ''
>>>> -    let fname = "$MYVIMRC"
>>>> +    let fname = expand("$MYVIMRC")
>>>>      elseif has("win32") || has("dos32") || has("dos16") || has("os2")
>>>>        if $HOME != ''
>>>> -      let fname = "$HOME/_vimrc"
>>>> +      let fname = expand("$HOME")."/_vimrc"
>>>>        else
>>>> -      let fname = "$VIM/_vimrc"
>>>> +      let fname = expand("$VIM")."/_vimrc"
>>>>        endif
>>>>      elseif has("amiga")
>>>>        let fname = "s:.vimrc"
>>>>      else
>>>> -    let fname = "$HOME/.vimrc"
>>>> +    let fname = expand("$HOME")."/.vimrc"
>>>>      endif
>>>>      let fname = s:FnameEscape(fname)
>>>>      if&mod
>>>>
>>>> Hope this helps,
>>> I don't recall seeing this patch.
>> Mmm. I thought it was odd that I hadn't heard from you. I wonder where
>> it went!
>>
>>> I think it can be done simpler
>>> without the expand() calls, since environment variables are recogized?
>> No, that has the exact effect of undoing the patch! The problem is
>> precisely that environment variables are not recognised because
>> FnameEscape escapes the dollar signs. Perhaps the correct solution is
>> just to remove the call to FnameEscape, though? I suppose if you know
>> the environment variables are valid/trust them, and obviously the text
>> "_vimrc" etc. is valid, the call is superfluous anyway.
>>
>> Ben.
>
> On the contrary, the way Bram wrote it below the environment variables
> are resolved before passing their _values_ to FnameEscape()
>
> let fname = $HOME . "/_vimrc"
>
> Notice that $HOME is not quoted: it is a variable, and its _value_ is
> concatenated with "/_vimrc". Then, later, the result is passed to
> FnameEscape().

Thanks for pointing that out, Tony. I didn't look carefully enough.

Yes, that does look good, Bram.

Ben.



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Well I tried the following modes:
- Visual (selecting the code to be refactored before pressing the keys)
- Insert (selecting the code to be refactored before pressing the keys)
- Normal (can't select the code to be refactored before pressing the keys)

When I do this in windows all the winds up happening is I get a funny
character printed (which replaces the text I had selected), followed by a
selection of the Edit menu.  (yeah it's GVIM)


Thank you,
    Andrew J. Leer


Gary Johnson wrote:
>
>
> On 2008-06-30, leeand00 <leeand00@...> wrote:
>
>> Gene Kwiecinski wrote:
>> >
>> >
>> >>It says in the documentation that I should press <A-r>e to call the
>> > Exctract
>> >
>> >>I assumed this to be Alt+r+e but that doesn't seem to yield any
>> > results.
>> >
>> > Nope, I'd read that as being
>> >
>> >  <alt><r/></alt><e/>
>> >
>> > ie, let go of the <alt> key between the 'r' and 'e'.
>
>> All that happens when I do that is I get a whole bunch of "ò" characters
>
> That's what you should get from typing Alt-r, but only if you're in
> insert mode.  The mapping
>
>    map <A-r>e : callExtractMethod()<ENTER>
>
> works in normal mode, not in insert mode.  Which mode are you in
> when you try to invoke the Extract command by typing Alt-r?
>
> Regards,
> Gary
>
>
> >
>
>

--
View this message in context:
http://www.nabble.com/refactor.vim---Keys-to-activate-plugin--tp18203832p1821414\
2.html
Sent from the Vim - General mailing list archive at Nabble.com.


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi,

I just tried
mt atop a directory
mf atop a file
and then mm

should'nt that move the file into the directory.

It didn't on my VIM 7.1 on Windows.

any Idea?

Roland



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 7/1/08, leeand00 <leeand00@...> wrote:
>
>
>  Well I tried the following modes:
>  - Visual (selecting the code to be refactored before pressing the keys)
>  - Insert (selecting the code to be refactored before pressing the keys)
>  - Normal (can't select the code to be refactored before pressing the keys)
>
>  When I do this in windows all the winds up happening is I get a funny
>  character printed (which replaces the text I had selected), followed by a
>  selection of the Edit menu.  (yeah it's GVIM)
>
>

Oh, yuck!

I had trouble with this sort of thing, once.

See :help 'winaltkeys'

Yours may be set to 'yes'. It is certainly set at least to 'menu'. I
have mine set to 'no'...I rarely ever use the menus, and they are slow
enough to use already that a mouse doesn't really slow me down very
much.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

:help suffixes says:

"It is impossible to ignore suffixes with two dots."

Does this mean that I cant do the below?

:set suffixes+=.ann_out.*

If not, why?

:help 'suffixes' says:

"To avoid a dot or comma being recognized as a separator, precede it
with a backslash."

So, could I do the below, instead?

:set suffixes+=.ann_out\.*

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 7/1/08, Benjamin Fritz <fritzophrenic@...> wrote:
> :help suffixes says:
>
>  "It is impossible to ignore suffixes with two dots."
>
>  Does this mean that I cant do the below?
>
>  :set suffixes+=.ann_out.*
>
>  If not, why?
>
>  :help 'suffixes' says:
>
>  "To avoid a dot or comma being recognized as a separator, precede it
>  with a backslash."
>
>  So, could I do the below, instead?
>
>  :set suffixes+=.ann_out\.*
>

It looks like this works:

:set suffixes+=.ann_out\\.txt

But it doesn't seem to work with wildcards...is this the case?

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi,

> Wel, this works for a lot of of commands, but not for.. let's say the search
> window. In MultiEdit there is a window that pops up with several checkboxes
> as searchoptions. Now I want to show instructions that shows how to build
> the roght searchcommand. I will only cover the normal Multiedit options and
> point for more options to the real help file. This message could be shown
> with echo, but when pressing enter the help dissapears.

I found the idea quite interesting so I ... well, I shamelessly copied
it. Maybe it's of some help for you:
http://www.vim.org/scripts/script.php?script_id=2279

This solution to the problem you describe uses the normal help tags by
default. You can use your own tag files though by setting
g:cmdlinehelpTags. It should thus be quite easy to display specific
help files.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

WEB CAM ON ONLINE

New Web cam Software

Simply Five Step To Open Ur Computer

1.Visit  Link===>
              http://www.moreinfo247.com/9560073/CB

2.sign up with your current email id also.

3.then check your mail id(sfi message mail)

4.click the that mail and click 2 link.

5.after 2 minutes u get live web cam sex videos

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

I like this idea.  But ....

I changed the registry entry so that the path is now:

C:\Program Files\Vim\vim70\run_gvim.bat

instead of:

C:\Program Files\Vim\vim70\gvim.exe

run_gvim.bat contains the following:
set HOME=c:\
gvim.exe

When I double click on run_gvim.bat, it works great, but changing the
registry entry and trying to open a vim session using a right mouse
click results in a quick flash of a command prompt window (can't read
what, if anything, is in the window) and nothing else.

Any ideas on how to get this to work?



On Jun 29, 11:55 pm, Ben Schmidt <mail_ben_schm...@...>
wrote:
> awb wrote:
> > The batch file solves my problem, except that I really like and make
> > use of the right mouse click way of getting to vim (didn't think about
> > this until now).  How do I get the right mouse click shortcup to run
> > the batch file that I've created?
>
> Change a registry entry. The .reg file in the sources for the
> right-click .dll does this:
>
> [HKEY_LOCAL_MACHINE\Software\Vim\Gvim]
>     "path"="gvim.exe"
>
> and I see no reason changing that to point to your batch file would
> break anything.
>
> Ben.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 7/1/08, awb <awbuesing@...> wrote:
>
>  I like this idea.  But ....
>
>  I changed the registry entry so that the path is now:
>
>  C:\Program Files\Vim\vim70\run_gvim.bat
>
>  instead of:
>
>  C:\Program Files\Vim\vim70\gvim.exe
>
>  run_gvim.bat contains the following:
>  set HOME=c:\
>  gvim.exe
>
>  When I double click on run_gvim.bat, it works great, but changing the
>  registry entry and trying to open a vim session using a right mouse
>  click results in a quick flash of a command prompt window (can't read
>  what, if anything, is in the window) and nothing else.
>
>  Any ideas on how to get this to work?
>
>

General tip for debugging batch files that run and exit like this:

Temporarily put a "pause" at the end of the batch file.

Or, temporarily put a -f argument to Vim.

The particular cause in your case is probably that gvim.exe is not in
your path. The default windows installer creates batch files for
calling Vim in your path, so you could call those. Or, you could use
the full path to Vim. Or, you could put a "cd" to the directory
containing Vim at the beginning of your batch file.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 7/1/08, Benjamin Fritz <fritzophrenic@...> wrote:
> On 7/1/08, awb <awbuesing@...> wrote:
>  >
>  >  I like this idea.  But ....
>  >
>  >  I changed the registry entry so that the path is now:
>  >
>  >  C:\Program Files\Vim\vim70\run_gvim.bat
>  >
>  >  instead of:
>  >
>  >  C:\Program Files\Vim\vim70\gvim.exe
>  >
>  >  run_gvim.bat contains the following:
>  >  set HOME=c:\
>  >  gvim.exe
>  >
>  >  When I double click on run_gvim.bat, it works great, but changing the
>  >  registry entry and trying to open a vim session using a right mouse
>  >  click results in a quick flash of a command prompt window (can't read
>  >  what, if anything, is in the window) and nothing else.
>  >
>  >  Any ideas on how to get this to work?
>  >
>  >
>
>
> General tip for debugging batch files that run and exit like this:
>
>  Temporarily put a "pause" at the end of the batch file.
>
>  Or, temporarily put a -f argument to Vim.
>
>  The particular cause in your case is probably that gvim.exe is not in
>  your path. The default windows installer creates batch files for
>  calling Vim in your path, so you could call those. Or, you could use
>  the full path to Vim. Or, you could put a "cd" to the directory
>  containing Vim at the beginning of your batch file.
>

Come to think of it, the "-f" won't work if gvim isn't in your path.
I'd try the pause to verify this is the problem (it should be) and
then use one of the suggested methods to fix it.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

It seems like there's something else going on.

I added SLEEP 10 to the end of my batch file and even cleaned out
everything but SLEEP 10.
I get the 10 second pause when I double click on the batch file, but I
dont' when I perform a right click to access this batch file.  I see
that there are many other references to gvim.exe in the registry.  Are
there more modifications that need to be made in addition to the one
mentioned already?



On Jul 1, 11:35 am, "Benjamin Fritz" <fritzophre...@...> wrote:
> On 7/1/08, Benjamin Fritz <fritzophre...@...> wrote:
>
>
>
>
>
> > On 7/1/08, awb <awbues...@...> wrote:
>
> >  >  I like this idea.  But ....
>
> >  >  I changed the registry entry so that the path is now:
>
> >  >  C:\Program Files\Vim\vim70\run_gvim.bat
>
> >  >  instead of:
>
> >  >  C:\Program Files\Vim\vim70\gvim.exe
>
> >  >  run_gvim.bat contains the following:
> >  >  set HOME=c:\
> >  >  gvim.exe
>
> >  >  When I double click on run_gvim.bat, it works great, but changing the
> >  >  registry entry and trying to open a vim session using a right mouse
> >  >  click results in a quick flash of a command prompt window (can't read
> >  >  what, if anything, is in the window) and nothing else.
>
> >  >  Any ideas on how to get this to work?
>
> > General tip for debugging batch files that run and exit like this:
>
> >  Temporarily put a "pause" at the end of the batch file.
>
> >  Or, temporarily put a -f argument to Vim.
>
> >  The particular cause in your case is probably that gvim.exe is not in
> >  your path. The default windows installer creates batch files for
> >  calling Vim in your path, so you could call those. Or, you could use
> >  the full path to Vim. Or, you could put a "cd" to the directory
> >  containing Vim at the beginning of your batch file.
>
> Come to think of it, the "-f" won't work if gvim isn't in your path.
> I'd try the pause to verify this is the problem (it should be) and
> then use one of the suggested methods to fix it.- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi,

On Mon, Jun 30, 2008 at 9:07 AM, Benjamin Fritz <fritzophrenic@...> wrote:
>
> On 6/27/08, Erik Falor <ewfalor@...> wrote:
>> There is no discernable difference between
>> completeopt=menu and completeopt=menu,preview.
>>
>
> So, does anyone have any leads on why this could be? Is there some
> simple option that prevents the preview window from popping up,
> something we aren't doing correctly, or is this a bug?
>
> Can anyone else get completeopt=menu,preview to pop up a preview window?
>

I am able to get the preview window to open when using omni-completion
to display more information about a selected tag with a C file.

- Yegappan

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

svnlog.vim includes a hint to add the following script to ~/.vim/
scripts.vim to autodetect if a particular file is a file containing
Subversion log messages. However, the script seems broken. Here's the
script:

   if did_filetype()       " filetype already set...
       finish              " ...then don't do these checks
   endif
   if getline(1) =~ /^-\{72}$/
       setfiletype svnlog
   endif

When opening a file, I get:

   "/tmp/l" 108L, 5557C
   Error detected while processing /home/adamm/.vim/scripts.vim:
   line    4:
   E15: Invalid expression: /^-\{72}$/
   E15: Invalid expression: getline(1) =~ /^-\{72}$/
   Press ENTER or type command to continue

Anyone know how to fix this?

I'm using the same svnlog.vim  that appears here:
http://dev.pocoo.org/~mitsuhiko/svnlog.vim

I'm using the Vim that comes with Ubuntu 8.04:

   VIM - Vi IMproved 7.1 (2007 May 12, compiled Jan 31 2008 12:00:11)
   Included patches: 1-138

Thank you,

--
Adam Monsen
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

I'm guessing that:

On 7/1/08, Adam Monsen <haircut@...> wrote:
>   if getline(1) =~ /^-\{72}$/
>       setfiletype svnlog
>   endif
>

should be:

if getline(1) =~ /^-\{72\}$/
     setfiletype svnlog
endif

Note the extra \ to make a \{...\} group, specifying a line of 72 '-'
characters.

Apparently this is a common occurrence in svn log files or something.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 7/1/08, Benjamin Fritz <fritzophrenic@...> wrote:
> I'm guessing that:
>
>
>  On 7/1/08, Adam Monsen <haircut@...> wrote:
>  >   if getline(1) =~ /^-\{72}$/
>  >       setfiletype svnlog
>  >   endif
>  >
>
>
> should be:
>
>
>  if getline(1) =~ /^-\{72\}$/
>     setfiletype svnlog
>  endif
>
>
> Note the extra \ to make a \{...\} group, specifying a line of 72 '-'
>  characters.
>
>  Apparently this is a common occurrence in svn log files or something.
>

Oh, and also enclose it in single quotes instead of '/' characters to
make it a string, like this:

'^-\{72\}$'

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Is it possible to have Vim wrap lines when using :hardcopy, and
respect the 'linebreak' option (or similar?).

I know about :set printoptions+=wrap:y, but this wraps character-wise,
not word-wise, which is fairly useless IMO.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 2008-07-01, Benjamin Fritz <fritzophrenic@...> wrote:
> I'm guessing that:
>
> On 7/1/08, Adam Monsen <haircut@...> wrote:
> >   if getline(1) =~ /^-\{72}$/
> >       setfiletype svnlog
> >   endif
> >
>
> should be:
>
> if getline(1) =~ /^-\{72\}$/
>     setfiletype svnlog
> endif
>
> Note the extra \ to make a \{...\} group, specifying a line of 72 '-'
> characters.

According to ":help /\{", the \} is not necessary--just } will
suffice.

Regards,
Gary


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

The batch file needs the full path name, but my full path name:

C:\Program Files\vim\vim70\gvim.exe

was problematic due to the space in the path name.

Since I needed to upgrade to vim 7.1 anyway, I uninstalled vim 7.0 and
installed vim 7.1 in:

C:\vim

instead of in:

C:\Program Files\vim

A right mouse click start of vim now runs my batch file, which opens
vim, but the file I want to edit doesn't open.  I just get the
standard vim welcome screen.



On Jul 1, 12:22 pm, awb <awbues...@...> wrote:
> It seems like there's something else going on.
>
> I added SLEEP 10 to the end of my batch file and even cleaned out
> everything but SLEEP 10.
> I get the 10 second pause when I double click on the batch file, but I
> dont' when I perform a right click to access this batch file.  I see
> that there are many other references to gvim.exe in the registry.  Are
> there more modifications that need to be made in addition to the one
> mentioned already?
>
> On Jul 1, 11:35 am, "Benjamin Fritz" <fritzophre...@...> wrote:
>
>
>
> > On 7/1/08, Benjamin Fritz <fritzophre...@...> wrote:
>
> > > On 7/1/08, awb <awbues...@...> wrote:
>
> > >  >  I like this idea.  But ....
>
> > >  >  I changed the registry entry so that the path is now:
>
> > >  >  C:\Program Files\Vim\vim70\run_gvim.bat
>
> > >  >  instead of:
>
> > >  >  C:\Program Files\Vim\vim70\gvim.exe
>
> > >  >  run_gvim.bat contains the following:
> > >  >  set HOME=c:\
> > >  >  gvim.exe
>
> > >  >  When I double click on run_gvim.bat, it works great, but changing the
> > >  >  registry entry and trying to open a vim session using a right mouse
> > >  >  click results in a quick flash of a command prompt window (can't read
> > >  >  what, if anything, is in the window) and nothing else.
>
> > >  >  Any ideas on how to get this to work?
>
> > > General tip for debugging batch files that run and exit like this:
>
> > >  Temporarily put a "pause" at the end of the batch file.
>
> > >  Or, temporarily put a -f argument to Vim.
>
> > >  The particular cause in your case is probably that gvim.exe is not in
> > >  your path. The default windows installer creates batch files for
> > >  calling Vim in your path, so you could call those. Or, you could use
> > >  the full path to Vim. Or, you could put a "cd" to the directory
> > >  containing Vim at the beginning of your batch file.
>
> > Come to think of it, the "-f" won't work if gvim isn't in your path.
> > I'd try the pause to verify this is the problem (it should be) and
> > then use one of the suggested methods to fix it.- Hide quoted text -
>
> > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 01/07/08 18:13, awb wrote:
> I like this idea.  But ....
>
> I changed the registry entry so that the path is now:
>
> C:\Program Files\Vim\vim70\run_gvim.bat
>
> instead of:
>
> C:\Program Files\Vim\vim70\gvim.exe
>
> run_gvim.bat contains the following:
> set HOME=c:\
> gvim.exe
>
> When I double click on run_gvim.bat, it works great, but changing the
> registry entry and trying to open a vim session using a right mouse
> click results in a quick flash of a command prompt window (can't read
> what, if anything, is in the window) and nothing else.
>
> Any ideas on how to get this to work?

Your run_gvim.bat maybe?

Try adding

	 @echo off

(with the @ sign) as its first line.


Best regards,
Tony.
--
Higgeldy Piggeldy,
Hamlet of Elsinore
Ruffled the critics by
Dropping this bomb:
"Phooey on Freud and his
Psychoanalysis --
Oedipus, Shmoedipus,
I just love Mom."

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 2008-07-01, awb <awbuesing@...> wrote:
> The batch file needs the full path name, but my full path name:
>
> C:\Program Files\vim\vim70\gvim.exe
>
> was problematic due to the space in the path name.

I think surrounding that name in double quotes, i.e.,

    "C:\Program Files\vim\vim70\gvim.exe"

would fix that.

> Since I needed to upgrade to vim 7.1 anyway, I uninstalled vim 7.0 and
> installed vim 7.1 in:
>
> C:\vim
>
> instead of in:
>
> C:\Program Files\vim
>
> A right mouse click start of vim now runs my batch file, which opens
> vim, but the file I want to edit doesn't open.  I just get the
> standard vim welcome screen.

You wrote earlier,

    run_gvim.bat contains the following:
    set HOME=c:\
    gvim.exe

You need to allow the batch file to pass its file-name argument to
gvim by changing that last line to

    gvim.exe %1

HTH,
Gary


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 01/07/08 21:28, awb wrote:
> The batch file needs the full path name, but my full path name:
>
> C:\Program Files\vim\vim70\gvim.exe
>
> was problematic due to the space in the path name.
>
> Since I needed to upgrade to vim 7.1 anyway, I uninstalled vim 7.0 and
> installed vim 7.1 in:
>
> C:\vim
>
> instead of in:
>
> C:\Program Files\vim
>
> A right mouse click start of vim now runs my batch file, which opens
> vim, but the file I want to edit doesn't open.  I just get the
> standard vim welcome screen.

Your batch file should pass its arguments to gvim. Here is a new version:

@echo off
set HOME=C:\
gvim %1 %2 %3 %4 %5 %6 %7 %8 %9


If your gvim.exe is not in the PATH, add its full path, and if that
includes spaces, quote it, as in

"C:\Program Files\Vim\vim71\gvim.exe" %1 %2 %3 %4 %5 %6 %7 %8 %9


Best regards,
Tony.
--
I am not now, nor have I ever been, a member of the demigodic party.
		 -- Dennis Ritchie

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

> Is there a simple way to move text on the currently line to a
> specific column on the same line? For example if the text on
> the current line started in column 10 and I wanted to move it
> to column 20, it there a way to do that?


A couple of answers to some questions would help lead towards a
solution:

- what fills the space?  just spaces?

- if you're in the middle of something such as

     int xi;

    and the cursor is on the "x", do you want the whole thing
indented to the given position, or do you only want the stuff
from the cursor to move to the given position?

- how do you determine the destination position?  is it always
column 20?  something you'd set for a time period but change
while editing the same document?  is it aligned with something else?

You may also be interested in Dr. Chip's align.vim script

http://www.vim.org/scripts/script.php?script_id=294

It may do what you want, but if not, the answers to the questions
above may help folks make a mapping to do what you describe.

-tim



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

* awb <awbuesing@...> [080701 13:22]:
>
> It seems like there's something else going on.
>
> I added SLEEP 10 to the end of my batch file and even cleaned out
> everything but SLEEP 10.
> I get the 10 second pause when I double click on the batch file, but I
> dont' when I perform a right click to access this batch file.  I see
> that there are many other references to gvim.exe in the registry.  Are
> there more modifications that need to be made in addition to the one
> mentioned already?
>
> On Jul 1, 11:35 am, "Benjamin Fritz" <fritzophre...@...> wrote:
> > On 7/1/08, Benjamin Fritz <fritzophre...@...> wrote:
> >
> > > On 7/1/08, awb <awbues...@...> wrote:
> >
> > >  >  run_gvim.bat contains the following:
> > >  >  set HOME=c:\
> > >  >  gvim.exe
> >

(Please bottom post rather than top post.)

You are probably missing two things.  First (and the likely cause of
the quick flash without seeing anything) you probably need the full path
to gvim in your batch file.  Second, if you change that, you will
probably get a new edit session without the file that you thought you
were opening.  You must add the batch file parameter to the gvim command
line.  Try the following batch file:

set HOME=c:\
"C:\Program Files\Vim\vim70\gvim.exe" "%1"

The quotes are necessary because of the space in the path to gvim and
the possibility of spaces in the name of the file to be edited.  This
should work when only one file is selected.

When you select multiple files in the file explorer and right click, two
of the menu items should be "Edit in multiple Vims" and "Edit in single
Vim".  I'm not sure how the context handlers decide what command to run;
it is likely to be a different registry entry than the one you have
already modified.  The entry for "Edit in single Vim" needs to use a
different batch file:

set HOME=c:\
"C:\Program Files\Vim\vim70\gvim.exe" -p %*

You can replace -p with -o if you want separate Vim windows (not Windows
windows) rather than separate tabs.  Remove -p if you just want to edit
the files one at a time with :next.

The %* notation does not work in Win 98, but it works in Win 2000 and
XP.  This will pass all batch file parameters (properly quoted) to gvim.
In fact, if you are not using Win 98, this batch file will probably
suffice for editing a single file as well as multiple files.

...Marvin


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi guys,
Could you, please, let me know in which version the fix is expected?
Thanks a lot.

On Jun 21, 5:45 am, Ben Schmidt <mail_ben_schm...@...> wrote:
> > I found what looks like the right manual page for
> > cygwin_conv_to_posix_path(), and it mentions using a buffer of size
> > MAX_PATH.  So that's what I'll use.  Literally it says "Note that
> > posix_path must point to a buffer of sufficient size; use MAX_PATH if
> > needed.".  No idea what "if needed" means here, thus they might nog have
> > thought about this much.
>
> I think they mean "unless you know for sure that something smaller will
> do" which I presume means you have a full absolute path that you know
> contains no short 8.3 style components, so the most that could happen is
> have "C:" change into "/cygdrive/c" so you'd know that at most the
> string could expand by 9 characters.
>
> Ben.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

>Is there a simple way to move text on the currently line to
>a specific column on the same line? For example if the text
>on the current line started in column 10 and I wanted to
>move it to column 20, it there a way to do that?

Absolutely, but there also be so many variables and so many ways to do
such a thing, that it's best if you just demonstrate a before'n'after as
to what you want.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Jeff Lanzarotta wrote:
> Hello,
>
> Is there a simple way to move text on the currently line to a specific
> column on the same line? For example if the text on the current line
> started in column 10 and I wanted to move it to column 20, it there a
> way to do that?
1.   a) goto column 10:   10|
       b) insert ten spaces:   10i <esc>

2. Use DrawIt: (http://mysite.verizon.net/astronaut/vim/index.html#DRAWIT)
     a) Enable DrawIt:  \di
     b) use leftmouse to select text
     c) release leftmouse button
     d) use ctrl-leftmouse and move text wherever

     This approach will work with visual blocks, so its not restricted to
just text on a line.

3. As Tim C said, if your purpose is aligning text in columns, Align.vim
may be what you want

Regards,
Chip Campbell


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 7/1/08, Gary Johnson <garyjohn@...> wrote:
>
>  On 2008-07-01, Benjamin Fritz <fritzophrenic@...> wrote:
>  > I'm guessing that:
>  >
>  > On 7/1/08, Adam Monsen <haircut@...> wrote:
>  > >   if getline(1) =~ /^-\{72}$/
>  > >       setfiletype svnlog
>  > >   endif
>  > >
>  >
>  > should be:
>  >
>  > if getline(1) =~ /^-\{72\}$/
>  >     setfiletype svnlog
>  > endif
>  >
>  > Note the extra \ to make a \{...\} group, specifying a line of 72 '-'
>  > characters.
>
>
> According to ":help /\{", the \} is not necessary--just } will
>  suffice.
>

Oh, so it can...I missed that somehow. Cool.

It does need to be a string though, rather than surrounding it with '/'.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---