unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: A few questions about debbugs
Date: Fri, 23 Aug 2024 10:00:53 +0200	[thread overview]
Message-ID: <87ttfc3h7d.fsf@gmx.de> (raw)
In-Reply-To: <jwv7ccaggjl.fsf-monnier+emacs@gnu.org> (Stefan Monnier via Users list for the's message of "Wed, 21 Aug 2024 09:24:40 -0400")

Stefan Monnier via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

Hi Stefan,

>> Replacing soap-invoke by soap-invoke-async is not a problem. What I
>> worry about is the UI. If you invoke debbugs-search, and you do
>> something else in Emacs then, you need a proper way how to present the
>> search results to the user w/o interrupting the work she is doing
>> meanwhile.
>
> Indeed displaying the buffer asynchronously is too disruptive.
>
> The usual way to do that in Emacs is to immediately display the (empty)
> result buffer and then maybe emit a `message` when this buffer has
> been filled.

Thanks for the explanation. I'll give it a try for debbugs-{gnu,org}-search.

> Maybe to complement Michael's answer: `debbugs.gnu.org` was originally
> setup for Emacs's bug tracking needs.  Since then, other GNU packages
> have decided to use that server as well, but Emacs is still probably the
> main user.

Yes, but not such dominant as expected:

--8<---------------cut here---------------start------------->8---
(length (debbugs-get-bugs :package "emacs" :archive "both"))
=> 34657

(length (debbugs-get-bugs :package "guix" :package "guix-patches" :archive "both"))
=> 27259
--8<---------------cut here---------------end--------------->8---

>         Stefan

Best regards, Michael.



  reply	other threads:[~2024-08-23  8:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 22:26 A few questions about debbugs Björn Bidar
2024-08-13  7:27 ` Michael Albinus
2024-08-19  9:26   ` Björn Bidar
     [not found]   ` <871q2krhgh.fsf@>
2024-08-19 11:03     ` Michael Albinus
2024-08-20 10:38       ` Björn Bidar
     [not found]       ` <87a5h7o4wu.fsf@>
2024-08-21  8:43         ` Michael Albinus
2024-08-21 13:24           ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-08-23  8:00             ` Michael Albinus [this message]
2024-08-28 11:42               ` Michael Albinus
2024-08-31 15:19                 ` Björn Bidar
     [not found]                 ` <87a5gsn2j9.fsf@>
2024-08-31 17:21                   ` Michael Albinus
2024-09-20 10:04                   ` Michael Albinus
2024-09-22 11:49                     ` Björn Bidar
2024-08-23  4:18           ` Björn Bidar
     [not found]           ` <87seuvg9ck.fsf@>
2024-08-23  8:23             ` Michael Albinus
2024-08-23  8:31               ` Michael Albinus

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=87ttfc3h7d.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
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).