From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 43489@debbugs.gnu.org
Subject: bug#43489: [PATCH] Don't signal scan-error when moving by sexp interactively
Date: Fri, 18 Sep 2020 17:23:10 +0200 [thread overview]
Message-ID: <87imcbds81.fsf@gnus.org> (raw)
In-Reply-To: <D52B3A19-259E-4F5F-B35B-0C71E25776DD@acm.org> ("Mattias Engdegård"'s message of "Fri, 18 Sep 2020 17:13:18 +0200")
Mattias Engdegård <mattiase@acm.org> writes:
> In fact, several of the commands in question don't even beep at the
> boundaries in some cases: for example, C-M-f after the last sexp of
> the buffer jumps to end-of-buffer and silently stays there. Should we
> add noise messages for such cases? Surely not.
Yeah, that is pretty inconsistent.
> In other words: I'm not strongly against messages instead of dings if
> that is the condition for applying the patch, but would like to hear
> the benefit of those messages argued positively.
Emacs does signal errors a lot more in editing than other editors, it's
true -- for instance, `left' at the beginning of the buffer.
> There, I'm better now. And here's a hot cuppa, lovely.
:-)
>> I wonder whether this would have any negative effect when people are
>> using these commands in keyboard macros. For instance, if you've
>> recorded a macro that does `M-C-f M-DEL' or something, previously it
>> would signal an error and then stop, while now it'll just continue and
>> delete the wrong thing?
>
> Actually, (ding) interrupts keyboard macros, so this does work.
Ah, I'd forgotten that.
Still, I'm not sure whether a (ding) is more helpful than a non-cryptic
user-error message in these instances.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-18 15:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 11:31 bug#43489: [PATCH] Don't signal scan-error when moving by sexp interactively Mattias Engdegård
2020-09-18 13:13 ` Lars Ingebrigtsen
2020-09-18 13:18 ` Dmitry Gutov
2020-09-18 13:42 ` Lars Ingebrigtsen
2020-09-18 13:48 ` Dmitry Gutov
2020-09-18 15:13 ` Mattias Engdegård
2020-09-18 15:23 ` Lars Ingebrigtsen [this message]
2020-09-18 16:01 ` Mattias Engdegård
2020-09-19 14:13 ` Lars Ingebrigtsen
2020-09-20 17:33 ` Mattias Engdegård
2020-09-20 19:54 ` Lars Ingebrigtsen
2020-09-21 10:55 ` Mattias Engdegård
2020-09-21 14:47 ` Lars Ingebrigtsen
2020-09-21 17:12 ` Mattias Engdegård
2020-09-22 14:32 ` Lars Ingebrigtsen
2020-09-23 9:17 ` Mattias Engdegård
2020-09-23 13:40 ` Lars Ingebrigtsen
2020-09-23 14:33 ` Mattias Engdegård
2020-09-23 14:45 ` João Távora
2020-09-23 16:24 ` Mattias Engdegård
2020-09-23 16:37 ` João Távora
2020-09-24 15:50 ` Mattias Engdegård
2020-09-24 15:58 ` João Távora
2020-09-24 17:32 ` Stefan Monnier
2020-09-24 19:23 ` João Távora
2020-09-28 17:05 ` Stefan Monnier
2020-09-20 21:39 ` Dmitry Gutov
2020-09-21 11:21 ` Mattias Engdegård
2020-09-21 12:36 ` Dmitry Gutov
2020-09-21 17:12 ` Mattias Engdegård
2020-09-21 17:49 ` Dmitry Gutov
2020-09-21 8:49 ` João Távora
2020-09-21 14:43 ` Lars Ingebrigtsen
2020-09-21 17:12 ` Mattias Engdegård
2020-09-21 17:25 ` João Távora
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=87imcbds81.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43489@debbugs.gnu.org \
--cc=mattiase@acm.org \
/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.