This is the mail archive of the
mailing list for the Cygwin project.
RE: "which" command does not expand "~" in path
- From: Errol Smith <errol at ros dot com dot au>
- To: cygwin mailing-list <cygwin at cygwin dot com>
- Date: Wed, 29 Sep 2004 01:08:42 +1000
- Subject: RE: "which" command does not expand "~" in path
At 09:23 PM 26/09/2004, "Hannu E K Nevalainen" wrote:
FWIW; 'man bash' has a section on Tilde Expansion - I take it as; bash does
this expansion for you, not which.exe -> use $HOME when not typing at the
This is all fine & good, but it doesn't change the fact that the
cygwin-supplied "which" does NOT work with the cygwin-supplied
".bash_profile" (when you use a personal ~/bin directory.).
Here is a simple patch which fixes half the problem (the ".bash_profile"
placing a raw ~ in the path):
--- /etc/skel/.bash_profile 2004-05-15 21:40:04.000000000 +1000
+++ .bash_profile 2004-09-29 00:21:50.000000000 +1000
@@ -10,16 +10,16 @@
# Set PATH so it includes user's private bin if it exists
# if [ -d ~/bin ] ; then
# Set MANPATH so it includes users' private man if it exists
# if [ -d ~/man ]; then
# Set INFOPATH so it includes users' private info if it exists
# if [ -d ~/info ]; then
This won't help anyone who expects the cygwin "which" command to be the
same as the GNU version regarding the tilde character in paths (OK, so
maybe that would be rare), but it will stop people running into it using
cygwin's defaults. (I fixed the MAN & INFO paths for consistency).
btw, does anyone know why those private paths are commented out by default?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html