From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org, Eric Abrahamsen <eric@ericabrahamsen.net>
Subject: Re: A few questions about debbugs
Date: Mon, 19 Aug 2024 12:26:54 +0300 [thread overview]
Message-ID: <24373.7537459069$1724059662@news.gmane.org> (raw)
In-Reply-To: <87r0as992a.fsf@gmx.de> (Michael Albinus's message of "Tue, 13 Aug 2024 09:27:25 +0200")
Guten Morgen :)
Michael Albinus <michael.albinus@gmx.de> writes:
> Björn Bidar <bjorn.bidar@thaodan.de> writes:
>
>> Hey,
>
> Hi Björn,
>
>> I have a few questions regardings debbugs, to improve my usage with it.
>> How can I improve the search speed when searching for bugs?
>> For example I'm trying to use debbugs to search the Emacs bugtracker
>> for existing bugs before reporting bugs and the search is so slow that
>> using the website is much faster.
>
> Hmm, it depends on an example. Could you pls show such?
I reproduced this in a clean Emacs config (with-emacs.sh[1]).
0. Install debbugs if not installed
1. debbugs-gnu-search
However I can't reproduce this right now strangely, the issue seems to
just have disappeared on my side.
I maybe the issue was just on my side, the search works relative fast.
Fast enough to not interrupt the IRC process running in Emacs.
Thou it would be awesome if the search would asynchronous.
> Note, that the website has direct access to the bug database, while the
> debbugs package communicates via SOAP with debbugs.gnu.org. There might
> be speed regressions due to this. However, for further analysis, I would
> like to see your example.
I was aware this. I read the documentation when I stumbled upon KDE having once
used Debbugs. To bad that Debbugs can't interact with Bugzilla :)
>> Another thing I wonder is when I try to open a ephemeral bug group to
>> view a bug after closing the group it does return back to another Gnus
>> Group buffer I have open instead of the last one I used the command in.
>> Why is it this way, should debbugs rather use display-buffer here
>> anyway?
>
> This I cannot answer, somebody from the Gnus camp might know
> better. Adding Eric in Cc.
Thank you
---
[1] https://raw.githubusercontent.com/alphapapa/with-emacs.sh/master/with-emacs.sh
next prev parent reply other threads:[~2024-08-19 9:26 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 [this message]
[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
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='24373.7537459069$1724059662@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
--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.
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).