all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Joshua Branson <jbranso@dismail.de>
Cc: 56987@debbugs.gnu.org
Subject: [bug#56987] [PATCH] etc: guix-debbugs.el: new file.
Date: Wed, 10 Aug 2022 18:44:52 +0200	[thread overview]
Message-ID: <87sfm4dp4r.fsf@gmx.de> (raw)
In-Reply-To: <20220805012310.5999-1-jbranso@dismail.de> (Joshua Branson's message of "Thu, 4 Aug 2022 21:23:10 -0400")

Joshua Branson <jbranso@dismail.de> writes:

Hi Joshua,

just some comments after short reading of the patch.

>  @example
>  @kbd{C-u} @kbd{M-x} debbugs-gnu @kbd{RET} @kbd{RET} guix-patches @kbd{RET} n y
>  @end example

Alternatively, a user could set debbugs-gnu-default-packages to '("guix" "guix-patches")
Then it won't be necessary to enter the package name(s) again and again.

> +;; Copyright (C) 2022 Joshua Branson

This would change to FSF, if bundled with the debbugs package.

> +;; Package-Requires: ((emacs "24.3"))

debbugs.el says

;; Package-Requires: ((emacs "26.1") (soap-client "3.1.5"))

So I guess you might lift up the required Emacs version.

> +;; TODO make this by default only search open bugs AND NOT closed bugs.
> +(defun debbugs-guix-search ()
> +  (interactive)
> +  (debbugs-gnu-search (read-string "Search String: ") nil nil '("guix" "guix-patches") nil))

As said the other message, it should be

(debbugs-gnu-search (read-string "Search String: ") '((pending . "pending")) nil '("guix" "guix-patches"))

> +;; The debbugs database runs once a day.  So after I send a bug report
> +;; and run this command, my latest bug report might not be here.  No worries,
> +;; just wait one day, and it will be there.  :)

To be more precise, the Hyperestraier search engine on debbugs.gnu.org
makes new indices after that period. New submitted bugs are in the
debbugs database shortly after sending the message. It is just
debbugs-gnu-search, which needs these indices.

> +;; I have noticed that this function works 80% of the time.  But after I close bug reports,
> +;; it seems to stop working for about 1/2 hour.  I'm guessing the server's database
> +;; resets itself after every time that I close a bug report...

debbugs.el uses a cache, which flushes the value after an hour. See the
variable debbugs-cache-expiry.

There is the command debbugs-gnu-rescan, bound to key "g", which rescans
an existing tabulated list. With a prefix argument ("C-u g"), the cache
is ignored, and the data are retrieved directly from debbugs.gnu.el.

However, please be cautious with invalidating the cache. Every action on
the debbugs.gnu.org server causes a workload there, and we don't want to
overuse it.

Best regards, Michael.




  parent reply	other threads:[~2022-08-10 17:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  1:23 [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-05  1:32 ` Joshua Branson via Guix-patches via
2022-08-10 15:16   ` Joshua Branson via Guix-patches via
2022-08-10 16:44 ` Michael Albinus [this message]
2022-08-10 20:10 ` jbranso--- via Guix-patches via
2022-08-10 20:24   ` Maxime Devos
2022-08-10 20:39   ` jbranso--- via Guix-patches via
2022-08-10 21:22   ` [bug#56987] Requesting help in assigning copright to Emacs's debbugs jbranso--- via Guix-patches via
2022-08-11 19:51     ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
     [not found]     ` <304e6f0d877d6b8bb60db051e661edf1@dismail.de>
2022-08-17 20:14       ` [bug#56987] Fwd: [gnu.org #1863422] Joshua Allen Branson GNU EMACS jbranso--- via Guix-patches via
2022-08-18  9:52         ` Michael Albinus
2022-08-22 17:21           ` [bug#56987] [PATCH] etc: guix-debbugs.el: new file Joshua Branson via Guix-patches via
2022-08-11  6:24   ` Michael Albinus
2022-08-11 15:25     ` Joshua Branson via Guix-patches via
2022-08-11 16:06       ` Michael Albinus
2022-08-13 22:49         ` Joshua Branson via Guix-patches via
2022-08-12 19:17       ` jbranso--- via Guix-patches via
2022-10-01 15:39 ` [bug#56987] [PATCH] added *my-open-bugs functions Joshua Branson via Guix-patches via
2022-10-02 12:52   ` Michael Albinus
2022-10-03 20:02   ` jbranso--- via Guix-patches via
2022-10-04 14:15     ` Michael Albinus
2022-10-05 16:41 ` [bug#56987] [PATCH] new functions 'debbugs-gnu-my-open-bugs' and 'debbugs-gnu-guix-search' Joshua Branson via Guix-patches via
2022-10-05 20:10   ` bug#56987: " Michael Albinus
     [not found] <rt-4.2.16-14-g9a593ee-12923-1660753466-248.1863422-5-0@rt.gnu.org>
     [not found] ` <RT-Ticket-1863422@rt.gnu.org>
     [not found]   ` <rt-4.2.16-14-g9a593ee-21845-1660236515-917.1863103-5-0@rt.gnu.org>

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=87sfm4dp4r.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=56987@debbugs.gnu.org \
    --cc=jbranso@dismail.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.