From: Drew Adams via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>,
"72282@debbugs.gnu.org" <72282@debbugs.gnu.org>
Subject: bug#72282: History entries shouldn't have the exact region hardwired in
Date: Thu, 25 Jul 2024 02:06:08 +0000 [thread overview]
Message-ID: <CO6PR10MB54737FD5C87F12AD2CCFAE7FF3AB2@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87o76m1ilb.1.fsf@jidanni.org>
> (repeat-complex-command)
> is great, except when used after
> (shell-command-on-region)
> in which case we will be repeating
> (shell-command-on-region 2234 2892 ...)
> instead of just
> (shell-command-on-region REGION-START REGION-END ...)
> in other words the previous exact region is hardwired into
> the history.
>
> Yes, you might say well then just do `M-| <up> RET`.
> Well that's harder to type than `<again>`, `<redo>`, `C-x M-:` or `C-x
> M-ESC`,
> which are the bindings of repeat-complex-command.
>
> So maybe for all history items, they shouldn't have the exact region
> hardwired in.
I brought this up when the change was made to do
what's done now. Originally Emacs put nil nil
in place of the specific region limits.
I don't recall whether a bug was filed for that
change or it was discussed in emacs-devel before
the change was made. In any case, the decision
was to go with the "enhancement" that we have
now: the specific region limits.
IOW, FWIW, I agree with you. I find myself
hand-replacing the numeric limits with nil's
fairly often.
I don't recall the reasons given for the change
to use the explicit numbers - if any reasons
were given.
next prev parent reply other threads:[~2024-07-25 2:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 23:22 bug#72282: History entries shouldn't have the exact region hardwired in Dan Jacobson
2024-07-25 2:06 ` Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-07-25 18:12 ` Juri Linkov
2024-08-19 6:49 ` Juri Linkov
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=CO6PR10MB54737FD5C87F12AD2CCFAE7FF3AB2@CO6PR10MB5473.namprd10.prod.outlook.com \
--to=bug-gnu-emacs@gnu.org \
--cc=72282@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=jidanni@jidanni.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.