all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 29598@debbugs.gnu.org
Subject: bug#29598: 26.0; doc of `load-history'
Date: Sat, 9 Dec 2017 08:27:54 -0800 (PST)	[thread overview]
Message-ID: <664c0075-fab4-4127-800e-eaaeec42002f@default> (raw)
In-Reply-To: <<837etwuqgx.fsf@gnu.org>>

> > Shouldn't the doc say something about the order of the elements of the
> > alist?  It's a history, but neither the Elisp manual nor the doc string
> > mentions whether the beginning or the end of the list is the oldest
> > part of the history of loads.
> 
> Since it's an alist, and every element should be there only once, why
> does the order matter?

Because it's a history?  We already tell users, by using
that name, that it is chronological.  What we don't tell
them is which chronological order is used.

If someone is looking for something, it helps to know whether
the list order is old-to-new or new-to-old.  And if someone
locates something of interest in the list it helps to know
whether it is the stuff that comes before or after it that
was loaded when it got loaded.

Is there some reason not to mention the order?  We do, after
all, bother to call it `*-history'.





       reply	other threads:[~2017-12-09 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<abd8ea3d-1224-4364-b9e2-73b8c63b90bc@default>
     [not found] ` <<837etwuqgx.fsf@gnu.org>
2017-12-09 16:27   ` Drew Adams [this message]
     [not found]     ` <CADwFkmn0A3EMx_yX9emy8Wvcw5R7Byk7eFUNPYYT1-kxP1_ykA@mail.gmail.com>
2020-08-19 12:53       ` bug#29598: 26.0; doc of `load-history' Drew Adams
2020-10-27  2:31     ` Stefan Kangas
2020-10-27  8:53       ` bug#29598: (no subject) Lars Ingebrigtsen
2017-12-07  5:55 bug#29598: 26.0; doc of `load-history' Drew Adams
2017-12-09 10:48 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=664c0075-fab4-4127-800e-eaaeec42002f@default \
    --to=drew.adams@oracle.com \
    --cc=29598@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.