From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: unique syntax for reporting (submitting bugs)
Date: Sat, 23 Oct 2021 11:36:32 +0300 [thread overview]
Message-ID: <83fsss5e9b.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=qBjNuP7rBE-c8=XNrPNPq+K=eqk47NTGagU4k4N5xqQ@mail.gmail.com> (message from Stefan Kangas on Sat, 23 Oct 2021 01:16:58 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 23 Oct 2021 01:16:58 -0700
>
> Uwe Brauer <oub@mat.ucm.es> writes:
>
> > So in order not to confuse myself I am using the following alias
> >
> > (defalias 'emacs-submit-bug-report 'report-emacs-bug)
> >
> > But I was wondering, couldn't GNU emacs also use this alias in its
> > default configuration, since it seems a bit more common.
>
> It's a small mess, indeed.
>
> However, we have in etc/TODO:
>
> ** Check for any included packages that define obsolete
> bug-reporting commands
> Change them to use report-emacs-bug.
>
> *** Related functions (do all of them need changing?):
> **** org-submit-bug-report
> **** lm-report-bug
> **** tramp-bug
> **** c-submit-bug-report
>
> I looked into this a little bit two years ago, but then got
> side-tracked. Some of these commands should be kept, from the
> discussion at the time. I'll make sure to remember to update the TODO
> with what I gathered in my notes at that time.
Can't report-emacs-bug intuit what to do by looking at the current
major mode, and perhaps some other variables?
next prev parent reply other threads:[~2021-10-23 8:36 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
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 [this message]
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=83fsss5e9b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
--cc=stefankangas@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 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).