From: Eli Zaretskii <eliz@gnu.org>
To: Gemini Lasswell <gazally@runbox.com>
Cc: emacs-devel@gnu.org
Subject: Re: list-threads
Date: Sun, 09 Sep 2018 19:01:46 +0300 [thread overview]
Message-ID: <835zzer76d.fsf@gnu.org> (raw)
In-Reply-To: <87pnxmu13q.fsf@runbox.com> (message from Gemini Lasswell on Sun, 09 Sep 2018 08:44:41 -0700)
> From: Gemini Lasswell <gazally@runbox.com>
> Date: Sun, 09 Sep 2018 08:44:41 -0700
> Cc: emacs-devel@gnu.org
>
> > . Will the new function backtrace--frames-from-thread (and its
> > subroutines) compile and work in an Emacs configured without
> > threads? If not, they should be conditioned by THREADS_ENABLED.
>
> Yes, they compile. In an Emacs configured without threads,
> backtrace--frames-from-thread is present but will always give a
> wrong-type-argument error, because you can't make a thread object to
> pass to it without make-thread.
It is better to signal an error with a more friendly description that
wrong-type-argument, I think.
Thanks.
prev parent reply other threads:[~2018-09-09 16:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 1:11 list-threads Gemini Lasswell
2018-07-29 7:56 ` list-threads Michael Albinus
2018-07-29 8:37 ` list-threads Michael Albinus
2018-07-29 14:31 ` list-threads Gemini Lasswell
2018-07-29 17:31 ` list-threads Eli Zaretskii
2018-07-30 13:27 ` list-threads Gemini Lasswell
2018-07-30 17:21 ` list-threads Stefan Monnier
2018-07-30 14:59 ` list-threads Eli Zaretskii
2018-08-01 16:03 ` list-threads Gemini Lasswell
2018-08-01 16:37 ` list-threads Eli Zaretskii
2018-08-01 20:04 ` list-threads Gemini Lasswell
2018-08-02 13:53 ` list-threads Eli Zaretskii
2018-08-02 14:51 ` list-threads Gemini Lasswell
2018-08-27 17:38 ` list-threads Gemini Lasswell
2018-08-27 18:48 ` list-threads Eli Zaretskii
2018-09-09 15:44 ` list-threads Gemini Lasswell
2018-09-09 16:01 ` Eli Zaretskii [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:
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=835zzer76d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gazally@runbox.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).