GNU bug report logs -
#38384
(next|previous)-buffer silent about not switching
Previous Next
Reported by: Juanma Barranquero <lekktu <at> gmail.com>
Date: Tue, 26 Nov 2019 12:09:02 UTC
Severity: minor
Tags: patch
Done: Juanma Barranquero <lekktu <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Tue, 26 Nov 2019 16:54:56 +0100
> Cc: 38384 <at> debbugs.gnu.org
>
> > Could that disrupt noninteractive calls?
>
> Yes, that's why added the notice in NEWS in the "Incompatible Lisp Changes".
Then how about signaling user-error only in interactive calls?
> But, on one hand, programs should perhaps be using switch-to-(prev|next)-buffer. AFAICS, next-buffer and
> previous-buffer aren't even documented in the Elisp manual (they are briefly mentioned in the Emacs
> manual).
>
> And on the other, if code is using (next|prev)-buffer, silently getting the same buffer is likely a subtle bug
> anyway. At least now they get notice.
IMO, if we can improve the diagnostics only in interactive
invocations, we have all the advantages without any disadvantages (and
can move this out of the "incompatible changes" section).
This bug report was last modified 5 years and 181 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.