This is the mail archive of the cygwin@sources.redhat.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Re. Bash Prompt Here



You can download X-Setup from http://www.xteq.com/ (it's free)
and install it. 
There's an option under "Appearance | Explorer | Context Menu | Files
Commands" that will let you add programs to the context menu of any file.
Just add the file name and description (i.e. vim.exe %1, if VIM is in your
PATH ) and X-Setup will add the registry key for you. X-Setup also has loads
of other tweaks for Windows, I highly recommend it. And no, I'm not
associated with xteq in any way.... :)

-Peace Out-
Frank Merenda | Senior Software Engineer
VetMedCenter | http://www.VetMedCenter
fmerenda@VetExchange.com

"Don't believe the hype." 

-- Public Enemy

> -----Original Message-----
> From: Ed Bradford/Raleigh/IBM [mailto:egb@us.ibm.com]
> Sent: Tuesday, October 03, 2000 11:23 AM
> 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.
> 
> Ed
> 
> Your Windows 2000 Arborist
> T/L 589-4410; Outside: 1-919-993-4410
> egb@us.ibm.com
> 
> 
> Barry Buchbinder <BBUCHBINDER@niaid.nih.gov>@sources.redhat.com on
> 10/03/2000 10:46:11 AM
> 
> Sent by:  cygwin-owner@sources.redhat.com
> 
> 
> To:   "Cygwin (E-mail)" <cygwin@sourceware.cygnus.com>
> cc:
> Subject:  Re. Bash Prompt Here
> 
> 
> 
> You're right!  Here's an updated BashHere.reg.  One will have 
> to edit it to
> get bash invoked the way one wants.
> 
> - Barry Buchbinder
> 
> ============
> You should also include "Drive" where "Directory" is below. 
> That way, when
> you right click on a drive, you can get a "Bash here" also.
> 
> I used
>      f:\cyg\bin\bash.exe -i
> and I had to train my .bashrc to do most of the stuff in 
> /etc/profile to
> avoid the cd $HOME issue. After that, all works as expected.
> 
> Ed
> 
> Your Windows 2000 Arborist
> T/L 589-4410; Outside: 1-919-993-4410
> egb@us.ibm.com
> 
> Barry Buchbinder <BBUCHBINDER@niaid.nih.gov>@sources.redhat.com on
> 10/03/2000 10:07:51 AM
> 
> Sent by:  cygwin-owner@sources.redhat.com
> 
> To:   "Cygwin (E-mail)" <cygwin@sourceware.cygnus.com>
> Subject:  Re. Bash Prompt Here
> 
> The following works for me on Win98.  Since one doesn't 
> logon, there is no
> cd to $HOME and bash starts in whatever directory Windows 
> tells bash it is
> in.  Of course, this won't work if .bashrc has a cd command in it.
> 
> - Barry Buchbinder
> 
> REGEDIT4
> 
> [HKEY_CLASSES_ROOT\Directory\shell\BashHere]
> @="&Bash Prompt Here"
> 
> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command]
> @="c:\\cygwin\\bin\\bash.exe"
> 
> 
> 
> 
> --
> 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
> 

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]