unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <mwd@md5i.com>
To: Alan Mackenzie <acm@muc.de>
Cc: Michael Welsh Duggan <mwd@md5i.com>, 15784@debbugs.gnu.org
Subject: bug#15784: 24.3.50; cc-mode bug reporting
Date: Sun, 10 Nov 2013 13:43:19 -0500	[thread overview]
Message-ID: <87d2m8yu60.fsf@maru2.md5i.com> (raw)
In-Reply-To: <20131110111031.GA3089@acm.acm> (Alan Mackenzie's message of "Sun, 10 Nov 2013 11:10:31 +0000")

Alan Mackenzie <acm@muc.de> writes:

> Hello, Glenn.
>
> On Wed, Nov 06, 2013 at 08:28:39PM +0000, Alan Mackenzie wrote:
>> On Sun, Nov 03, 2013 at 07:31:36PM -0500, Glenn Morris wrote:
>> > Alan Mackenzie wrote:
>
>> > >> It sends to bug-cc-mode@gnu.org.  It might make sense to change this to
>> > >> send to the gnu debbugs list instead, with an appropriate cc-mode tag.
>
>> > If you change c-submit-bug-report to send mail to
>> > submit@debbugs.gnu.org, with an "X-Debbugs-Package: cc-mode" header,
>> > then all those reports will still end up on the bug-cc-mode list, not
>> > the bug-gnu-emacs list (ie, submit@debbugs will act like an alias for
>> > bug-cc-mode). But they will get entered into the tracker and get bug
>> > numbers. So this change would actually make it _less_ easier to lose
>> > cc-mode bugs.
>
>> The header "X-Debbugs-Package:" isn't mentioned in
>> .../admin/notes/bugtracker.  Can you point me at any documentation for
>> it?
>
>> > This is what Gnus does, for example, and they have the same XEmacs
>> > issues as you do. It seems to be working fine for them.
>
>> OK.  This would involve amending `reporter-submit-bug-report'.  I'll look
>> at this.
>
> `reporter-submit-bug-report' doesn't seem amenable to easy amendation.
> The function where the mail headers get inserted into the mail buffer is
> the result of "(get mail-user-agent 'composefunc)".  At this stage, we're
> deep inside the Emacs mail functionality.
>
> I don't think it's worthwhile making such a large change just to get
> debbugs error numbers onto CC Mode bug reports.  But if somebody else
> were to make this change, I'm sure CC Mode could use it.  Patches
> welcome.  ;-)

It seems easy enough.  It looks like just need to add 

        (save-excursion
          (or (mail-position-on-field "X-Debbugs-Package")
              (insert "cc-mode")))

To the lambda you are already passing as the last argument you pass to
`reporter-submit-bug-report' in `c-submit-bug-report'.

-- 
Michael Welsh Duggan
(md5i@md5i.com)





  reply	other threads:[~2013-11-10 18:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 16:01 bug#15784: 24.3.50; cc-mode bug reporting Michael Welsh Duggan
2013-11-03 21:54 ` Alan Mackenzie
2013-11-04  0:31   ` Glenn Morris
2013-11-06 20:28     ` Alan Mackenzie
2013-11-06 20:52       ` Glenn Morris
2013-11-10 11:10       ` Alan Mackenzie
2013-11-10 18:43         ` Michael Welsh Duggan [this message]
2014-01-30  2:59           ` Glenn Morris
2015-05-27  6:31             ` Glenn Morris

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=87d2m8yu60.fsf@maru2.md5i.com \
    --to=mwd@md5i.com \
    --cc=15784@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).