From: Eli Zaretskii <eliz@gnu.org>
To: Paul Nelson <ultrono@gmail.com>
Cc: 73284@debbugs.gnu.org
Subject: bug#73284: [PATCH] Add option to push mark after delete-pair
Date: Mon, 16 Sep 2024 14:44:10 +0300 [thread overview]
Message-ID: <86setzddrp.fsf@gnu.org> (raw)
In-Reply-To: <CAOA-32Pa7YEjqS+_UrkWrY+vUdZZY4jFOEEuiEu3QqGoxGaLqA@mail.gmail.com> (message from Paul Nelson on Sun, 15 Sep 2024 22:58:09 +0200)
> From: Paul Nelson <ultrono@gmail.com>
> Date: Sun, 15 Sep 2024 22:58:09 +0200
>
> The delete-pair command from lisp.el deletes a matched pair of
> delimiters. After using this command, I often want to operate on the
> region enclosed by the deleted delimiters. As far as I know, there's
> currently no quick way to access the end of that region.
>
> This patch introduces a custom option, delete-pair-push-mark. When
> enabled, it causes delete-pair to push a mark at the end of the
> enclosed region.
>
> This opens up various workflows. For instance, after deleting a pair,
> we can use C-x C-x to highlight the region and act on it further.
Shouldn't this activate the region, instead of forcing users to do
that manually? Users that have transient-mark-mode enabled (which is
ON by default), will expect that, I think.
> To err on the side of caution, I hid the new behavior behind a user
> option, disabled by default. I could just as well see it being turned
> on by default (or getting rid of the user option, making the new
> behavior "mandatory"), and am open to suggestions/feedback.
I don't think doing this by default is a good idea. Such significant
changes in behavior are better off starting disabled.
Let's see what others think about such optional behavior.
Thanks.
next prev parent reply other threads:[~2024-09-16 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-15 20:58 bug#73284: [PATCH] Add option to push mark after delete-pair Paul Nelson
2024-09-16 11:44 ` Eli Zaretskii [this message]
2024-09-16 14:07 ` Paul Nelson
2024-09-17 6:56 ` Juri Linkov
2024-09-17 9:20 ` Sean Whitton
2024-09-21 10:25 ` 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=86setzddrp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=73284@debbugs.gnu.org \
--cc=ultrono@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).