From: Juanma Barranquero <lekktu@gmail.com>
To: 38384@debbugs.gnu.org
Subject: bug#38384: (next|previous)-buffer silent about not switching
Date: Tue, 26 Nov 2019 13:08:12 +0100 [thread overview]
Message-ID: <CAAeL0SSD8RAX7gAjHK5odY7RusGzD0ZtTAHdLgBEyd4Jf6xRsA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 385 bytes --]
Package: emacs
Severity: minor
Tags: patch
X-Debbugs-Cc: rudalics@gmx.at
In some circumstances, next-buffer and previous-buffer do not have any
buffer to switch to, and in that case they silently do nothing. (Strictly
speaking, they call switch-to-(next|prev)-buffer, which do nothing and
return nil).
I think they should throw a user-error, to inform the user about the
situation.
[-- Attachment #1.2: Type: text/html, Size: 536 bytes --]
[-- Attachment #2: window.patch --]
[-- Type: application/octet-stream, Size: 841 bytes --]
diff --git i/lisp/window.el w/lisp/window.el
index 49fad75d3c..c8a5816b8c 100644
--- i/lisp/window.el
+++ w/lisp/window.el
@@ -4850,7 +4850,8 @@ next-buffer
(user-error "Window is strongly dedicated to its buffer"))
(t
(dotimes (_ (or arg 1))
- (switch-to-next-buffer)))))
+ (unless (switch-to-next-buffer)
+ (user-error "No next buffer"))))))
(defun previous-buffer (&optional arg)
"In selected window switch to ARGth previous buffer.
@@ -4864,7 +4865,8 @@ previous-buffer
(user-error "Window is strongly dedicated to its buffer"))
(t
(dotimes (_ (or arg 1))
- (switch-to-prev-buffer)))))
+ (unless (switch-to-prev-buffer)
+ (user-error "No previous buffer"))))))
(defun delete-windows-on (&optional buffer-or-name frame)
"Delete all windows showing BUFFER-OR-NAME.
next reply other threads:[~2019-11-26 12:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:08 Juanma Barranquero [this message]
2019-11-26 13:42 ` bug#38384: (next|previous)-buffer silent about not switching martin rudalics
2019-11-26 14:05 ` Juanma Barranquero
2019-11-26 15:42 ` Eli Zaretskii
2019-11-26 15:54 ` Juanma Barranquero
2019-11-26 16:00 ` Juanma Barranquero
2019-11-26 17:00 ` martin rudalics
2019-11-26 18:04 ` Eli Zaretskii
2019-11-26 18:23 ` Juanma Barranquero
2019-11-26 18:44 ` Eli Zaretskii
2019-11-26 18:51 ` Juanma Barranquero
2019-11-26 19:37 ` Eli Zaretskii
2019-11-26 19:56 ` Juanma Barranquero
2019-11-26 20:07 ` Eli Zaretskii
2019-11-26 17:00 ` martin rudalics
2019-11-26 18:03 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAeL0SSD8RAX7gAjHK5odY7RusGzD0ZtTAHdLgBEyd4Jf6xRsA@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=38384@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).