GNU bug report logs - #62700
29.0.60; minibuffer-{previous,next,choose}-completion behave unintuitively when point is not at end of buffer

Previous Next

Full log

Message #121 received at 62700 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: sbaugh <at> janestreet.com
Cc: 62700 <at> debbugs.gnu.org, sbaugh <at> catern.com
Subject: Re: bug#62700: 29.0.60;
 minibuffer-{previous,next,choose}-completion behave unintuitively when
 point is not at end of buffer
Date: Sat, 10 Jun 2023 13:51:49 +0300

> Date: Mon, 08 May 2023 19:11:58 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 62700 <at> debbugs.gnu.org, sbaugh <at> catern.com, sbaugh <at> janestreet.com
> 
> > From: Juri Linkov <juri <at> linkov.net>
> > Cc: sbaugh <at> catern.com,  62700 <at> debbugs.gnu.org,  sbaugh <at> janestreet.com
> > Date: Mon, 08 May 2023 18:48:12 +0300
> > 
> > > Thanks, installed on the emacs-29 branch, and closing the bug.
> > 
> > Should the original patch be installed to master now?
> 
> It's up to you.

I don't know what you did after this message, but today I merged from
emacs-29 to master and got conflicts in minibuffer.el.  The conflicts
were strange: they seemed to be caused by gitmerge.el attempting to
merge backported changes?  That should not happen.

Would you please look at minibuffer.el on the master branch and see if
anything there needs fixing?

Thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.