reassign 369619 coreutils
retitle 369619 wishlist: ptx should have its own info page
thanks
Hi Dan!
On Die, 06 Jun 2006, Dan Jacobson wrote:
> NP> Info would have to check *every* node in *every* info file, ie reading
> NP> all info files, checking all node texts, and probably finding 20
> NP> occurences of ptx in these files. Which one should be shown?
> Naw... just as Debian has only one ptx command on PATH, there should
> only be one on "INFOPATH":
Nup, it doesn't work like this. It is true there an info pages, and if
ptx has an info page, then
info ptx
will work.
But info has the additional feature that it can jump from the command
line to sub-sections (called nodes) in an info file.
But ptx doesn't have its own info file, so
info ptx
cannot work. The information for ptx in the info file is hidden in
subsection 7.6 of the coreutils info file.
> NP> get with "info ptx" the right stuff. If it is hidden in some node of the
> NP> info document named differently, then you cannot accept much better?
> Can't it still get written into a link from the top level info directory
> or something?
Well, this is something the coreutils authors should do.
I have reassigned this bug to coreutils, as it definitely is not a
problem of info.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining <preining AT logic DOT at> Università di Siena
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
`We've got to find out what people want from fire, how
they relate to it, what sort of image it has for them.'
The crowd were tense. They were expecting something
wonderful from Ford.
`Stick it up your nose,' he said.
`Which is precisely the sort of thing we need to know,'
insisted the girl, `Do people want fire that can be fitted
nasally?'
--- Ford "debating" what to do with fire with a marketing
--- girl.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
