all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Brady Trainor <mail@bradyt.com>, 32030-done@debbugs.gnu.org
Subject: bug#32030: 27.0.50; debug-on-signal, void-variable
Date: Wed, 21 Aug 2019 04:22:19 +0200	[thread overview]
Message-ID: <CADwFkmnM8roc-+=QJUqp-GFZieeCsM+MRLDT-DXptFUn31cgFA@mail.gmail.com> (raw)
In-Reply-To: <20180702013808.9B014E4621@mailuser.nyi.internal>

Noam Postavsky <npostavs@gmail.com> writes:

> forwarded 32030 https://github.com/nex3/dart-mode/issues/30
> quit
>
> On 2 July 2018 at 01:38, Noam Postavsky <npostavs@gmail.com> wrote:
>
>> If this is getting called from redisplay, I think the debugger might be
>> suppressed from that context, even if you set debug-on-signal.  I seem
>> to recall triggerring refontification synchronously with M-o M-o
>> (font-lock-fontify-block) worked for me in a similar situation (although
>> it's possible you won't hit the error this way).
>
> I can get a backtrace this way, I posted to the dart-mode issue:
>
> https://github.com/nex3/dart-mode/issues/30#issuecomment-403521238

This issue seems to not be related to a third party package (and the
link to the issue in the dart-mode issue tracker has additionally now
been fixed).  I'm therefore closing this bug report.

Thanks,
Stefan Kangas





      parent reply	other threads:[~2019-08-21  2:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  1:38 bug#32030: 27.0.50; debug-on-signal, void-variable Brady Trainor
2018-07-02  3:05 ` Noam Postavsky
2018-07-02  5:13   ` Brady Trainor
2018-07-02  5:38     ` Noam Postavsky
2018-07-02 14:37       ` Eli Zaretskii
2018-07-09 15:38       ` Noam Postavsky
2019-08-21  2:22 ` Stefan Kangas [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmnM8roc-+=QJUqp-GFZieeCsM+MRLDT-DXptFUn31cgFA@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=32030-done@debbugs.gnu.org \
    --cc=mail@bradyt.com \
    --cc=npostavs@gmail.com \
    /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.