unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 31492@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#31492: 26.1; query-replace-regexp undo fails in regexps w/o printable chars
Date: Sun, 20 May 2018 18:47:10 +0300	[thread overview]
Message-ID: <83po1qfhxd.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1805202202180.24622@calancha-pc> (message from Tino Calancha on Sun, 20 May 2018 22:46:05 +0900 (JST))

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sun, 20 May 2018 22:46:05 +0900 (JST)
> cc: Tino Calancha <tino.calancha@gmail.com>, 31492@debbugs.gnu.org
> 
> > The question is: is such a situation possible?
> Everything is possible (except, possibly, that I find a new job).

Actually, I know a few things that are even less possible than that.

> You know what they say: In the risk is the pleasure. Otherwise we
> can use the first patch; the one with the test:
> (/= (match-beginning 0) (match-end 0))

No, I like the 2nd one better.

Thanks.





  reply	other threads:[~2018-05-20 15:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 13:27 bug#31492: 26.1; query-replace-regexp undo fails in regexps w/o printable chars Tino Calancha
2018-05-18 14:16 ` Eli Zaretskii
2018-05-18 14:22   ` Tino Calancha
2018-05-18 15:07     ` Eli Zaretskii
2018-05-19  1:46       ` Tino Calancha
2018-05-19  7:50         ` Eli Zaretskii
2018-05-19 14:28           ` Tino Calancha
2018-05-20  9:29             ` Eli Zaretskii
2018-05-20 11:51               ` Tino Calancha
2018-05-20 11:59                 ` Eli Zaretskii
2018-05-20 12:06                   ` Tino Calancha
2018-05-20 12:48                     ` Eli Zaretskii
2018-05-20 13:46                       ` Tino Calancha
2018-05-20 15:47                         ` Eli Zaretskii [this message]
2018-05-21  1:51                           ` Tino Calancha
2018-05-21 15:05                             ` Eli Zaretskii
2018-05-23  9:22                               ` Tino Calancha

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=83po1qfhxd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31492@debbugs.gnu.org \
    --cc=tino.calancha@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).