This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: Re. Bash Prompt Here
- To: "Cygwin (E-mail)" <cygwin at sourceware dot cygnus dot com>
- Subject: RE: Re. Bash Prompt Here
- From: "Ed Bradford/Raleigh/IBM" <egb at us dot ibm dot com>
- Date: Tue, 3 Oct 2000 15:16:37 -0400
Ok, thanks to all for their contributions. The following works:
HKEY_CLASSES_ROOT\*\shell -- had to create
XQXSETCMD1 - is what X-Setup creates
ABC - is what I created instead - I gave it a
value of "Edit with VIM"
command - I gave it a value of "vim %1"
Now the only problem is that VIM complains with "unable to open swap file".
If I go to the directory
directly in a bash box and enter
vim xxx
all is well.
It is only the * entry that is needed. The "unknown" only works for files
whose extension is not recognized or files
that do not have an extension (suffix). Are there any quick ideas on why
vim is complaining about the swap file?
Thanks
Ed
Your Windows 2000 Arborist
T/L 589-4410; Outside: 1-919-993-4410
egb@us.ibm.com
Bernard Dautrevaux <Dautrevaux@microprocess.com>@sources.redhat.com on
10/03/2000 02:24:40 PM
Sent by: cygwin-owner@sources.redhat.com
To: Ed Bradford/Raleigh/IBM@IBMUS, "Cygwin (E-mail)"
<cygwin@sourceware.cygnus.com>
cc:
Subject: RE: Re. Bash Prompt Here
> -----Original Message-----
> From: Ed Bradford/Raleigh/IBM [mailto:egb@us.ibm.com]
> Sent: Tuesday, October 03, 2000 5:23 PM
> To: Cygwin (E-mail)
> Subject: Re: Re. Bash Prompt Here
>
>
> One final question problem for the group to address. Some
> versions of vim
> install stuff
> in the registry so that when you right click ANY file, you
> get the choice
> of "Edit with vim". I have
> not been able to find a simple registry hack to make that
> happen without
> having a registered
> dll. Also, it wasn't exactly clear to me how to train the VIM
> dll to use
> something else. I must have spent
> less than 5 minutes looking at it.
>
> Has anyone figured out how to do this? I have tried just
> putting stuff in
> the HKCR/file registry key but that
> doesn't seem to do it.
Hi,
IIRC, just look at HKEY_ROOT_CLASSES\Unknown\shell. All keys created
here are used by default for any file for which there is no explicit class.
For others I'm afraid you have to add a command for *all* HKRC\*\shell keys
;-(
I really hope someone knows a better solution,
Bernard
--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: dautrevaux@microprocess.com
b.dautrevaux@usa.net
--------------------------------------------
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com