From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 12187@debbugs.gnu.org, karl@freefriends.org
Subject: bug#12187: 24.1.50; Regression: `Info-breadcrumbs-depth' should show `File:' without ".info" suffix
Date: Mon, 13 Aug 2012 18:44:20 +0300 [thread overview]
Message-ID: <838vdi7q5n.fsf@gnu.org> (raw)
In-Reply-To: <837A4A5337854402803C885693F4CD76@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: "'KarlBerry'" <karl@freefriends.org>, <12187@debbugs.gnu.org>
> Date: Mon, 13 Aug 2012 06:55:25 -0700
>
> Eli, can you speak more of the advantage of showing the suffix? E.g., are there
> cases where there might be more than one manual with the same file name except
> for the suffix?
Yes, there could be more than one manual with the same name, however
unlikely. Not sure how important that is, though.
> And could you elaborate on how this relates to other Info readers
> and why it can be important to show the suffix?
What you see is simply the header line of every node, verbatim, as
makeinfo generates it. If you visit the Info file literally, that is
what you will see there at the beginning of each node. I don't think
there's some deep philosophy here, just tradition and KISS, really.
next prev parent reply other threads:[~2012-08-13 15:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 21:00 bug#12187: 24.1.50; Regression: `Info-breadcrumbs-depth' should show `File:' without ".info" suffix Drew Adams
2012-08-13 2:39 ` Eli Zaretskii
2012-08-13 13:45 ` Stefan Monnier
2012-08-13 13:55 ` Drew Adams
2012-08-13 15:44 ` Eli Zaretskii [this message]
2012-08-13 16:10 ` Drew Adams
2012-08-21 22:28 ` bug#12187: 24.1.50; " Juri Linkov
2012-08-22 23:33 ` Juri Linkov
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838vdi7q5n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12187@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=karl@freefriends.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).