all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Christopher Howard <christopher@librehacker.com>,
	 Andrew Tropin <andrew@trop.in>,
	 Katherine Cox-Buday <cox.katherine.e+guix@gmail.com>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>,
	 Guix Devel <guix-devel@gnu.org>
Subject: Re: gnus debbugs searches?
Date: Mon, 16 Dec 2024 17:22:32 +0900	[thread overview]
Message-ID: <877c80ujef.fsf@gmail.com> (raw)
In-Reply-To: <87cyhs5126.fsf@gmx.de> (Michael Albinus's message of "Sun, 15 Dec 2024 18:05:37 +0100")

Hi Michael,

Michael Albinus <michael.albinus@gmx.de> writes:

[...]

> The recent version in GNU ELPA is debbugs 0.42.

I've now updated it in Guix, thanks (commit 2e8a8b3ddb).

>> It seems to work for me.  M-x debbugs-gnu-guix-search RET python-team,
>> then M-x debbugs-gnu-show-last-result (that seems to be a new thing -- I
>> guess I'll check the customizations to revert to show directly the
>> results):
>
> Since debbugs 0.41, bug reports are retrieved asynchronously.
> debbugs-gnu-show-last-result switches to the result buffer (you get a
> meesage, when bug retrieval has finished).
>
> If you don't like it, set debbugs-gnu-use-threads to nil.

I see!  Thanks for the heads-up.  I'll try it for a bit more time to see
if I get used to it, otherwise it's good to know there's a means to get
the old behavior back!

-- 
Thanks,
Maxim


      reply	other threads:[~2024-12-16  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 21:10 gnus debbugs searches? Christopher Howard
2024-12-15 11:47 ` Maxim Cournoyer
2024-12-15 17:05   ` Michael Albinus
2024-12-16  8:22     ` Maxim Cournoyer [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877c80ujef.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=andrew@trop.in \
    --cc=christopher@librehacker.com \
    --cc=cox.katherine.e+guix@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.