From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 37930@debbugs.gnu.org
Subject: bug#37930: 26.3; Elisp manual: please remove index entry `seq library'
Date: Sat, 26 Oct 2019 18:12:32 +0300 [thread overview]
Message-ID: <83sgnftuan.fsf@gnu.org> (raw)
In-Reply-To: <80c877d4-178e-479b-bc12-048aefbb433f@default> (message from Drew Adams on Sat, 26 Oct 2019 08:00:09 -0700 (PDT))
> Date: Sat, 26 Oct 2019 08:00:09 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 37930@debbugs.gnu.org
>
> > > commentary, in a Lisp library
> > > dynamic-library-alist
> > > find library
> > > image-load-path-for-library
> > > library
> > > library compilation
> > > library header comments
> > > library search
> > > Lisp library
> > > load-library
> > > locate-library
> > > seq library
> > >
> > > `seq library' does not belong here.
> >
> > Disagree. You are assessing index entries from
> > a completely wrong angle.
>
> What angle is that?
That of consistency. As expressed by "doesn't belong".
> You disagree that `seq library' doesn't belong.
> Fair enough. Why do you think it belongs?
That's a wrong question, when talking about index entries. the
important question is "is it useful?"
> Maybe there's a good reason for entry `seq
> library'. It's not obvious to me.
Not obvious to you doesn't mean you should file a bug report, or that
we should continue discussing this.
next prev parent reply other threads:[~2019-10-26 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<5034f118-77b6-4f94-8d7b-2be7fd8f5195@default>
[not found] ` <<834kzwvutf.fsf@gnu.org>
2019-10-26 15:00 ` bug#37930: 26.3; Elisp manual: please remove index entry `seq library' Drew Adams
2019-10-26 15:12 ` Eli Zaretskii [this message]
[not found] <<<5034f118-77b6-4f94-8d7b-2be7fd8f5195@default>
[not found] ` <<<834kzwvutf.fsf@gnu.org>
[not found] ` <<80c877d4-178e-479b-bc12-048aefbb433f@default>
[not found] ` <<83sgnftuan.fsf@gnu.org>
2019-10-26 15:55 ` Drew Adams
2019-10-26 16:10 ` Eli Zaretskii
2019-10-25 20:53 Drew Adams
2019-10-26 7:18 ` 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=83sgnftuan.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37930@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).