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: Fri, 02 Nov 2018 11:23:03 +0100	[thread overview]
Message-ID: <87efc3lqwo.fsf@gmx.de> (raw)
In-Reply-To: <87k1lxhtfc.fsf@gmail.com> (Noam Postavsky's message of "Thu, 01 Nov 2018 08:29:59 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

Hi Noam,

> As mentioned in [1], I have a modified version of
> debbugs-gnu-send-control-message which just creates the message (or
> edits the current one) rather than sending it right away.  I'm posting
> it here as a patch to debbugs-gnu.el.

Looks interesting. It seems better suited to extend existing messages,
when replying to another bug-related message.

However, when I call it interactively for control message
"documentation", I get an error:

save-excursion: Search failed: "^user emacs$"

Maybe you could fix it? Furthermore, it asks me for the bug id, even if
the Cc: header contains already such. I guess it could retrieve this
there, and show me as default if it is unique.

> It might make sense to replace the current
> debbugs-gnu-send-control-message, or just factor out the common parts,
> I haven't really thought much about that.

I believe we should keep both functions (with a common basic function),
with different key bindings. "C" for debbugs-gnu-send-control-message,
and maybe "E" for debbugs-control-make-message.

I like also your extensions of the control messages. Would you like to
document them in debbugs-ug.texi?

Best regards, Michael.





  parent reply	other threads:[~2018-11-02 10:23 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 [this message]
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
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=87efc3lqwo.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.