From: Stefan Kangas <stefan@marxist.se>
To: "Miguel V. S. Frasson" <mvsfrasson@gmail.com>
Cc: 34214@debbugs.gnu.org
Subject: bug#34214: 25.3; minibuffer function help in lisp modes changes match-data
Date: Thu, 13 Aug 2020 07:30:35 -0700 [thread overview]
Message-ID: <CADwFkmkLx4jmAGwGJFzrM3o29Daoi4QGynY2ky1=148oqS4wEA@mail.gmail.com> (raw)
In-Reply-To: <CAARdmY3isBNbnM=sbvATaMfT7WwA5eS3aaAcB5FNOzUwJ4v36A@mail.gmail.com>
[Please use "Reply to all" so that your replies get recorded in the bug
tracker.]
"Miguel V. S. Frasson" <mvsfrasson@gmail.com> writes:
> Hi.
>
> The "documented" behavior is in Elisp Reference, but not in doc-strings of
> functions that rely on match data. So they are not so easily spotted by
> non-experienced users.
>
> This bug teached me a lesson, but it took me a lot of time to realize how
> volatile match-data is, changed even by a helper mode like eldoc.
>
> IMO it is so easy to avoid interference into user experience in this case,
> adding convenience, just by saving match data inside eldoc...
>
> Should a helper mode "confuse" non-experienced users because it could rely
> on "documented" behavior? If so, why does Emacs have disabled commands, if
> they are also documented?
>
> Best regards
>
> Miguel
Actually, you may have a point regarding eldoc, if it's clobbering match
data just by moving around the buffer. I guess it would be nice to
avoid that.
Let's see if anyone else has something to say here.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-08-13 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 23:42 bug#34214: 25.3; minibuffer function help in lisp modes changes match-data Miguel V. S. Frasson
2019-01-27 13:58 ` Philipp Stephani
2020-08-13 11:37 ` Stefan Kangas
[not found] ` <CAARdmY3isBNbnM=sbvATaMfT7WwA5eS3aaAcB5FNOzUwJ4v36A@mail.gmail.com>
2020-08-13 14:30 ` Stefan Kangas [this message]
2020-08-13 17:14 ` Miguel V. S. Frasson
2020-09-18 9:51 ` Stefan Kangas
2021-09-22 22:10 ` Lars Ingebrigtsen
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='CADwFkmkLx4jmAGwGJFzrM3o29Daoi4QGynY2ky1=148oqS4wEA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=34214@debbugs.gnu.org \
--cc=mvsfrasson@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 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).