public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Ed Bradford/Raleigh/IBM" <egb@us.ibm.com>
To: "Cygwin (E-mail)" <cygwin@sourceware.cygnus.com>
Subject: Re: Re. Bash Prompt Here
Date: Tue, 03 Oct 2000 08:22:00 -0000	[thread overview]
Message-ID: <OFBB1561E0.D645CEF6-ON8525696D.00543838@raleigh.ibm.com> (raw)

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

             reply	other threads:[~2000-10-03  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-03  8:22 Ed Bradford/Raleigh/IBM [this message]
2000-10-03 11:27 ` Larry Hall (RFK Partners, Inc)
  -- strict thread matches above, loose matches on Subject: below --
2000-10-03 12:16 Ed Bradford/Raleigh/IBM
2000-10-03 12:04 Earnie Boyd
2000-10-03 11:34 Bernard Dautrevaux
2000-10-03  9:19 Frank Merenda
2000-10-03  7:46 Barry Buchbinder
2000-10-03  7:15 Ed Bradford/Raleigh/IBM
2000-10-03  7:08 Barry Buchbinder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=OFBB1561E0.D645CEF6-ON8525696D.00543838@raleigh.ibm.com \
    --to=egb@us.ibm.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).