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/
