From: Eli Zaretskii <eliz@gnu.org>
To: Scott Bell <sctb@me.com>, Leo Liu <sdl.web@gmail.com>,
Philip Kaludercic <philipk@posteo.net>
Cc: 74773@debbugs.gnu.org
Subject: bug#74773: [PATCH] Elaborate doc string for rcirc-next-active-buffer
Date: Wed, 11 Dec 2024 14:21:10 +0200 [thread overview]
Message-ID: <86msh24dhl.fsf@gnu.org> (raw)
In-Reply-To: <m25xnrz6or.fsf@me.com> (bug-gnu-emacs@gnu.org)
> Date: Tue, 10 Dec 2024 12:20:04 -0700
> From: Scott Bell via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> I found the current behavior of rcirc-next-active-buffer surprising in
> the case where there is no activity, so I thought it could be described
> in the doc string.
Leo and Philip, is this okay to install?
> >From b5a3f93c006316d53139bbd308afbf4c70c89289 Mon Sep 17 00:00:00 2001
> From: Scott Bell <sctb@me.com>
> Date: Tue, 10 Dec 2024 12:02:54 -0700
> Subject: [PATCH] ; * lisp/net/rcirc.el (rcirc-next-active-buffer): Doc string
>
> ---
> lisp/net/rcirc.el | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lisp/net/rcirc.el b/lisp/net/rcirc.el
> index c41e2ec153f..33e4008fc0b 100644
> --- a/lisp/net/rcirc.el
> +++ b/lisp/net/rcirc.el
> @@ -2448,7 +2448,8 @@ rcirc-bury-buffers
>
> (defun rcirc-next-active-buffer (arg)
> "Switch to the next rcirc buffer with activity.
> -With prefix ARG, go to the next low priority buffer with activity."
> +With prefix ARG, go to the next low priority buffer with activity.
> +When there are no buffers with activity, bury all rcirc buffers."
> (interactive "P")
> (let* ((pair (rcirc-split-activity rcirc-activity))
> (lopri (car pair))
> --
> 2.39.5 (Apple Git-154)
>
next prev parent reply other threads:[~2024-12-11 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:20 bug#74773: [PATCH] Elaborate doc string for rcirc-next-active-buffer Scott Bell via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-11 12:21 ` Eli Zaretskii [this message]
2024-12-11 13:37 ` Leo Liu
2024-12-11 16:31 ` Philip Kaludercic
2024-12-12 11:19 ` 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=86msh24dhl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74773@debbugs.gnu.org \
--cc=philipk@posteo.net \
--cc=sctb@me.com \
--cc=sdl.web@gmail.com \
/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).