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 19:10:00 +0300 [thread overview]
Message-ID: <83pnijtrmv.fsf@gnu.org> (raw)
In-Reply-To: <e1b17d46-c925-4e5f-ae90-d13c0dcd07df@default> (message from Drew Adams on Sat, 26 Oct 2019 08:55:11 -0700 (PDT))
> Date: Sat, 26 Oct 2019 08:55:11 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 37930@debbugs.gnu.org
>
> > > 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?"
>
> Fair enough. Read it that way then, if you
> want to quibble.
"Quibble", thanks a lot.
> To me, it doesn't belong - it shouldn't be
> present, because I don't see it as especially
> useful. But I'll be glad to learn how it is.
How else do you get to functions from that library in the manual?
> > Not obvious to you doesn't mean you should file a bug report, or that
> > we should continue discussing this.
>
> I should file a bug report when I think it can
> help improve Emacs. And that's what I do.
>
> Please don't tell others when or whether they
> _should_ file bug reports.
Your bug report was considered and rejected. Why do you continue
arguing instead of accepting the decision? This is a recurring
pattern with you, and one that makes it so unnecessarily hard handling
your bug reports. People avoid responding to your bug reports because
of that. I myself sometimes avoid them. This is unnecessary, and
actually harms Emacs.
Please consider not arguing about decisions to close your bug reports.
> You can close any report that you don't think is helpful.
I already did. But it doesn't seem to help, not with bugs filed by
you.
next prev parent reply other threads:[~2019-10-26 16:10 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>
[not found] ` <<80c877d4-178e-479b-bc12-048aefbb433f@default>
[not found] ` <<83sgnftuan.fsf@gnu.org>
2019-10-26 15:55 ` bug#37930: 26.3; Elisp manual: please remove index entry `seq library' Drew Adams
2019-10-26 16:10 ` Eli Zaretskii [this message]
[not found] <<5034f118-77b6-4f94-8d7b-2be7fd8f5195@default>
[not found] ` <<834kzwvutf.fsf@gnu.org>
2019-10-26 15:00 ` Drew Adams
2019-10-26 15:12 ` 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=83pnijtrmv.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).