From: Visuwesh <visuweshm@gmail.com>
To: Juergen Fenn <jfenn@gmx.net>, Eli Zaretskii <eliz@gnu.org>,
Ihor Radchenko <yantar92@posteo.net>
Cc: alan@idiocy.org, emacs-devel@gnu.org, numbchild@gmail.com
Subject: Re: [BR] Clipboard support on macOS and Org 9.7
Date: Tue, 18 Jun 2024 10:03:56 +0530 [thread overview]
Message-ID: <130FDFF7-D630-4DE9-A962-FF8550A3D727@gmail.com> (raw)
In-Reply-To: <4dc83a0b-567b-4d57-aa78-533921eae1a4@gmx.net>
On 18 June 2024 04:00:06 GMT+05:30, Juergen Fenn <jfenn@gmx.net> wrote:
>
>
>Am 17.06.24 um 14:07 Uhr schrieb Eli Zaretskii:
>> I'd prefer a bug report with all the details, TIA.
>
>Eli, I'd be happy to give you all the information you need in order to
>improve the NextStep/macOS port, but I am unsure about how to do that. I
>am used to reporting bugs on bug trackers such as Mozilla's Bugzilla and
>Wikimedia's Phabricator, while you seem to prefer an email-based
>workflow, don't you?
>
>Which details do you lack, and what do I have to do in order to provide
>them to you? When I posted to the list yesterday I thought it would be
>enough to link to the debugging we already did on the Org mailing list
>the other day, but it looks like i was wrong.
M-x report-emacs-bug RET and include all the necessary details. I think everything that you sent so far and the latest message in org ML by JD Smith should be good. I think Eli would prefer if you include a summary of what has been discussed already in the org ML with links to the messages to know it in greater detail.
Thanks.
>Thanks and best regards,
>Jürgen.
next prev parent reply other threads:[~2024-06-18 4:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 21:22 [BR] Clipboard support on macOS and Org 9.7 Juergen Fenn
2024-06-17 11:00 ` Eli Zaretskii
2024-06-17 11:15 ` Ihor Radchenko
2024-06-17 12:07 ` Eli Zaretskii
2024-06-17 22:30 ` Juergen Fenn
2024-06-18 4:33 ` Visuwesh [this message]
2024-06-18 12:43 ` Eli Zaretskii
2024-06-17 12:05 ` Robert Pluim
2024-06-17 22:25 ` Juergen Fenn
2024-06-18 7:37 ` Robert Pluim
2024-06-22 20:16 ` Juergen Fenn
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=130FDFF7-D630-4DE9-A962-FF8550A3D727@gmail.com \
--to=visuweshm@gmail.com \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jfenn@gmx.net \
--cc=numbchild@gmail.com \
--cc=yantar92@posteo.net \
/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).