From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: sctb@me.com, sdl.web@gmail.com, 74773-done@debbugs.gnu.org
Subject: bug#74773: [PATCH] Elaborate doc string for rcirc-next-active-buffer
Date: Thu, 12 Dec 2024 13:19:49 +0200 [thread overview]
Message-ID: <86o71hywq2.fsf@gnu.org> (raw)
In-Reply-To: <871pyexjsz.fsf@posteo.net> (message from Philip Kaludercic on Wed, 11 Dec 2024 16:31:56 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: Zaretskii Eli <eliz@gnu.org>, Bell Scott <sctb@me.com>,
> 74773@debbugs.gnu.org
> Date: Wed, 11 Dec 2024 16:31:56 +0000
>
> Leo Liu <sdl.web@gmail.com> writes:
>
> >> On 11 Dec 2024, at 20:21, Eli Zaretskii <eliz@gnu.org> wrote:
> >>
> >>
> >>>
> >>> 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?
> >
> > After checking all irc buffers with activity, the next rcirc-next-active-buffer returns you back to the buffer where your work is ie non irc buffers.
> >
> > So the patch doesn’t add much though harmless.
>
> 1+
Thanks, so I've now installed this on the emacs-30 branch, and I'm
closing this bug.
prev parent reply other threads:[~2024-12-12 11:19 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
2024-12-11 13:37 ` Leo Liu
2024-12-11 16:31 ` Philip Kaludercic
2024-12-12 11:19 ` Eli Zaretskii [this message]
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=86o71hywq2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74773-done@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).