all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Menefee <mpmenefee@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34186@debbugs.gnu.org
Subject: bug#34186: 26.1; locking up
Date: Thu, 24 Jan 2019 08:53:58 -0600	[thread overview]
Message-ID: <CACsqcGENogouCV+fOPPoDgytFQR+Zj-o7FL66fZ3A2h4o_Cg_Q@mail.gmail.com> (raw)
In-Reply-To: <83munq6rmj.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

Hi,

I narrowed it down to a "#define anything(" as the last line in the buffer
will consistently lock up for me.  I'm sure it's the c mode not resolving
something right.  I will experiment more and send you the results if I can
reproduce with minimal buffer content.

Thanks

On Thu, Jan 24, 2019, 8:46 AM Eli Zaretskii <eliz@gnu.org wrote:

> > From: Michael Menefee <mpmenefee@gmail.com>
> > Date: Wed, 23 Jan 2019 10:24:09 -0600
> >
> > Editing a C header file, I type
> > '#define AVL_iter(' and it locks up consistently and has to be killed
> > from another terminal, with CPU at 100%.
>
> I cannot reproduce this.  Does the buffer contain anything else in
> addition to the text you've shown?  Does it happen in "emacs -Q"?
>
> I invoked "emacs -Q", then typed
>
>   C-x C-f headerhang.h
>   #define AVL_iter(
>
> At that point, Emacs was responsive as I'd expect.  Are you doing the
> same to reproduce the problem?
>
> Thanks.
>

[-- Attachment #2: Type: text/html, Size: 1482 bytes --]

  reply	other threads:[~2019-01-24 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 16:24 bug#34186: 26.1; locking up Michael Menefee
2019-01-24 14:45 ` Eli Zaretskii
2019-01-24 14:53   ` Michael Menefee [this message]
2019-01-24 16:32     ` Michael Menefee
2019-01-24 17:41       ` Eli Zaretskii
2019-01-24 18:06         ` Alan Mackenzie
2019-01-25 16:30         ` 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=CACsqcGENogouCV+fOPPoDgytFQR+Zj-o7FL66fZ3A2h4o_Cg_Q@mail.gmail.com \
    --to=mpmenefee@gmail.com \
    --cc=34186@debbugs.gnu.org \
    --cc=eliz@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.