emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: About org-submit-bug-report [9.3 (release_9.3 @ /usr/local/share/emacs/27.0.50/lisp/org/)]
Date: Mon, 03 Feb 2020 20:21:53 +0100	[thread overview]
Message-ID: <874kw7o4ry.fsf@gnu.org> (raw)
In-Reply-To: <87sglf3k9r.fsf@web.de> (Michael Heerdegen's message of "Fri, 20 Dec 2019 01:36:48 +0100")

Hi Michael,

> I want to suggest to make `report-org-bug' and alias for the command
> `org-submit-bug-report'.  That's the name I expected (considering
> "report-emacs-bug"), also some other Emacs packages name their bug
> reporting command according to this scheme.  The additional name would
> make this important command more discoverable.

M-x report TAB only complete `report-emacs-bug' in my setup.
I'm not sure making an exception for Org mode is that useful.

> Second point: When you think it is a trivial task for a common user
> please consider to add some text to the initial buffer contents of the
> message buffer created by this command explaining where one can search
> for existing reports (to avoid duplicates and reports about things that
> are just pitfalls etc).  My buffer included a link to a page explaining
> how to create a good report but there this information is also missing,
> although I think it would be a good place.

I've updated the message a bit, please let me know if this is better:



      parent reply	other threads:[~2020-02-03 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20  0:36 Bug: About org-submit-bug-report [9.3 (release_9.3 @ /usr/local/share/emacs/27.0.50/lisp/org/)] Michael Heerdegen
2019-12-20  9:18 ` [FWD from emacs-orgmode] " Ihor Radchenko
2020-02-03 19:21 ` Bastien [this message]

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874kw7o4ry.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael_heerdegen@web.de \


* 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


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).