[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems with query-replace, replace-string

From: Viktor Haag
Subject: Re: problems with query-replace, replace-string
Date: 16 Nov 2001 15:24:28 -0500
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1

address@hidden (Eli Zaretskii) writes:

> On Wed, 14 Nov 2001, Spencer Thiel wrote:
> > This sometimes replaced "Software Manager</h2>" with "Update
> > Assistanth2>", and "Software Manager</a>" with "Update
> > Assistanta>" clipping the </.  It seems that the replacement
> > is happening to characters that aren't included inside the
> > search string.  Above is just an example.  The bug isn't
> > specific to the search string above, or to the clipped
> > characters.  I've encountered the problem with a variety of
> > different search strings and replacement strings.  I've had
> > the problem on builds on both windows and linux, and while
> > using html-helper-mode, cperl-mode, and c++-mode.  The
> > behavior isn't consistent -- I can do the same search and
> > replace on multiple files and some will experience the bug
> > while others don't.
> To be able to debug this, we need a recipe to reproduce the
> problem.  Ideally, the recipe should start with "emacs -q
> --no-site-file", to avoid complications with user and site-wide
> customizations.

Eli, you can have at least independent confirmation. This is
*exactly* the same problem I reported a few months back, and you
gave exactly the same response (and appropriately so).

I was unable at the time to come up with a reliable way to
reproduce this problem.

> Could you please try to find such a recipe?  It would be a
> great help; without such a recipe, the only person who could
> debug this problem is you.

Errg. I hope this problem gets fixed as well.

My workaround was to rebind M-% to query-replace-regexp with
which I have not noticed the problem (yet).

Viktor Haag : Software & Information Design : Research In Motion
          "See? What? Walk in real quick was the plan?"

reply via email to

[Prev in Thread] Current Thread [Next in Thread]