Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: ericblake AT comcast DOT net (Eric Blake) To: Herb Martin , cygwin AT cygwin DOT com Subject: RE: Another (differently) broken man on CygWin 1.5.8 -- Apropos still troublesome Date: Mon, 15 Aug 2005 15:00:49 +0000 Message-Id: <081520051500.6300.4300AE21000197AE0000189C22007614380A050E040D0C079D0A@comcast.net> X-Authenticated-Sender: ZXJpY2JsYWtlQGNvbWNhc3QubmV0 > There is a man directory in /usr/bin, i.e., /usr/bin/man -- > with man.exe being the program, while manpath gives: This sentence was confusing. Are you telling me that /usr/bin/man exists and is a directory (does it have normal subdirectories like man1?), and that /usr/bin/man.exe exists and is the program? I'm trying to see if there is anything weird about auto-.exe magic in coreutils. > > $ manpath > /usr/local/man:/usr/share/man:/usr/man:/usr/X11R6/man:/usr/ssl/man:/usr/X11R > 6/share/man > > $ which apropos > /usr/bin/apropos > > $ link /usr/bin/man.exe /usr/bin/man > link: cannot create link `/usr/bin/man' to `/usr/bin/man.exe': File exists What were you trying here - to create /usr/bin/man as an alternate spelling of man.exe? Would 'ln -f' work better than 'link' did? link(1) currently does not do extra .exe magic, only ln(1). I'll have to check if ln(1) has problems if the non-.exe version exists as a directory, and decide whether link(1) should do .exe magic... > > $ which man.exe > /usr/bin/man.exe > > Man works, but I cannot build a link from man->man.exe due to > the directory with the same name: > > $ man > What manual page do you want? > > Running hash against /usr/bin/man without adding the > .exe fails this way: > > $ hash -p /usr/bin/man man > bash: hash: /usr/bin/man: Is a directory > > This seems to work but doesn't fix apropos: > $ hash -p /usr/bin/man.exe man > bash: hash: /usr/bin/man: Is a directory > That is sounding a bit weird. I'll have to see if I can reproduce that, and if it implies a bug in bash's hashing. No guarantees of when, though, since it seems you've solved your problem by getting rid of the /usr/bin/man/ directory. -- Eric Blake volunteer cygwin bash/coreutils maintainer -- 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/