Re: Re: opening files in win NT
- Any chance this group could be split into M$ and a *nix groups?
--- John Kilbourne <jkilbour@...> wrote:
>I don't know if i messed up somehting in doing this, but I do not_____________________________________________________________
>have a "gvim.exe" "%1" file, just a gvim.exe, which I have set as the
>executable. How important is the -space_percent_1 part, and how do I
>get that file back?
>------------------ Reply Separator --------------------
>Originally From: "Alex Angelopoulos" <alex@...>
>Subject: Re: opening files in win NT
>Date: 01/01/2002 05:54pm
>Make sure GVim is set as the registered handler for openiong those,
>of course. To get it to open correctly, if you go and check the
>file types, you shuld have something like this defined as the command
>for opening -
>A simple trick I always do is put a shortcut to vim into my "SendTo"
>folder - this opens things correctly even if there are spaces
>in the path, since Windows correctly interprets it.
>----- Original Message -----
>From: "John Kilbourne" <jkilbour@...>
>Sent: Tuesday/2002 January 01 17:14
>Subject: opening files in win NT
>: I have set the Windows Explorer settings (View->Options->FileTypes-
>: >etc.) to use GVim as the default file opener for C,cpp and other
>: file extensions, but when I double click on such files I get a blank
>: gvim window. I must go to File-Open and manually open the file to be
>: able to edit in GVim. I don't know if this is a Windows problem or a
>: vim problem, but it is *my* problem. How can I make it so I can
>: double click on a file to edit it in Windows?
>: Thank you.
Want a new web-based email account ? ---> http://www.firstlinux.net
On Wed, Jan 02, 2002 at 11:49:16AM -0500, John Kilbourne wrote:
| I don't know if i messed up somehting in doing this, but I do not
| have a "gvim.exe" "%1" file, just a gvim.exe, which I have set as the
| executable. How important is the -space_percent_1 part,
If you leave out that %1, then gvim gets no arguments and doesn't have
any clue that you double-clicked on a file or that you want to open
it. The %1 is a placeholder for the first argument (the file name).
Just putting <space>%1 is a problem though if you put spaces in a file
name because space separates arguments. Thus you need to quote the
argument to keep the spaces where they belong.
Only two things are infinite, the universe and human stupidity, and I'm
not sure about the former.