unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: 55794@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>, "Brian Cully" <bjc@spork.org>
Subject: [bug#55794] doc: Add debbugs-gnu-guix command for Emacs.
Date: Sat, 04 Jun 2022 15:32:43 +0300	[thread overview]
Message-ID: <87leucmwwk.fsf@gmail.com> (raw)
In-Reply-To: 87czfpilmn.fsf@gnu.org


[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]

Hi,

Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Brian Cully <bjc@spork.org> skribis:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>>     If you are using Emacs, does debbugs.el have
>>>     shortcomings that make it a problem to review patches?
>
> To be clear, the question was directed primarily at current committers.
>
>> 1) It’d be nice if ‘M-x debbug-guix’ existed. I (briefly) looked at
>> making such a command, thinking it’d be relatively straight-forward to
>> just copy ‘debbugs-gnu’ and tweak some variables, but when it looked
>> like it was going to take more than 10 minutes just to figure out how
>> it was all put together I gave up as I can’t really dedicate time to
>> it right now.
>
> Try: C-u M-x debbugs-gnu.  From there you can choose ‘guix’,
> ‘guix-patches’, or anything else (info "(guix) Debbugs User
> Interfaces").

I have a command in my Emacs config, which is handy to skip those steps.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: doc: Add debbugs-gnu-guix command for Emacs. --]
[-- Type: text/x-patch, Size: 1021 bytes --]

commit a603a7eeb06afa2ebd0c3015ece6fdb5ef43e95a
Author: Oleg Pykhalov <go.wigust@gmail.com>
Date:   Sat Jun 4 03:42:43 2022 +0300

    doc: Add debbugs-gnu-guix command for Emacs.
    
    * doc/contributing.texi (Debbugs User Interfaces): Add debbugs-gnu-guix
    command for Emacs.

diff --git a/doc/contributing.texi b/doc/contributing.texi
index e1902f120f..bf77b6e774 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1459,6 +1459,17 @@ For example, to list all open issues on @code{guix-patches}, hit:
 @kbd{C-u} @kbd{M-x} debbugs-gnu @kbd{RET} @kbd{RET} guix-patches @kbd{RET} n y
 @end example
 
+Additionally, @kbd{M-x debbugs-gnu-guix} command in (@pxref{Init File,,,
+emacs, The GNU Emacs Manual}) can be defined with:
+
+@lisp
+(defun debbugs-gnu-guix ()
+  "List Guix issues."
+  (interactive)
+  (debbugs-gnu '("serious" "important" "normal")
+               '("guix" "guix-patches")))
+@end lisp
+
 @xref{Top,,, debbugs-ug, Debbugs User Guide}, for more information on
 this nifty tool!
 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

           reply	other threads:[~2022-06-04 12:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <87czfpilmn.fsf@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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87leucmwwk.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=55794@debbugs.gnu.org \
    --cc=bjc@spork.org \
    --cc=ludo@gnu.org \
    /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 public inbox

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

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).