public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "karl at freefriends dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug manual/13248] Provide the Next link on a node at the bottom of the page for that node ...
Date: Mon, 03 Oct 2011 22:27:00 -0000	[thread overview]
Message-ID: <bug-13248-131-VXRYAmOaNf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13248-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13248

--- Comment #2 from Karl Berry <karl at freefriends dot org> 2011-10-03 22:26:16 UTC ---
Hi guys,

1) In general, nodes are short.  It would be annoying to have nav links at the
bottom of those.  So I don't think it would be right to change the default,
even for libc (which has more long nodes than "usual", granted).

2) It's conceivable to put nav links at the bottom only of "long" nodes, for
some definition of "long".  This feature might already be in the new makeinfo,
I confess I've lost track of everything that's been added.  If not it can be
done for a future release.  I'll check it on the Texinfo side.

Best,
Karl

P.S. libc folks: I haven't forgotten about my promise to document the online
manual publishing process.  It remains high on the list, even though it doesn't
seem like it :(.  Sorry.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-10-03 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-02 14:44 [Bug manual/13248] New: " kedar.mhaswade at gmail dot com
2011-10-03 16:42 ` [Bug manual/13248] " roland at gnu dot org
2011-10-03 22:27 ` karl at freefriends dot org [this message]
2014-06-27 11:58 ` fweimer at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-13248-131-VXRYAmOaNf@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).