help-gnu-emacs
[Top][All Lists]
Advanced

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

Re: kmacro-end-and-call-macro repeats macro multiple times following ise


From: nomiskatz
Subject: Re: kmacro-end-and-call-macro repeats macro multiple times following isearch-forward
Date: Sun, 18 Aug 2013 02:13:20 -0700 (PDT)
User-agent: G2/1.0

Grrrr! And apologies.

I missed out a step -- calling isearch-forward from within the keyboard macro.  
It should be:

  - C-s   (isearch-forward)   to search for the repeated text
  - C-x (   (kmacro-start-macro)
  - Enter some new text
  - C-s C-s   to search again
  - C-x e  (kmacro-end-and-call-macro)




On Sunday, 18 August 2013 09:08:17 UTC+1, nomi...@gmail.com  wrote:
> I've just upgraded from Emacs 24.2.1 to Emacs 24.3.1.
> 
> 
> 
> Full version details:
> 
>   "GNU Emacs 24.2.1 (x86_64-apple-darwin, NS apple-appkit-1038.36)
> 
>    of 2012-08-27 on bob.porkrind.org"
> 
>   and
> 
>   "GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36)
> 
>    of 2013-03-13 on bob.porkrind.org"
> 
> 
> 
> If I have a buffer with some text that is repeated several times and do the 
> following...
> 
>   - C-s   (isearch-forward)   to search for the repeated text
> 
>   - C-x (   (kmacro-start-macro)
> 
>   - Enter some new text
> 
>   - C-x e  (kmacro-end-and-call-macro)
> 
> ... I get different behaviour in my old and new versions of Emacs.
> 
> 
> 
> In Emacs 24.2.1 and all previous versions I've used, 
> kmacro-end-and-call-macro calls the macro once more, and I can go through the 
> file making changes one at a time, and I can stop when I want.
> 
> 
> 
> In Emacs 24.3.1, kmacro-end-and-call-macro calls the macro repeatedly making 
> changes to all the repeated text up to the end of the file.
> 
> 
> 
> Interestingly, if I define a similar keyboard macro that uses next-error 
> rather than isearch-forward I get my changes one at a time.
> 
> 
> 
> Is this some bizarre new behaviour for isearch-forward? Can I get the old 
> behaviour back?
> 
> 
> 
> _
> 
> Simon


reply via email to

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