From: Drew Adams <drew.adams@oracle.com>
To: Uwe Brauer <oub@mat.ucm.es>, "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: unique syntax for reporting (submitting bugs)
Date: Sat, 23 Oct 2021 15:50:53 +0000 [thread overview]
Message-ID: <SJ0PR10MB54886CB03B8D5F5B360C2E75F3819@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87sfws7x0c.fsf@mat.ucm.es>
> There are two issues here.
> 1. Have a common syntax for sending bug reports, for example
> - package-report-bug or
> - package-submit-bug-report
> 2. The other, more complex issue, is that within GNU emacs the
> command emacs-report-bug would send an appropriate bug report
> based on the mayor mode used when calling the bug-report
> function
I don't see the lack of uniqueness as a real problem.
Can you give an example/scenario that points out what
problems might arise from it? I'm not saying there
are none; I just can't see them yet.
What you show there are descriptions of solutions.
It's the problems they're intended to fix that I have
trouble imagining (so far).
___
[FWIW, for my libraries I use "<libname>-send-bug-report".
In this case the command just invokes `browse-url' with
a `mailto:' that constructs a mail skeleton with Subject
line and some instructions and the emacs-version in the
body. (Sending an email isn't much in the way of
"submitting" a report.)]
next prev parent reply other threads:[~2021-10-23 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 7:31 unique syntax for reporting (submitting bugs) Uwe Brauer
2021-10-23 7:40 ` Po Lu
2021-10-23 12:20 ` Uwe Brauer
2021-10-23 12:40 ` Po Lu
2021-10-23 16:04 ` Uwe Brauer
2021-10-23 15:50 ` Drew Adams [this message]
2021-10-23 16:07 ` [External] : " Uwe Brauer
2021-10-23 16:43 ` Uwe Brauer
2021-10-23 16:44 ` Drew Adams
2021-10-23 8:16 ` Stefan Kangas
2021-10-23 8:36 ` Eli Zaretskii
2021-10-23 9:48 ` Stefan Kangas
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=SJ0PR10MB54886CB03B8D5F5B360C2E75F3819@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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).