unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 45330@debbugs.gnu.org
Subject: bug#45330: 28.0.50; debbugs-gnu: Can't select reports before having started Gnus
Date: Mon, 06 Dec 2021 02:14:22 +0100	[thread overview]
Message-ID: <87a6hesff5.fsf@web.de> (raw)
In-Reply-To: <87mtlelmpz.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 05 Dec 2021 14:18:32 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> I can switch the test to be something more explicit, but how about --
> bear with me here -- making `gnus-summary-line-format' a group
> parameter? It's something I've been thinking about for a while. It would
> be really nice to be able to give different groups different summary
> appearances. And it would allow Michael and everyone else to use a
> separate format string for groups like debbugs or whatnot, that are
> often opened without Gnus actually being running.
>
> WDYT?

I have no strong opinion, but - why not, could be useful.  I don't think
this will spare a fix for this issue though.  Because, AFAIR this
registry -> nil thing has several reincarnations in debbugs.

Michael.





  reply	other threads:[~2021-12-06  1:14 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20  4:53 bug#45330: 28.0.50; debbugs-gnu: Can't select reports before having started Gnus Michael Heerdegen
2020-12-21  4:56 ` Lars Ingebrigtsen
2020-12-21  7:10   ` Michael Heerdegen
2020-12-21 16:12     ` Eric Abrahamsen
2020-12-22 16:43       ` Eric Abrahamsen
2020-12-23  5:23         ` Michael Heerdegen
2020-12-23 18:08           ` Eric Abrahamsen
2021-12-04 23:18             ` Lars Ingebrigtsen
2021-12-05  0:23               ` Michael Heerdegen
2021-12-05 19:48                 ` Lars Ingebrigtsen
2021-12-05 22:18                   ` Eric Abrahamsen
2021-12-06  1:14                     ` Michael Heerdegen [this message]
2021-12-06  1:29                       ` Eric Abrahamsen
2021-12-06  5:46                     ` Lars Ingebrigtsen
2021-12-06 18:06                       ` Eric Abrahamsen
2021-12-06 21:29                         ` Michael Heerdegen
2021-12-06 21:45                           ` Eric Abrahamsen
2021-12-06 23:01                             ` Michael Heerdegen
2021-12-12  2:46                     ` Michael Heerdegen
2021-12-23 22:42                       ` Eric Abrahamsen
2021-12-31 18:55                         ` Michael Heerdegen
2021-12-31 20:43                           ` Eric Abrahamsen
2022-01-12 23:06                           ` Eric Abrahamsen
2022-01-12 23:07                           ` Eric Abrahamsen
2022-01-13 12:43                             ` Michael Heerdegen
2022-01-13 19:42                               ` Eric Abrahamsen
2022-01-13 21:54                                 ` Michael Heerdegen

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=87a6hesff5.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=45330@debbugs.gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=larsi@gnus.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).