all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 30676@debbugs.gnu.org
Subject: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 02 Mar 2018 18:22:14 -0500	[thread overview]
Message-ID: <87r2p22hcp.fsf@gmail.com> (raw)
In-Reply-To: <CAOnWdoi1ibP261-FyBG+2E+B7t+Xote-gJzVFnFtBq1Zmu=C+A@mail.gmail.com> (Reuben Thomas's message of "Fri, 2 Mar 2018 23:07:29 +0000")

Reuben Thomas <rrt@sc3d.org> writes:

> On 2 March 2018 at 22:41, Noam Postavsky <npostavs@gmail.com> wrote:

>>> It would be nice if one could run smie-config-guess without having to
>>> worry about it locking up Emacs on large buffers. If it were possible
>>> to interrupt it with C-g, that would make it friendlier.
>>
>> C-g interrupts just fine for me; since it written in lisp, I can't see
>> why it should be otherwise.
>
> Indeed, I was a bit surprised, but I ran it on my ~/.bash_history
> (about 10Mb, 900,000 lines) and however many times I pressed C-g, it
> just sat there slowly counting through the "Analyzing" progress meter,
> and Emacs taking 100% CPU.

I just checked again, with a file produced by re-catting my
~/.bash_history until it's 900,000 lines (I got ~13MB), C-g still works
fine here.





  reply	other threads:[~2018-03-02 23:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-02 13:16 bug#30676: Please make smie-config-guess interruptible Reuben Thomas
2018-03-02 22:41 ` Noam Postavsky
2018-03-02 23:07   ` Reuben Thomas
2018-03-02 23:22     ` Noam Postavsky [this message]
2018-03-02 23:28       ` Reuben Thomas
2018-03-02 23:47         ` Noam Postavsky
2018-03-02 23:51           ` Reuben Thomas
2018-03-03  8:25             ` Michael Albinus
2018-03-03  8:28               ` Reuben Thomas

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=87r2p22hcp.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=30676@debbugs.gnu.org \
    --cc=rrt@sc3d.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.