From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Eli Zaretskii'" <eliz@gnu.org>
Cc: 12187@debbugs.gnu.org, 'KarlBerry' <karl@freefriends.org>
Subject: bug#12187: 24.1.50; Regression: `Info-breadcrumbs-depth' should show `File:' without ".info" suffix
Date: Mon, 13 Aug 2012 06:55:25 -0700 [thread overview]
Message-ID: <837A4A5337854402803C885693F4CD76@us.oracle.com> (raw)
In-Reply-To: <jwvr4ra29i4.fsf-monnier+emacs@gnu.org>
> >> We should not be displaying the suffix ".info". The
> >> "file" name here is intended to indicate which manual you are in.
>
> > No, it's a file name. That's how all Info readers work.
> > This is not a bug.
>
> I agree it's not a bug, and not a regression in the Info
> reader either, but IIUC having just "elisp" in there would work
> as well (because when searching for "elisp" the Info reader also
> tries to look for "elisp.info"), so I think it's a reasonable
> request to elide the ".info". But I'm not sure if eliding should
> be the job of makeinfo or of the Info renderer.
I can see both your points of view.
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? And could you elaborate on how this relates to other Info
readers and why it can be important to show the suffix?
I was thinking of the suffix here as essentially noise. But if there is a real
use for it then I would agree that it need not be removed.
next prev parent reply other threads:[~2012-08-13 13:55 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 [this message]
2012-08-13 15:44 ` Eli Zaretskii
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=837A4A5337854402803C885693F4CD76@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12187@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=karl@freefriends.org \
--cc=monnier@iro.umontreal.ca \
/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).