all messages for Emacs-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: help-gnu-emacs@gnu.org
Subject: Re: Use Debbugs to search for only open bugs
Date: Fri, 05 Aug 2022 09:08:01 +0200	[thread overview]
Message-ID: <87zggjcgmm.fsf@gmx.de> (raw)
In-Reply-To: <87y1w323wb.fsf@dismail.de> (Joshua Branson's message of "Thu, 04 Aug 2022 15:40:52 -0400")

Joshua Branson <jbranso@dismail.de> writes:

Hi Joshua,

> Can anyone give my a simple debbugs function, that will prompt me for a
> search string, and return a list of open bugs for "guix" and
> "guix-patches"?
>
> Here's what I've come up with so far:
>
> #+BEGIN_SRC emacs-lisp
> (defun debbugs-guix-search ()
>   (interactive)
>   (debbugs-gnu-search (read-string "Search String: ") nil nil '("guix" "guix-patches") nil))
> #+END_SRC
>
> The only problem with this function is that it shows open bug reports.
> 90% of the time I am not interested in those bug reports.

From your description it isn't obvious to me, whether you want to see
just open bugs, or not. But you can play with the QUERY argument of
debbugs-gnu-search, like

--8<---------------cut here---------------start------------->8---
(debbugs-gnu-search (read-string "Search String: ") '((pending . "open")) nil '("guix" "guix-patches"))
--8<---------------cut here---------------end--------------->8---

> Thanks!

Best regards, Michael.



  parent reply	other threads:[~2022-08-05  7:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 19:40 Use Debbugs to search for only open bugs Joshua Branson
2022-08-05  1:25 ` Michael Heerdegen
2022-08-05  7:08 ` Michael Albinus [this message]
2022-08-05  8:55   ` Joshua Branson
2022-08-05  9:46     ` Michael Albinus
2022-08-10 13:54       ` Michael Albinus
2022-08-10 15:17         ` Joshua Branson
2022-08-10 15:25         ` Joshua Branson
2022-08-10 16:23           ` 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

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

  git send-email \
    --in-reply-to=87zggjcgmm.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=help-gnu-emacs@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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.