X-Spam-Check-By: sourceware.org
Message-ID: <455A3E5B.2080806@tlinx.org>
Date: Tue, 14 Nov 2006 14:08:27 -0800
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: "Bash Here..." menu option "howto" reg-entry
References: <45550DA4 DOT 6090208 AT tlinx DOT org> <813e5f920611101730i7bd3aa00s34db8af7fefddf90 AT mail DOT gmail DOT com> <45599157 DOT 9090702 AT tlinx DOT org> <45599CD6 DOT 5070508 AT users DOT sourceforge DOT net>
In-Reply-To: <45599CD6.5070508@users.sourceforge.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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



Frank Fesevur wrote:
> Linda Walsh wrote:
>> Yes...it requires installing a separate executable program.
>>
>> This "add bash prompt" requires no 3rd party binary and
>> uses programs already included in the cygwin base package.
>>
>> The installable program also has a bug in that it invokes each
>> shell window as a separate user login, breaking the normal
>> windowing paradigm of one login (starting an X-server, for
>> example), followed by multiple client windows (that don't get
>> started as login windows).
>
> The maintainer of chere reads this list, so I think he will respond.
>
>> Why install extra programs when it can all be done by adding
>> 2 registry keys (1 for directories, 1 for drives)?
>
> The answer is very simple to me. Because you can configure it much 
> better and easier. Why should I *manually* edit a .reg file to change 
> the paths? I don't like to have cygwin installed in c:\ as you 
> apparently have. That is handled by chere for you.
>
> Regards,
> Frank
----
    True, I thought I mentioned the installation in root requirement.

    Basically, if you want *nix utils to *inter-operate*, cleanly,
on windows and *nix files, they, ideally, should have a consistent
path structure in and out of cygwin.  I wanted the *nix tools as
an addition to my win environment, not as a separate world -- if I
want that, I might as well use linux (or use a VM running linux).
I want the *nix tools to make my life easier on Windows.  I can use
*nix tools, largely, to manage my system.  I'm using cygwin as an
integration tool -- not for the purpose of having a 2nd, separate
environment.

    Along the same lines, my Windows home directories are all under
"/Home".  (not an easy process & best done when first setting up the
system).

My *nix and Win worlds share /home -- no conflicts, no problems in 5+ 
years,
same with cygwin root at "/".

Definitely different strokes for different folks...:-)





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/