From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@linkov.net>
Cc: Sam Steingold <sds@gnu.org>, 37998@debbugs.gnu.org
Subject: bug#37998: 27.0.50; gnus RFE: gnus-other-tab a la gnus-other-frame
Date: Fri, 22 Nov 2019 13:10:31 +0100 [thread overview]
Message-ID: <87lfs8t8lk.fsf@gnus.org> (raw)
In-Reply-To: <87o8x4hnu8.fsf@mail.linkov.net> (Juri Linkov's message of "Fri, 22 Nov 2019 00:22:07 +0200")
Juri Linkov <juri@linkov.net> writes:
> For example, I create a separate tab for each group and
> for the group buffer. Using display-buffer-alist the
> rules could look like
>
> ("\\`\\*Group\\*\\'" .
> (display-buffer-in-tab
> (name . "Gnus")))
>
> ("\\`\\*Summary \\(.*\\)\\*\\'"
> . (display-buffer-in-tab
> (name . "Group \\1")))
>
> So e.g. the command `M-x gnus RET' will create the tab with the name
> "Gnus" automatically, or switch to the existing tab with the name "Gnus".
> Opening a summary from the group buffer will either create a new tab
> with the name deduced from the summary buffer name, or switch
> to the existing tab by name.
Yes, that makes more sense than adding a new separate command, so I'm
closing this bug report. But perhaps an example like this should be
added to the manual?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-11-22 12:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 20:21 bug#37998: 27.0.50; gnus RFE: gnus-other-tab a la gnus-other-frame Sam Steingold
2019-10-30 20:58 ` Lars Ingebrigtsen
2019-10-30 21:11 ` Sam Steingold
2019-11-17 9:53 ` Lars Ingebrigtsen
2019-11-21 22:22 ` Juri Linkov
2019-11-22 12:10 ` Lars Ingebrigtsen [this message]
2019-11-22 18:50 ` Sam Steingold
2019-11-23 23:11 ` Juri Linkov
2019-11-26 22:55 ` Juri Linkov
2019-11-27 12:21 ` Lars Ingebrigtsen
2019-11-27 21:28 ` Juri Linkov
2019-11-30 21:37 ` Juri Linkov
2019-12-05 9:37 ` Lars Ingebrigtsen
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=87lfs8t8lk.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37998@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=sds@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).