From: tpeplt <tpeplt@gmail.com>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: Jean-Christophe Helary via Users list for the GNU Emacs text
editor <help-gnu-emacs@gnu.org>,
Jean-Christophe Helary
<jean.christophe.helary@traductaire-libre.org>
Subject: Re: Handling the message:// protocol in Emacs
Date: Wed, 01 Jan 2025 22:40:42 -0500 [thread overview]
Message-ID: <87wmfdannp.fsf@gmail.com> (raw)
In-Reply-To: <67749c6e.e90a0220.291618.33c5SMTPIN_ADDED_BROKEN@mx.google.com> ("Björn Bidar"'s message of "Wed, 01 Jan 2025 03:37:05 +0200")
Björn Bidar <bjorn.bidar@thaodan.de> writes:
>>> It would be good if org-mode could recognize that protocol out of the box...
>>
>> Because ‘org-mode’ is included with Emacs, you might consider reporting
>> this behavior using M-x report-emacs-bug, either as a desired feature
>> for Emacs or as a mistake in how Emacs is working. If it is the latter,
>> then consider looking at the Emacs user manual’s chapter on Org mode,
>> (info "(emacs) Org Mode"), and demonstrating how Emacs’s behavior does
>> not match the manual.
>
> I agree but please use M-x org-submit-bug-report instead.
Thanks. I was not aware of that command.
Using: C-h a bug report RET
produces the following list in Emacs 29.4:
debbugs-org-emacs-release-blocking-reports M-x ... RET
Show the reports that are blocking an Emacs release.
lm-report-bug M-x ... RET
Report a bug in the package currently being visited to its maintainer.
org-submit-bug-report M-x ... RET
Submit a bug report on Org via mail.
package-report-bug M-x ... RET
Prepare a message to send to the maintainers of a package.
report-emacs-bug <menu-bar> <help-menu> <send-emacs-bug-report>
Report a bug in GNU Emacs.
--
The lyf so short, the craft so long to lerne.
- Geoffrey Chaucer, The Parliament of Birds.
next prev parent reply other threads:[~2025-01-02 3:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 14:01 Handling the message:// protocol in Emacs Jean-Christophe Helary via Users list for the GNU Emacs text editor
2024-12-30 18:54 ` tpeplt
2025-01-01 1:37 ` Björn Bidar
[not found] ` <67749c6e.e90a0220.291618.33c5SMTPIN_ADDED_BROKEN@mx.google.com>
2025-01-02 3:40 ` tpeplt [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-30 2:22 Jean-Christophe Helary via Users list for the GNU Emacs text editor
2024-12-30 4:29 ` Björn Bidar
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=87wmfdannp.fsf@gmail.com \
--to=tpeplt@gmail.com \
--cc=bjorn.bidar@thaodan.de \
--cc=help-gnu-emacs@gnu.org \
--cc=jean.christophe.helary@traductaire-libre.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.
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).