unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Allen Li <darkfeline@felesatra.moe>
To: 45607@debbugs.gnu.org
Subject: bug#45607: 27.1; compiled replace-string breaks repeat-complex-command
Date: Sat, 02 Jan 2021 01:04:30 -0800	[thread overview]
Message-ID: <80o8i7676p.fsf@felesatra.moe> (raw)

Interactive commands that act on the region are handled specially such
that when repeated with `repeat-complex-command`, the repeated command
uses the current region rather than the region used for the previous
invocation of the command.

`replace-string` does not respect this; it uses the previous region when
repeated with `repeat-complex-command`.

Note that loading `replace-string` from source (rather than byte
compiled) fixes this problem.  So it's probably a problem with byte
compiled commands.

I swear I filed a bug for this a long time ago, and I can't remember if
it's a regression or it hasn't landed in a release yet.  I can't find
the original bug.

In GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.22, cairo version 1.17.3)
 of 2020-08-28 built on juergen
Windowing system distributor 'The X.Org Foundation', version 11.0.12010000
System Description: Arch Linux

Configured features:
XPM JPEG TIFF GIF PNG RSVG CAIRO SOUND GPM DBUS GSETTINGS GLIB NOTIFY
INOTIFY ACL GNUTLS LIBXML2 FREETYPE HARFBUZZ M17N_FLT LIBOTF ZLIB
TOOLKIT_SCROLL_BARS GTK3 X11 XDBE XIM MODULES THREADS LIBSYSTEMD JSON
PDUMPER LCMS2 GMP

Important settings:
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix





             reply	other threads:[~2021-01-02  9:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-02  9:04 Allen Li [this message]
2022-06-07 12:38 ` bug#45607: 27.1; compiled replace-string breaks repeat-complex-command Lars Ingebrigtsen
2022-06-07 18:40   ` Juri Linkov
2022-06-07 18:58     ` Eli Zaretskii
2022-06-09  8:39       ` Allen Li
2022-06-09  9:23         ` Eli Zaretskii
2022-06-08 12:05     ` Lars Ingebrigtsen
2022-06-09 18:52       ` Lars Ingebrigtsen
2022-06-09 18:56         ` Lars Ingebrigtsen
2022-06-09 20:51           ` Drew Adams
2022-07-05 14:41           ` Michael Heerdegen
2022-07-05 16:45             ` Lars Ingebrigtsen
2022-07-05 18:47               ` Michael Heerdegen
2022-07-06  7:53             ` Juri Linkov
2022-07-06 11:35               ` Lars Ingebrigtsen
2022-07-06 18:39                 ` Juri Linkov
2022-07-07  8:02                   ` Lars Ingebrigtsen
2022-08-08 13:53                     ` Lars Ingebrigtsen
2022-08-08 17:07                       ` Juri Linkov
2022-08-09 15:00                         ` Lars Ingebrigtsen
2022-08-09 18:41                           ` Juri Linkov
2022-08-09 18:48                             ` Eli Zaretskii
2022-08-09 19:15                               ` Lars Ingebrigtsen
2022-08-09 19:25                                 ` Eli Zaretskii
2022-08-09 19:30                                   ` Lars Ingebrigtsen
2022-08-09 19:14                             ` Lars Ingebrigtsen
2022-08-09 19:30                               ` Juri Linkov
2022-08-12 13:01                                 ` Lars Ingebrigtsen
2022-08-12 17:39                                   ` Juri Linkov
2022-08-13 11:46                                     ` Lars Ingebrigtsen
2022-08-13 19:30                                       ` Juri Linkov
2022-08-15  6:37                                         ` Lars Ingebrigtsen
2022-09-04 16:57                                 ` 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

  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=80o8i7676p.fsf@felesatra.moe \
    --to=darkfeline@felesatra.moe \
    --cc=45607@debbugs.gnu.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 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).