GNU bug report logs - #30676
Please make smie-config-guess interruptible

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 30676 in the body.
You can then email your comments to 30676 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: bug-emacs <bug-emacs <at> gnu.org>
Subject: Please make smie-config-guess interruptible
Date: Fri, 2 Mar 2018 13:16:40 +0000

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.

-- 
https://rrt.sc3d.org

Message #8 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 30676 <at> debbugs.gnu.org
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 02 Mar 2018 17:41:10 -0500

tags 30676 + unreproducible
quit

Reuben Thomas <rrt <at> sc3d.org> writes:

> 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.

Message #13 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 30676 <at> debbugs.gnu.org
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 2 Mar 2018 23:07:29 +0000

On 2 March 2018 at 22:41, Noam Postavsky <npostavs <at> gmail.com> wrote:
> tags 30676 + unreproducible
> quit
>
> Reuben Thomas <rrt <at> sc3d.org> writes:
>
>> 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.

-- 
https://rrt.sc3d.org

Message #16 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 30676 <at> debbugs.gnu.org
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 02 Mar 2018 18:22:14 -0500

Reuben Thomas <rrt <at> sc3d.org> writes:

> On 2 March 2018 at 22:41, Noam Postavsky <npostavs <at> 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.

Message #19 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 30676 <at> debbugs.gnu.org
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 2 Mar 2018 23:28:53 +0000

On 2 March 2018 at 23:22, Noam Postavsky <npostavs <at> gmail.com> wrote:
> Reuben Thomas <rrt <at> sc3d.org> writes:
>
>> On 2 March 2018 at 22:41, Noam Postavsky <npostavs <at> 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.

And I reproduced your result with emasc -Q.

I'm puzzled as to how something in my setup could be making it
uninterruptible, but clearly it's not an Emacs bug; do please close
this, and sorry for the noise: I should have thought of an emacs -Q
test before writing the original report.

If I run smie-config-guess manually with my setup, then I can
interrupt it. The problem arose when I ran it as part of
dtrt-indent-mode (3rd-party code that I maintain):
https://github.com/jscheid/dtrt-indent

But now I can't reproduce the problem, whereas I could several times
earlier today. Oh well. Sorry again.

-- 
https://rrt.sc3d.org

Message #22 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 30676 <at> debbugs.gnu.org
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 02 Mar 2018 18:47:19 -0500

close 30676 
quit

Reuben Thomas <rrt <at> sc3d.org> writes:

>> 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.
>
> And I reproduced your result with emasc -Q.
>
> I'm puzzled as to how something in my setup could be making it
> uninterruptible

Do you have anything that's setting `inhibit-quit'?

Message #27 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: Noam Postavsky <npostavs <at> gmail.com>
Cc: 30676 <at> debbugs.gnu.org
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Fri, 2 Mar 2018 23:51:08 +0000

On 2 March 2018 at 23:47, Noam Postavsky <npostavs <at> gmail.com> wrote:
>
> Do you have anything that's setting `inhibit-quit'?

Not in my own init code, but I see that org-mode and magit and helm do
in various places. So if one of those is somehow leaking…but they all
seem to be let bindings, so surely shouldn't be causing a global
problem…

-- 
https://rrt.sc3d.org

Message #30 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 30676 <at> debbugs.gnu.org, Noam Postavsky <npostavs <at> gmail.com>
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Sat, 03 Mar 2018 09:25:15 +0100

Reuben Thomas <rrt <at> sc3d.org> writes:

>> Do you have anything that's setting `inhibit-quit'?
>
> Not in my own init code, but I see that org-mode and magit and helm do
> in various places. So if one of those is somehow leaking…but they all
> seem to be let bindings, so surely shouldn't be causing a global
> problem…

Maybe a timer function which was called from inside such a let-form?

Best regards, Michael.

Message #33 received at 30676 <at> debbugs.gnu.org (full text, mbox):

From: Reuben Thomas <rrt <at> sc3d.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 30676 <at> debbugs.gnu.org, Noam Postavsky <npostavs <at> gmail.com>
Subject: Re: bug#30676: Please make smie-config-guess interruptible
Date: Sat, 3 Mar 2018 08:28:55 +0000

On 3 March 2018 at 08:25, Michael Albinus <michael.albinus <at> gmx.de> wrote:
> Reuben Thomas <rrt <at> sc3d.org> writes:
>
>>> Do you have anything that's setting `inhibit-quit'?
>>
>> Not in my own init code, but I see that org-mode and magit and helm do
>> in various places. So if one of those is somehow leaking…but they all
>> seem to be let bindings, so surely shouldn't be causing a global
>> problem…
>
> Maybe a timer function which was called from inside such a let-form?

Thanks for the hint. I'll try to keep it in mind if I come across the
problem again.

-- 
https://rrt.sc3d.org

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.