From: Hans F. N. <ha...@mi...> - 2004-06-28 00:34:04
|
[Changed subject to fit topic.] On Sun, Jun 27, 2004 at 08:23:17PM -0400, Alan G Isaac wrote: > On Mon, 28 Jun 2004, Hans Fredrik Nordhaug apparently wrote: > > Then try "kpsewhich tex.pro" - it should return > > [...]/texmf/dvips/base/tex.pro > > > OT, I guess. > I am puzzled by the behavior of kpsewhich. > If I go to > http://www.csit.fsu.edu/~mimi/tex/doc/html/manpages/kpsewhich.html > I get a description that matches expectations. > But if I type > kpsewhich --help > > Usage: kpsewhich [OPTION...] [FILENAME] > This program tries to locate a TeXMF related file. > Options: > -alias=APP Pretend to be APP. > -help Print this help screen and exit. > -file-type=FILETYPE Use the search path for FILETYPE. > -must-exist Make sure the file exists; run the package > installer if necessary. > -show-path=FILETYPE Show the search path for FILETYPE. > -start Start associated program if file was found. > -version Print the version number and exit. > > Note that the short options are not listed, not all long > options are listed, and the long options take a single dash > rather than the expected double dash, according to this > help. > > Finally, both the listed options seem to work with either a > single-dash or double-dash. All very odd. > > I thought the convention that long options are preceeded by > a double dash was very well established ... I agree that the option usage/help should be cleaned up. However, posting here won't solve anything. File a feature/bug report and things might improve :-) Hans |