From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 42993@debbugs.gnu.org
Subject: bug#42993: 26.3; [PATCH] Let Info bookmarks go to current, not recorded, version of manual
Date: Sun, 23 Aug 2020 09:32:09 -0700 (PDT) [thread overview]
Message-ID: <ac509cf4-a31e-4ca5-a05b-d4eb2ad7d638@default> (raw)
In-Reply-To: <<83mu2l98tg.fsf@gnu.org>>
> > An Info bookmark, like most bookmarks, records the target file as an
> > absolute file name. When you jump to an Info bookmark it jumps to the
> > recorded node in that Info file.
> >
> > But what if you have Info bookmarks that were recorded for older Emacs
> > versions? They typically have different absolute file names. When you
> > jump to such a bookmark it will go to the manual for that older Emacs
> > version, if you still have it installed (and the Info files are at the
> > same locations as recorded by the bookmark).
>
> The "official" way of installing Emacs will put the Info files into a
> single directory, so installing a newer version will overwrite the
> Info files with those of the newer version, leaving the absolute file
> name of the manual unchanged.
>
> So it sounds like you are suggesting a solution for a problem that
> happens only for users who for some reason install each Emacs version
> in a different place. How many such users are there?
You make a good point.
I don't know how many such users there are.
I do think Emacs should support such use cases.
I see no reason that it shouldn't. As I said, I
consider it a feature to be able to have Info
bookmarks to manuals for different Emacs versions.
Another consideration is using the same bookmarks
across different systems (e.g. MS Windows and
GNU/Linux), where the absolute locations, even
for "official installations" are likely to differ.
Requiring an Info bookmark to work only with its
absolute file name is, I think, unnecessarily
restrictive, even if it can also be useful (see
above: it's a feature).
But the point you make is certainly another
argument supporting user control of the behavior
(e.g. an option).
next parent reply other threads:[~2020-08-23 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<1e8dbcb9-e47f-48fd-a34a-f1cf304ba4cc@default>
[not found] ` <<83mu2l98tg.fsf@gnu.org>
2020-08-23 16:32 ` Drew Adams [this message]
2020-08-30 21:03 ` bug#42993: 26.3; [PATCH] Let Info bookmarks go to current, not recorded, version of manual Drew Adams
2021-05-13 9:55 ` Lars Ingebrigtsen
2020-08-23 6:07 Drew Adams
2020-08-23 6:26 ` Eli Zaretskii
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=ac509cf4-a31e-4ca5-a05b-d4eb2ad7d638@default \
--to=drew.adams@oracle.com \
--cc=42993@debbugs.gnu.org \
--cc=eliz@gnu.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).