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 19:27:08 +0300 [thread overview]
Message-ID: <83czr6we8z.fsf@gnu.org> (raw)
In-Reply-To: <DD7B43DA-7DA8-4DD4-A034-27FB195BAFF6@acm.org> (message from Mattias Engdegård on Sun, 25 Jul 2021 17:09:37 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 25 Jul 2021 17:09:37 +0200
> Cc: larsi@gnus.org, juri@linkov.net, 39121@debbugs.gnu.org,
> tino.calancha@gmail.com
>
> 25 juli 2021 kl. 13.49 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > That the occur-target text property's value can now be something new,
> > and that this new value form is actually the preferred one?
>
> Maybe, but we never said anything about occur-target to begin with.
The NEWS file doesn't necessarily describe only stuff documented
somewhere, it also describes changes that aren't documented anywhere
but the source code. Suppose someone read the source of replace.el,
found out about this property, and uses it to do something, either
privately or for some 3rd-part package. Put yourself in the shows of
that person and ask yourself whether you'd like to know that this kind
of change has been installed in Emacs.
> I'm not necessarily against it either. There may be a slight advantage for some code that can make good use of the new format. However, we can keep supporting existing code more or less indefinitely.
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.
next prev parent reply other threads:[~2021-07-25 16:27 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 [this message]
2021-07-25 18:54 ` Mattias Engdegård
2021-07-25 19:23 ` Eli Zaretskii
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=83czr6we8z.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.