From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: [External] : Re: unique syntax for reporting (submitting bugs)
Date: Sat, 23 Oct 2021 18:07:55 +0200 [thread overview]
Message-ID: <878ryj912c.fsf@mat.ucm.es> (raw)
In-Reply-To: SJ0PR10MB54886CB03B8D5F5B360C2E75F3819@SJ0PR10MB5488.namprd10.prod.outlook.com
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
>>> "DA" == Drew Adams <drew.adams@oracle.com> writes:
>> 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).
May it is just me. When I want to send a bug report, for some
package/library the first thing I do is running the apropos-command and
searching the word bug, to find out the specific syntax. As I said there
is, at least
- libname-report-bug
- libname-submit-bug-report
- libname-send-bug-report (your example)
So that is confusing I say. If one convention would be chosen, like in
«one ring to rule them all» I think it would simplify things a bit.
At least that is my experience over the years
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2021-10-23 16:07 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 ` [External] : " Drew Adams
2021-10-23 16:07 ` Uwe Brauer [this message]
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=878ryj912c.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=emacs-devel@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).