From: Gemini Lasswell <gazally@runbox.com>
To: Emacs Development <emacs-devel@gnu.org>
Subject: Re: list-threads
Date: Mon, 27 Aug 2018 10:38:06 -0700 [thread overview]
Message-ID: <87efej3e2p.fsf@runbox.com> (raw)
In-Reply-To: <87tvoiq208.fsf@runbox.com> (Gemini Lasswell's message of "Sat, 28 Jul 2018 18:11:51 -0700")
I've just pushed an update to the scratch/list-threads branch which
includes:
- lisp/thread.el, the new home for thread-related Lisp functions.
- A 'b' command in the *Threads* buffer which shows a backtrace of where
the thread at point had yielded or was blocked at the moment you
pressed 'b'.
- Documentation and a NEWS entry.
- Tests.
There are no local variables in the thread backtraces. I experimented a
bit with making Fbacktrace__locals work on non-current threads, with
mixed results (success in extracting variable values at the cost of
corrupting something making Emacs prone to crashing afterwards), and
decided that feature is more difficult (for me, at the present time)
than it is important.
If you have any feedback, let me know, otherwise I'll merge this in a
few days.
next prev parent reply other threads:[~2018-08-27 17:38 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 ` Gemini Lasswell [this message]
2018-08-27 18:48 ` list-threads Eli Zaretskii
2018-09-09 15:44 ` list-threads Gemini Lasswell
2018-09-09 16:01 ` list-threads 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=87efej3e2p.fsf@runbox.com \
--to=gazally@runbox.com \
--cc=emacs-devel@gnu.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.