all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 33225@debbugs.gnu.org, "garreau, alexandre" <galex-713@galex-713.eu>
Subject: bug#33225: [debbugs.el] Don't send control message immediately
Date: Sun, 31 Mar 2019 12:21:29 +0200	[thread overview]
Message-ID: <877ecfqr86.fsf@gmx.de> (raw)
In-Reply-To: <87y34x84km.fsf@gmail.com> (Noam Postavsky's message of "Fri, 29 Mar 2019 22:43:37 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

Hi Noam,

Thanks for the patch. In general, it works fine, so I guess you could
push it. We (I)'ll play then for some days, and if there's no serious
complaint, I'll make a new debbugs release.

But I still have some comments :-)

Please rename

debbugs-control-make-message → debbugs-gnu-make-control-message
debbugs-control-message-keywords → debbugs-gnu-control-message-keywords
debbugs-control-message-commands-regexp → debbugs-gnu-control-message-commands-regexp
debbugs-control-message-end-regexp → debbugs-gnu-control-message-end-regexp

Please add (the keybindings of) debbugs-gnu-make-control-message to the
Commentary sections of debbugs-gnu.el and debbugs-org.el and to the nodes
"Tabulated Lists" and "TODO Items" of debbugs-ug.texi.

Compiling debbugs-gnu.el results in

debbugs-gnu.el:1534:1:Warning: Unused lexical variable ‘addr’
debbugs-gnu.el:1552:1:Warning: Unused lexical variable ‘micro’
debbugs-gnu.el:1552:1:Warning: Unused lexical variable ‘subject’

Maybe you can fix it?

> Added, though it looks like the .info file is also in git?  I haven't
> regenerated it since I use texinfo 4.13, so that would trigger all sorts
> of spurious changes.

Yes, unfortunately, the info file must be there. Don't worry about, I'll
regenerate.

> +(defconst debbugs-control-message-keywords
> +  '("serious" "important" "normal" "minor" "wishlist"
> +    "done" "donenotabug" "donewontfix" "doneunreproducible"
> +    "invalid" ; done+notabug+wontfix
> +    "unarchive" "unmerge" "reopen" "close"
> +    "merge" "forcemerge"
> +    "block" "unblock"
> +    "owner" "noowner"
> +    "reassign"
> +    "retitle"
> +    "forwarded" "notforwarded"
> +    ;; 'notfixed <bugnum> <version>' works, even though it's
> +    ;; undocumented at debbugs.gnu.org.
> +    "fixed" "found" "notfound" "notfixed"
> +    "patch" "wontfix" "moreinfo" "unreproducible" "notabug"
> +    "pending" "help" "security" "confirmed" "easy"
> +    "usertag" "user"
> +    "documentation" ;; usertag:emacs.documentation
> +    ))

I suppose "user" is needed in case of debbugs-gnu-make-control-message
only. Could we separate this, and offer completion only for that
function?

> +        ((member message '("merge" "forcemerge"))
> +         (format "%s %d %s\n" message bugid
> +                 (read-string "Merge with bug #: ")))

You have removed the bug number completion via
debbugs-gnu-expand-bug-number-list. Why?

> +        ((member message '("block" "unblock"))
> +         (format
> +          "%s %d by %s\n" message bugid
> +          (mapconcat
> +           'identity
> +           (completing-read-multiple
> +            (format "%s with bug(s) #: " (capitalize message))
> +            (if (equal message "unblock")
> +                (mapcar 'number-to-string
> +                        (cdr (assq 'blockedby status))))
> +            nil (and (equal message "unblock") status))
> +           " ")))

dito

> +@item user
> +"user @var{username}"
> +
> +The username, read interactively, is either a package name or an email
> +address.

Please mention, that this is used in order to avoid giving the user name
again, for further commands.

Best regards, Michael.





  reply	other threads:[~2019-03-31 10:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 12:29 bug#33225: [debbugs.el] Don't send control message immediately Noam Postavsky
2018-11-01 14:28 ` Garreau, Alexandre
2018-11-02 10:30   ` Michael Albinus
2018-11-02 10:23 ` Michael Albinus
2019-01-04 14:38   ` Michael Albinus
2019-02-27  8:45     ` Michael Albinus
2019-02-28  1:10       ` Noam Postavsky
2019-02-28  7:10         ` Michael Albinus
2019-03-30  2:43   ` Noam Postavsky
2019-03-31 10:21     ` Michael Albinus [this message]
2019-03-31 21:27       ` Noam Postavsky
2019-04-01  7:35         ` Michael Albinus
2019-04-01 13:34           ` Noam Postavsky
2019-04-01 14:52             ` Michael Albinus
2019-04-01 22:47               ` Noam Postavsky
2019-04-01 22:59                 ` Noam Postavsky
2019-04-02  5:52                 ` 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=877ecfqr86.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=33225@debbugs.gnu.org \
    --cc=galex-713@galex-713.eu \
    --cc=npostavs@gmail.com \
    /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.