On 09/09/2014 04:55 AM, Paul Eggert wrote:
Subject: [PATCH 1/4] doc: mention which commands are optional
I was thinking that the bst way to do that would be to adjust things
so that the node wasn't installed if the command wasn't. But it's better
to have this info generally available online
On 09/09/2014 10:52 AM, Michael Stone wrote:
On Tue, Sep 09, 2014 at 03:31:35PM +0100, Pádraig Brady wrote:
It's useful to many, but I agree most don't bother with it
due to the awkward non intuitive default info reader _interface_
(though pinfo is a bit better in that regard).
Right. I've
On 09/09/2014 05:58 PM, Assaf Gordon wrote:
On 09/09/2014 10:52 AM, Michael Stone wrote:
On Tue, Sep 09, 2014 at 03:31:35PM +0100, Pádraig Brady wrote:
It's useful to many, but I agree most don't bother with it
due to the awkward non intuitive default info reader _interface_
(though pinfo is
Vincent Lefevre wrote:
Assaf Gordon wrote:
BTW,
http://gnu.org/s/; redirects to http://www.gnu.org/software/; ,
so
http://gnu.org/s/coreutils/ls
also works.
But isn't it better to avoid a redirection (if possible)?
I think it is better to use the canonical form. This will be
I normally build with --disable-dependency-tracking to speed up builds,
and also build out-of-tree, and got this with the latest coreutils:
$ cd /foo/bar/coreutils-8.23
$ mkdir _build
$ cd _build
$ ../configure --disable-dependency-tracking
checking for a BSD-compatible
