From: Michael Albinus <michael.albinus@gmx.de>
To: "Garreau\, Alexandre" <galex-713@galex-713.eu>
Cc: 33225@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#33225: [debbugs.el] Don't send control message immediately
Date: Fri, 02 Nov 2018 11:30:10 +0100 [thread overview]
Message-ID: <87a7mrlqkt.fsf@gmx.de> (raw)
In-Reply-To: <871s84g9cp.fsf@portable.galex-713.eu> (Alexandre Garreau's message of "Thu, 01 Nov 2018 15:28:54 +0100")
"Garreau, Alexandre" <galex-713@galex-713.eu> writes:
Hi Alexandre,
>> 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 believe this is the most straightforward solution to the problem of
> control messages sending too fast for the newcomer user.
As you have seen the other message, I'm also in favor of this solution.
> However, I guess this is a feature more than a bug for most used
> users, and this would have been only useful for the first time to me,
> when I wanted to “test it to see how it looks” thinking of “cancelling
> at the last moment”, and discovered the mail was already sent before I
> could even understand what was happening (and take the time to
> document more myself on what was the control message really meaning).
> Sure if I saw a message-mode buffer before, at this moment, I’d have
> canceled, but that would only have been useful the first time: then it
> would have become tiring, so I would have disabled it to come back the
> simple behavior, and loose the benefit of the additional
> security-check step.
In fact I believe we shall offer both
functions. debbugs-gnu-send-control-message, without any confirmation,
is good for experienced users. When you are working on a bug triage, for
example, you need a fluid workflow, w/o interruption for confirmation
and alike.
> What I suggested later instead was asking for confirmation for certain
> control messages that might uselessly garble and bloat the bug history,
> while letting go more common and useful messages that might otherwise
> anyway be undone without semantic overhead [2], first suggestion was
> just about asking for confirmation about certain messages and not
> others, so I attach the already suggested [3] patch here for better
> referencing of it. But in last message [2] I argued in favor of better
> discrimination among control messages and potentially clarifying their
> meaning and better linking doc.
I believe it is a matter of personal taste, which control messages need
a confirmation, and which not. And this will change also over the
time. Oce you know what "owner" is intended for, you don't need to
confirm this again and again.
What I could imagine is, that you implement an explanation for the
control messages, based on Noam's debbugs-control-make-message. This
needs an emhancement in the manuals, but I'm working on.
Best regards, Michael.
next prev parent reply other threads:[~2018-11-02 10:30 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 [this message]
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
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=87a7mrlqkt.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.