unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Wdired doesn't like re-search-forward
Date: Sat, 19 Jun 2021 21:50:50 -0300	[thread overview]
Message-ID: <CADs++6gO2S2q1O7HnSySk1twePoKas9mo1KHk+rgyg9Y3pD4Aw@mail.gmail.com> (raw)
In-Reply-To: <87tultbhm8.fsf@web.de>

On Sat, 19 Jun 2021 at 19:43, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
>
> Eduardo Ochs <eduardoochs@gmail.com> writes:
>
> >   (No changes to be performed)
> >
> > Is this related to the recent (?) changes in wdired?
>
> Could be.
>
> > I noticed that now letters are bound to `wdired--self-insert' instead
> > of `self-insert-command' in wdired mode... is there something that I
> > need to do to make wdired recognize changes that were not done by
> > `wdired--self-insert'?
>
> No (this is implemented using `before-change-functions' and
> `after-change-functions' and should automatically recognize any kind of
> modifications).
>
> But here a quick test using a
>
>  (while (re-search-forward ...) replace-match ...)
>
> loop didn't reveal the problem for me.
>
> > And, more important of all: should I prepare a minimal way to
> > reproduce the problem and submit a proper bug report?
>
> If the problem is not caused by your setup (can you reproduce the
> problem in emacs -Q; do you use a recent build?) -- yes of course,
> please do that.
>
>
> Regards,
>
> Michael.

Hi Michael!
Done:
https://lists.gnu.org/archive/html/bug-gnu-emacs/2021-06/msg01037.html
  Cheers, E. =)



      reply	other threads:[~2021-06-20  0:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 13:47 Wdired doesn't like re-search-forward Eduardo Ochs
2021-06-19 17:41 ` arthur miller
2021-06-19 22:43 ` Michael Heerdegen
2021-06-20  0:50   ` Eduardo Ochs [this message]

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=CADs++6gO2S2q1O7HnSySk1twePoKas9mo1KHk+rgyg9Y3pD4Aw@mail.gmail.com \
    --to=eduardoochs@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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.
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).