delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/04/12/16:10:36

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3CB7402D.2010404@dramgo.co.uk>
Date: Fri, 12 Apr 2002 21:14:37 +0100
From: Donald MacVicar <donald AT dramgo DOT co DOT uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.9) Gecko/20020311
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bash shell extension ?
References: <019201c1e1cf$7026dec0$52b4fc3e AT nori> <3CB70C91 DOT 204 AT DeFaria DOT com> <3CB71B61 DOT 6020707 AT dramgo DOT co DOT uk> <3CB7339E DOT 6080409 AT Salira DOT com>

Andrew DeFaria wrote:

> Donald MacVicar wrote:
>
>> Andrew DeFaria wrote:
>>
>>> Sam Edge wrote:
>>>
>>>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere]
>>>> @="&Bash Prompt Here"
>>>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command]
>>>> @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\""
>>>> [HKEY_CLASSES_ROOT\Drive\shell\BashHere]
>>>> @="&Bash Prompt Here"
>>>> [HKEY_CLASSES_ROOT\Drive\shell\BashHere\command]
>>>> @="c:\\cygwin\\bin\\bash.exe -c \"cd '%1' ; exec /bin/bash\""
>>>
>>>
>>>
>>> Personally I'm fond of "Bash this!" instead of "Bash Prompt Here" :-) !
>>>
>>> Also, the above does not handle the issue of the user's startup 
>>> scripts. Here's what I have:
>>>
>>> HKEY_CLASSES_ROOT\Directory\shell\BashHere]
>>> @="B&ash this!"
>>> [HKEY_CLASSES_ROOT\Directory\shell\BashHere\command]
>>> @="rxvt -e bash -c \"cd '%1';exec bash -rcfile ~/.bash_login\""
>>> [HKEY_CLASSES_ROOT\Drive\shell\BashHere]
>>> @="B&ash this!"
>>> [HKEY_CLASSES_ROOT\Drive\shell\BashHere\command]
>>> @="rxvt -e bash -c \"cd '%1';exec bash -rcfile ~/.bash_login\""
>>>
>>> Note if you do not wish to use rxvt then simply remove the "rxvt -e 
>>> " portion. This also makes the assumption that Cygwin's bin is in 
>>> your Windows System Environment variable PATH (which is should be, 
>>> especially if you use inetd) and that you've appropriately named 
>>> your bash startup stuff .bash
>>
>>
>>
>> surely you could just have @="rxvt -ls -e bash -c \"cd '%1'; exec 
>> bash --login\"" and then all the startup scripts would be run properly? 
>
>
> Nope! Because --login runs /etc/profile and /etc/profile cd's to $HOME!


Realised that about 10 secs after I sent the mail.
how about put the --login on the first bash - i.e. txvt -ls -e bash 
--login -c ......
Just tried that and it seems to wok.

Donald.

>
>>
>
>
>
>
> -- 
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019