From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: larsi@gnus.org, juri@linkov.net, 39121@debbugs.gnu.org,
tino.calancha@gmail.com
Subject: bug#39121: 27.0.60; occur: Add bindings for next-error-no-select
Date: Sun, 25 Jul 2021 22:23:26 +0300 [thread overview]
Message-ID: <834kciw635.fsf@gnu.org> (raw)
In-Reply-To: <408C22B8-4A9D-409F-8610-1AE86294FC20@acm.org> (message from Mattias Engdegård on Sun, 25 Jul 2021 20:54:47 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 25 Jul 2021 20:54:47 +0200
> Cc: larsi@gnus.org, juri@linkov.net, 39121@debbugs.gnu.org,
> tino.calancha@gmail.com
>
> 25 juli 2021 kl. 18.27 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > The NEWS file doesn't necessarily describe only stuff documented
> > somewhere, it also describes changes that aren't documented anywhere
> > but the source code.
>
> Yes, but then it's always something that affects the user in some way, isn't it?
"User" in this case includes Lisp programmers; there's the "Lisp
changes" section in NEWS for that reason.
> Mentioning changed internals doesn't seem to be standard practice, but I could be wrong about that.
Text properties are not internals, they are visible to any Lisp
program and to the user.
> Would you point out a few examples of where we described changed aspects of undocumented implementation details in NEWS? That would support your view and help me understand it better.
Sorry, no, I won't. I think this aspect of the change should be in
NEWS, and I'm asking you to document it there. I don't understand why
I'm required to go to such lengths to justify a simple request. If
you are still not convinced, I will do it myself, because this endless
dispute about a couple of sentences in NEWS is more than I can afford.
> The question is also whether it should be documented at all.
I think it should, and have said so.
> > Since you introduced the new format, you probably thought it to be
> > better than the existing one, right? Then telling others about that
> > would be a good service, IMO.
>
> The change was made exclusively for improving Occur itself, and the external packages that I have seen would generally draw little advantage from doing anything differently. Of course, I haven't seen them all, but having other people depending on implementation details of your software is a maintenance burden which either impedes progress.
Please leave the final judgment about that to me. I understand your
point and your doubts, but I still think we should document this
aspect of the change in NEWS. I hope this is enough to convince you.
TIA
next prev parent reply other threads:[~2021-07-25 19:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CD8A4158-1AD5-4997-8F36-8F8E7DF9BD32@acm.org>
2021-07-15 22:10 ` bug#39121: 27.0.60; occur: Add bindings for next-error-no-select Juri Linkov
2021-07-16 13:20 ` Mattias Engdegård
2021-07-23 13:32 ` Mattias Engdegård
2021-07-23 14:05 ` Lars Ingebrigtsen
2021-07-23 17:16 ` Mattias Engdegård
2021-07-24 11:46 ` Lars Ingebrigtsen
2021-07-24 17:29 ` Mattias Engdegård
2021-07-25 6:41 ` Lars Ingebrigtsen
2021-07-25 9:16 ` Eli Zaretskii
2021-07-25 10:55 ` Mattias Engdegård
2021-07-25 11:39 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-07-25 14:45 ` Mattias Engdegård
2021-07-25 11:49 ` Eli Zaretskii
2021-07-25 15:09 ` Mattias Engdegård
2021-07-25 16:27 ` Eli Zaretskii
2021-07-25 18:54 ` Mattias Engdegård
2021-07-25 19:23 ` Eli Zaretskii [this message]
2021-07-25 19:30 ` Mattias Engdegård
2021-07-26 12:43 ` Eli Zaretskii
2021-07-25 10:06 ` Mattias Engdegård
2020-01-13 20:51 Tino Calancha
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=834kciw635.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39121@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=tino.calancha@gmail.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 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.