emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#24580: closed (25.2.50; query-replace history does


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#24580: closed (25.2.50; query-replace history doesn't work)
Date: Wed, 05 Oct 2016 15:40:02 +0000

Your message dated Wed, 5 Oct 2016 11:39:09 -0400
with message-id <address@hidden>
and subject line Re: bug#24580: 25.2.50; query-replace history doesn't work
has caused the debbugs.gnu.org bug report #24580,
regarding 25.2.50; query-replace history doesn't work
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24580: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24580
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 25.2.50; query-replace history doesn't work Date: Sat, 01 Oct 2016 08:43:27 +0200 User-agent: mu4e 0.9.17; emacs 25.2.50.2
Hi all,

try this:

- start emacs -Q
- press `a' `C-b', `M-%', `a', `RET', `b', `RET', `!'
- press `M-%', `M-p'

Emacs says "Beginning of history; no preceding item".

Also, while I'm on my usual Emacs (with my customizations etc.), the
history seems to work, but apparently doesn't use
`query-replace-from-to-separator'.  I suspect these two bugs might be
related, but if needed, I may try to pinpoint the latter problem, too.

I'm on GNU Emacs 25.2.50.2 (commit 24388c8).

Best,

-- 
Marcin Borkowski



--- End Message ---
--- Begin Message --- Subject: Re: bug#24580: 25.2.50; query-replace history doesn't work Date: Wed, 5 Oct 2016 11:39:09 -0400 User-agent: Mutt/1.7+23 (87911ba95dae) (2016-08-17)
On 04/10/16 at 09:36am, Eli Zaretskii wrote:
> > Date: Mon, 3 Oct 2016 20:24:51 -0400
> > From: Mark Oteiza <address@hidden>
> > Cc: address@hidden, address@hidden
> > 
> > > Does a simple defvar you suggested before not work?
> > 
> > No, unless I erred somehow, which is likely, because what I tried first
> > (binding minibuffer-history) didn't appear to work either.  However, the
> > following does appear to solve the issue.
> 
> This looks much safer, so if you are okay with it, please push to
> master.

Done in 6d6c93f4


--- End Message ---

reply via email to

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