From: Tassilo Horn <tsdh@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21396@debbugs.gnu.org
Subject: bug#21396: 25.0.50; read-key's prompt is not visible
Date: Thu, 03 Sep 2015 20:36:40 +0200 [thread overview]
Message-ID: <874mjbgxjb.fsf@gnu.org> (raw)
In-Reply-To: <83egif9y7z.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 03 Sep 2015 21:03:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> > Putting me in the Cc was more trouble than
>> > anything else: it means I get *your* message instead of the one from
>> > Debbugs, so I don't get to know the bug-number and a naive reply would
>> > end up creating a new bug-nb!
>> > [ Tho, IIRC Glenn(?) added some Message-ID matching to Debbugs to try
>> > and catch those cases. So maybe it's not that bad. ]
>> >
>> > Better either not put the person in the Cc (in case you expect/know the
>> > person subscribes to bug-gnu-emacs), or else use "X-Debbugs-Cc:" which
>> > instructs Debbugs to add the person to the Cc of the messages it sends out.
>>
>> Oh, thanks for the pointer. Do you think it would be a good idea to
>> remap `message-goto-cc' to a similar function which goes to (and thereby
>> creates) the X-Debbugs-Cc header? I think it's generally a good idea to
>> notify the person who introduced some problem, and Cc-ing seems to be
>> the obvious way to do that.
>
> Please don't bother about this. The problem Stefan was worried about
> doesn't exist, AFAIK.
Maybe the double-bug issue doesn't exist but it's a fact that the
Cc-receiver doesn't get to know the bug number automatically, and that's
really annoying. The X-Debbugs-Cc would solve that, and the following
patch is easy enough, no?
--8<---------------cut here---------------start------------->8---
diff --git a/lisp/mail/emacsbug.el b/lisp/mail/emacsbug.el
index f54893f..82d8e74 100644
--- a/lisp/mail/emacsbug.el
+++ b/lisp/mail/emacsbug.el
@@ -143,6 +143,12 @@ This requires either the OS X \"open\" command, or the freedesktop
(defvar message-send-mail-function)
(defvar message-sendmail-envelope-from)
+(defun report-emacs-bug-message-goto-x-debbugs-cc ()
+ "Move point to the X-Debbugs-Cc header."
+ (interactive)
+ (push-mark)
+ (message-position-on-field "X-Debbugs-Cc" "To"))
+
;;;###autoload
(defun report-emacs-bug (topic &optional unused)
"Report a bug in GNU Emacs.
@@ -319,6 +325,8 @@ usually do not have translators for other languages.\n\n")))
;; This is so the user has to type something in order to send easily.
(use-local-map (nconc (make-sparse-keymap) (current-local-map)))
(define-key (current-local-map) "\C-c\C-i" 'info-emacs-bug)
+ (define-key (current-local-map) [remap message-goto-cc]
+ #'report-emacs-bug-message-goto-x-debbugs-cc)
(if can-insert-mail
(define-key (current-local-map) "\C-c\M-i"
'report-emacs-bug-insert-to-mailer))
--8<---------------cut here---------------end--------------->8---
Bye,
Tassilo
next prev parent reply other threads:[~2015-09-03 18:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 20:14 bug#21403: 25.0.50; invisible y-or-n-p prompt Mark Oteiza
2015-09-03 20:03 ` Stefan Monnier
2015-09-02 6:16 ` bug#21396: 25.0.50; read-key's prompt is not visible Tassilo Horn
2015-09-03 15:12 ` Stefan Monnier
2015-09-03 17:50 ` Tassilo Horn
2015-09-03 18:03 ` Eli Zaretskii
2015-09-03 18:36 ` Tassilo Horn [this message]
2015-09-03 18:18 ` Eli Zaretskii
2015-09-03 18:42 ` Tassilo Horn
2015-09-04 6:38 ` Eli Zaretskii
2015-09-04 8:04 ` Tassilo Horn
2015-09-04 8:38 ` Eli Zaretskii
2015-09-04 9:27 ` Tassilo Horn
2015-09-03 20:10 ` Stefan Monnier
2015-09-03 20:12 ` Dmitry Gutov
[not found] ` <<87egifgzog.fsf@gnu.org>
[not found] ` <<83d1xz9xjz.fsf@gnu.org>
2015-09-03 18:27 ` Drew Adams
[not found] ` <handler.21396.D21403.144131058918410.notifdone@debbugs.gnu.org>
2015-09-03 20:07 ` bug#21396: closed (Re: bug#21403: 25.0.50; invisible y-or-n-p prompt) Tassilo Horn
2015-09-03 23:02 ` bug#21403: 25.0.50; invisible y-or-n-p prompt Mark Oteiza
2015-09-07 17:17 ` Stefan Monnier
2015-09-07 17:28 ` Stefan Monnier
2015-09-07 1:04 ` Chris Feng
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mjbgxjb.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=21396@debbugs.gnu.org \
--cc=eliz@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/emacs.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).