From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: npostavs@users.sourceforge.net
Cc: 25122@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Boruch Baum <boruch_baum@gmx.com>
Subject: bug#25122: 24.5; function describe-variable hangs on large variables
Date: Sun, 12 Mar 2017 06:57:41 +0100 [thread overview]
Message-ID: <87d1dnrq96.fsf@gmail.com> (raw)
In-Reply-To: <871su38ogm.fsf@users.sourceforge.net>
npostavs@users.sourceforge.net writes:
> Perhaps we could run the printing in a thread
This is a good idea.
> and suspend it after printing X lines.
Instead just print something like "Computing foo value ..." and let finish
the thread, letting user reading and moving cursor in docstring while it
finishes, once done save-excursion and send message "Computing foo value
done".
> Then hitting RET on "..." would just print another X lines.
I think like Drew that this would be annoying.
That said, what's the reason of choosing the slower approach to compute
value (in a thread or not) instead of using the approach described in
the advice I sent here which takes 1s to compute load-history instead of
3mn ? (I use this advice since one year now without any problems).
--
Thierry
next prev parent reply other threads:[~2017-03-12 5:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 2:21 bug#25122: 24.5; function describe-variable hangs on large variables Boruch Baum
2016-12-06 6:41 ` Thierry Volpiatto
2016-12-07 3:50 ` npostavs
2016-12-07 8:58 ` Thierry Volpiatto
2017-03-11 5:40 ` npostavs
2017-03-11 15:33 ` Stefan Monnier
2017-03-11 19:29 ` Thierry Volpiatto
2017-03-11 21:59 ` npostavs
2017-03-11 23:55 ` Drew Adams
2017-03-12 5:57 ` Thierry Volpiatto [this message]
2017-03-12 14:07 ` Stefan Monnier
2017-03-12 14:15 ` npostavs
2017-03-12 14:59 ` Drew Adams
2017-03-12 16:29 ` Stefan Monnier
2017-03-12 16:32 ` npostavs
2017-03-13 4:47 ` npostavs
2017-03-13 14:01 ` npostavs
2017-03-16 2:54 ` npostavs
2017-04-18 3:53 ` npostavs
2017-04-22 18:25 ` npostavs
2017-04-26 3:57 ` Michael Heerdegen
2017-04-26 10:35 ` Michael Heerdegen
2017-03-11 19:34 ` Thierry Volpiatto
2017-03-12 16:07 ` npostavs
2017-03-11 15:21 ` Stefan Monnier
2017-03-11 15:35 ` npostavs
2017-03-11 19:26 ` Thierry Volpiatto
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=87d1dnrq96.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=25122@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@users.sourceforge.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).