[debbugs-tracker] bug#27941: closed (25.2; next-line-add-newlines and minibuffer)

[GNU bug Tracking System]

Your message dated Sun, 03 Dec 2017 18:00:36 +0200
with message-id <address@hidden>
and subject line Re: bug#29529: next-line-add-newlines shouldn't be respected 
in next-line-or-history-element
has caused the debbugs.gnu.org bug report #29529,
regarding 25.2; next-line-add-newlines and minibuffer
to be marked as done.

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


-- 
29529: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=29529
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 25.2; next-line-add-newlines and minibuffer
>
>
>
>
> Date: 
>
> Fri, 04 Aug 2017 02:14:00 -0400
>
>
>
>
> If you
>
> (setq next-line-add-newlines t)
>
> then pressing <down> in the minibuffer always adds a newline,
> rather than moving to the next history item.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#29529: next-line-add-newlines shouldn't be respected in next-line-or-history-element
>
>
>
>
> Date: 
>
> Sun, 03 Dec 2017 18:00:36 +0200
>
>
>
>
> > Date: Fri, 1 Dec 2017 23:49:56 +0100 (CET)
> > From: "E. Choroba" <address@hidden>
> > 
> > I don't like the "end of buffer" errors, so I have switched 
> > next-line-add-newlines to t. In recent Emacs versions, though, this makes it 
> > impossible to browse the minibuffer history with cursor arrows: <down> adds a 
> > newline into the minibufer instead of showing the next history element. M-n 
> > works correctly, though.
> > 
> > Steps to reproduce (tested in 25.3.1):
> > 
> > emacs -Q
> > (setq next-line-add-newlines t) C-x C-e
> > C-x C-f <down>
> > 
> > Solution:
> > 
> > Set the variable to nil locally in next-line-or-history-element.
> > 
> > Patch:
>
> Thanks, I installed your patch.
>
>
> --- End Message ---