From: Ihor Radchenko <yantar92@gmail.com>
To: Akib Azmain Turja <akib@disroot.org>
Cc: 57197@debbugs.gnu.org
Subject: bug#57197: 28.1.90; Can pure side-effect-free functions use multiple CPUs in Elisp?
Date: Mon, 15 Aug 2022 16:05:43 +0800 [thread overview]
Message-ID: <87v8qux76w.fsf@localhost> (raw)
In-Reply-To: <87a68659ro.fsf@disroot.org>
Akib Azmain Turja <akib@disroot.org> writes:
> I think the problem is the interpreter itself, which is not
> thread-safe.
Thanks for the clarification! This is unfortunate.
> This looks like a feature request, I think emacs-devel is good for that.
I have heard on emacs-devel that M-x report-emacs-bug should also be
used for feature requests. Moreover, CONTRIBUTE says:
Bug reports and fixes, feature requests and patches/implementations
should be sent to bug-gnu-emacs@gnu.org, the bug/feature list. This
is coupled to the https://debbugs.gnu.org tracker. It is best to use
the command 'M-x report-emacs-bug RET' to report issues to the tracker
(described below). Be prepared to receive comments and requests for
changes in your patches, following your submission.
Let me know if I miss something.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
next prev parent reply other threads:[~2022-08-15 8:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 4:18 bug#57197: 28.1.90; Can pure side-effect-free functions use multiple CPUs in Elisp? Ihor Radchenko
2022-08-15 5:57 ` Akib Azmain Turja
2022-08-15 7:13 ` Lars Ingebrigtsen
2022-08-15 8:05 ` Ihor Radchenko [this message]
2022-08-15 9:43 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 11:46 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8qux76w.fsf@localhost \
--to=yantar92@gmail.com \
--cc=57197@debbugs.gnu.org \
--cc=akib@disroot.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.