From: Alexis <flexibeast@gmail.com>
To: 20074@debbugs.gnu.org
Subject: bug#20074: edebug tracing can't be stopped with 'S'
Date: Fri, 13 Mar 2015 21:19:57 +1100 [thread overview]
Message-ID: <87fv999p2q.fsf@gmail.com> (raw)
In-Reply-To: <CA+3HrJVfs3PRSTq1=Y-XqSbT6Exqr6LYi_AB3aPCCt94wooKYw@mail.gmail.com>
On 2015-03-13T20:36:09+1100, Mario Valencia
<mariovalspi@gmail.com> said:
MV> So is this going to be fixed or what?
i'd be interested to know whether this behaviour is considered a
bug. When i see tight code loops like this, my first thought -
based on
experience - is: "When is the rest of the system [in this
instance, the Emacs system] going to get a chance to do anything,
such as read and handle input events?"
Do Emacs devs feel that Emacs should still be reasonably
responsive in the face of such tight loops?
Alexis.
next prev parent reply other threads:[~2015-03-13 10:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 20:42 bug#20074: edebug tracing can't be stopped with 'S' Mario Valencia
2015-03-11 16:24 ` Eli Zaretskii
[not found] ` <CA+3HrJXsgWHQG_6zk2vNXzEaqT8w-5-cw26fkLYH0xQXmk=nSQ@mail.gmail.com>
2015-03-11 16:28 ` bug#20074: Fwd: " Mario Valencia
2015-03-11 16:30 ` Mario Valencia
2015-03-13 9:36 ` Mario Valencia
2015-03-13 10:19 ` Alexis [this message]
2015-03-13 11:07 ` Eli Zaretskii
2015-03-13 11:37 ` Alexis
2015-03-13 13:20 ` Stefan Monnier
2015-03-13 14:02 ` Alexis
2015-03-14 18:49 ` Mario Valencia
[not found] ` <mailman.2024.1426359010.31049.bug-gnu-emacs@gnu.org>
2015-03-15 16:06 ` Alan Mackenzie
2015-03-15 20:36 ` Stefan Monnier
2015-03-15 21:31 ` Alan Mackenzie
[not found] ` <mailman.2056.1426435627.31049.bug-gnu-emacs@gnu.org>
2015-03-15 19:55 ` Alan Mackenzie
2015-03-16 3:12 ` Stefan Monnier
2015-03-16 11:38 ` Alan Mackenzie
2015-03-16 13:11 ` Stefan Monnier
[not found] ` <mailman.1823.1426020966.31049.bug-gnu-emacs@gnu.org>
2015-03-16 22:21 ` Alan Mackenzie
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=87fv999p2q.fsf@gmail.com \
--to=flexibeast@gmail.com \
--cc=20074@debbugs.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.