unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Elias Schwerdtfeger <nachtwaechter@tamagothi.de>
Cc: 25451@debbugs.gnu.org
Subject: bug#25451: 24.5; Freeze after while-keyword in sh-mode
Date: Sat, 14 Jan 2017 23:03:19 -0500	[thread overview]
Message-ID: <87mvetx94o.fsf@users.sourceforge.net> (raw)
In-Reply-To: <e3064508-c443-f1b3-bc88-29bd92ff3225@tamagothi.de> (Elias Schwerdtfeger's message of "Sun, 15 Jan 2017 00:05:55 +0100")

tags 25451 unreproducible
close 25451
quit

Elias Schwerdtfeger <nachtwaechter@tamagothi.de> writes:

> Am 14.01.2017 um 23:37 schrieb Noam Postavsky:
>> I'm sure what this means, and I'm not able to reproduce this.
>>
>
> That's really strange. I can't reproduce it now.
>
> A few hours ago I reproduced the bug five times, before I decided to
> file it as the first bug I found in nearly twenty years. Of course I
> killed emacs every time, before I used text-mode.
>
> It is not as simple as I thought first, and together with its
> reproducibility any chance of analyzing and fixing the bug has gone. I
> suggest closing this issue.

Ok, closing as unreproducible.

>
>> Can you reproduce it by just copying that text into a sh-mode buffer,
>> or does it only happen while typing?
>
> The first time I encountered the problem, it happened while I was
> typing. In all of my reproductions it happened after opening or
> recovering the file, when the mark reached the line with 'while'.
>
> Both is possible without freezing Emacs now, and I don't know why. Today
> is a good day for a RAM check.

Well, the symptoms suggest an infinite loop during fontification.  Do
report back if you can find a way to reproduce it consistently.





      reply	other threads:[~2017-01-15  4:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-14 20:54 bug#25451: 24.5; Freeze after while-keyword in sh-mode Elias Schwerdtfeger
2017-01-14 22:37 ` Noam Postavsky
2017-01-14 23:05   ` Elias Schwerdtfeger
2017-01-15  4:03     ` npostavs [this message]

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=87mvetx94o.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25451@debbugs.gnu.org \
    --cc=nachtwaechter@tamagothi.de \
    /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).