From: Andy Wingo <wingo@pobox.com>
To: saffronsnail@hushmail.com
Cc: 25293@debbugs.gnu.org
Subject: bug#25293: More descriptive page titles in documentation?
Date: Mon, 09 Jan 2017 22:56:09 +0100 [thread overview]
Message-ID: <87d1fvaoee.fsf@pobox.com> (raw)
In-Reply-To: <20161229184328.154BC40174@smtp.hushmail.com> (saffronsnail@hushmail.com's message of "Thu, 29 Dec 2016 10:43:27 -0800")
On Thu 29 Dec 2016 19:43, saffronsnail@hushmail.com writes:
> Frequently when I am working on guile code I have a few tabs open with
> particular sections of interest open. The titles of the pages all
> start with "Guile Reference Manual", which is not useful when
> switching between tabs. Would it be possible to retitle the pages so
> that the name of the section is first? For example, right now I have
> section 6.19.3 open and the title is "Guile Reference Manual: Creating
> Guile Modules". I also have section 6.20.6 open and the title is
> "Guile Reference Manual: Dynamic FFI". The names displayed in the tabs
> are both "Guile Referenc Man...". Rearranging the titles to be
> "Creating Guile Modules: Guile Reference Manual" and "Dynamic FFI:
> Guile Reference Manual" would make it easier to go directly to the tab
> with the information I need, rather than cycling through 4-5 different
> tabs to find the one I'm looking for.
Not a bad idea! Probably we should take this one up with the makeinfo
people.
Andy
next prev parent reply other threads:[~2017-01-09 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 18:43 bug#25293: More descriptive page titles in documentation? saffronsnail
2017-01-09 21:56 ` Andy Wingo [this message]
2017-03-01 14:49 ` Andy Wingo
[not found] ` <87mvd5f3wk.fsf@pobox.com>
2017-03-01 18:40 ` Gavin Smith
[not found] ` <CAKPWYQ1GcxJ2OvQuUEVjT9+X-Y+f00HXvvm22b=w4OBnwURwRA@mail.gmail.com>
2017-03-01 20:55 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1fvaoee.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25293@debbugs.gnu.org \
--cc=saffronsnail@hushmail.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).