Maybe the better fix would be renaming all the nodes in coreutils.texi to
comply with this convention?
I think the node names should stay as they are. The convention is
either Invoking xxx or xxx invocation.
http://www.gnu.org/prep/standards/html_node/Manual-Structure-Details.html
I
[EMAIL PROTECTED] (Karl Berry) wrote:
Maybe the better fix would be renaming all the nodes in coreutils.texi
to
comply with this convention?
I think the node names should stay as they are. The convention is
either Invoking xxx or xxx invocation.
On Sun, Jan 27, 2008 at 01:34:36PM -0600, Karl Berry wrote:
What this report really says to me is that the dir file was not
correctly created by the Debian (or whatever) installation process.
Oh, without a doubt. The debian install-info routine (IIRC) predates the
gnu install-info, and hasn't
On Sun, Jan 27, 2008 at 09:30:51PM +0100, Jim Meyering wrote:
Yes, that is the root of the problem.
It came down to a dispute about which of two install-info
programs should be installed. I'm amazed that it's lasted
so long (it seems it's been at least two years, now).
I don't think it's a
Jim Meyering [EMAIL PROTECTED] writes:
Another reason to use the more verbose command is to ensure that info
reliably displays the right node. Even with a proper installation, info
pr doesn't display the desired node (as you probably recall). Instead,
info simply displays the first node it
jimm info simply displays the first node it finds with a name matching
jimm pr. In my case, it is currently the PreScript node of a2ps.info.
What? That makes no sense to me at all. Info doesn't look inside every
info file randomly looking for nodes to match. It has to be in a dir
mstone The debian install-info routine (IIRC) predates the
gnu install-info,
That wasn't my understanding, but I never actually researched it. I was
not aware of any Debian ii at the time that rms wrote GNU ii (I was
maintaining Texinfo by then -- 1996), but then, I probably wouldn't
On Sun, Jan 27, 2008 at 06:51:54PM -0600, Karl Berry wrote:
mstone The debian install-info routine (IIRC) predates the
gnu install-info,
That wasn't my understanding, but I never actually researched it. I was
not aware of any Debian ii at the time that rms wrote GNU ii (I was
I've given up on the debian install-info ever being fixed. My new
thought on this is to simply modify the man page to say something like:
SEE ALSO
The full documentation for ls is maintained as a Texinfo
manual. If the info and ls programs are properly installed
at your
Michael Stone [EMAIL PROTECTED] wrote:
I've given up on the debian install-info ever being fixed. My new
thought on this is to simply modify the man page to say something
like:
SEE ALSO
The full documentation for ls is maintained as a Texinfo
manual. If the info and ls programs are
Jim Meyering wrote:
Michael Stone wrote:
The full documentation for ls is maintained as a Texinfo
manual. If the info and ls programs are properly installed at
your site (on debian they aren't), the command
info ls
should give you access to the
[EMAIL PROTECTED] (Bob Proulx) wrote:
I think it should be the normal case for all of the coreutils commands
and not the special case just for pr. Why not have this done uniformly?
info coreutils ls invocation
To me that looks nice enough to be used for all of the commands. Most
people
[EMAIL PROTECTED] (Bob Proulx) wrote:
Jim Meyering wrote:
Michael Stone wrote:
The full documentation for ls is maintained as a Texinfo
manual. If the info and ls programs are properly installed at
your site (on debian they aren't), the command
info ls
On Sat, Jan 26, 2008 at 06:09:27PM +0100, Jim Meyering wrote:
Another down side: it requires web access.
Yup.
What do you think of info
coreutils ls? It doesn't work for info coreutils pr (because info
matches the pr in the earlier Printing text node, but I suppose I
could special case that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 1/26/2008 11:39 AM:
|
| I've just applied this:
|
| 2008-01-26 Jim Meyering [EMAIL PROTECTED]
|
| Emit info coreutils 'PROG invocation' into the man page,
| rather than just info PROG. The latter would
Eric Blake [EMAIL PROTECTED] wrote:
According to Jim Meyering on 1/26/2008 11:39 AM:
|
| I've just applied this:
|
| 2008-01-26 Jim Meyering [EMAIL PROTECTED]
|
| Emit info coreutils 'PROG invocation' into the man page,
| rather than just info PROG. The latter would often fail
On Sat, Jan 26, 2008 at 11:14:49AM -0700, Bob Proulx wrote:
I think it should be the normal case for all of the coreutils commands
and not the special case just for pr. Why not have this done uniformly?
info coreutils ls invocation
That might work.
Mike Stone
--
To UNSUBSCRIBE, email to
Michael Stone wrote:
Frankly, I suspect that a whole lot of people would rather have a
web interface anyway--there aren't many who think the info interface
is all that friendly...
Unfortunately then there is the problem of upstream documentation and
downstream stable release programs being out
On Sat, Jan 26, 2008 at 01:12:13PM -0700, Bob Proulx wrote:
Unfortunately then there is the problem of upstream documentation and
downstream stable release programs being out of sync with each other.
There would be the potential for bts reports from users saying such
and such a feature is
Package: coreutils
Version: 5.97-5
Severity: normal
man ls tells me that info ls should give me full documentation,
but it just shows me the man page again.
This may be related to these bugs:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=244658 (basename)
20 matches
Mail list logo
