From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "53261@debbugs.gnu.org" <53261@debbugs.gnu.org>
Subject: bug#53261: [External] : Re: bug#53261: 26.3; Doc of `load-history' should say what the alist order is.
Date: Sat, 15 Jan 2022 21:35:01 +0000 [thread overview]
Message-ID: <SJ0PR10MB54882647F4A61CE8D9ACB048F3559@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <878rvhmm8z.fsf@gnus.org>
> > The doc of `load-history' describes the alist entries in detail. But it
> > should also say that the list entries are in reverse chronological order
> > of loading, i.e., earliest loaded libraries at the end, most recently
> > loaded entries at the beginning.
>
> I'm not sure whether that's something that we guarantee, or want to
> guarantee? Anybody have any opinions here?
1. I believe it's been in that order since Day One.
2. How could it be otherwise? (Dunno.)
3. Users should have some understanding of the order,
to make sense of `load-history'. Examining this
history is one way of figuring out something that
didn't go as expected (e.g. the wrong definition
of something shadowing another).
It's called `load-history'. Users will expect it
to be similar to other `*-history' lists, unless
its doc says something different. But it helps
to directly say what its order is.
It's true that the doc strings of the individual
_minibuffer_ history vars don't say that they are
"most recent first". But at least the Elisp
manual (node `Minibuffer History') says it's true
of all minibuffer history vars.
The Emacs manual (node `Shell Ring') says that
shell histories are like minibuffer histories.
And node `Repetition' says that command history
is also "most recent first".
next prev parent reply other threads:[~2022-01-15 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 17:00 bug#53261: 26.3; Doc of `load-history' should say what the alist order is Drew Adams
2022-01-15 8:33 ` Lars Ingebrigtsen
2022-01-15 21:35 ` Drew Adams [this message]
2022-02-13 10:11 ` Lars Ingebrigtsen
2022-02-13 16:51 ` bug#53261: [External] : " Drew Adams
2022-02-15 4:27 ` Richard Stallman
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=SJ0PR10MB54882647F4A61CE8D9ACB048F3559@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=53261@debbugs.gnu.org \
--cc=larsi@gnus.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).