From: Marc Munro <marc@bloodnok.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29726@debbugs.gnu.org
Subject: bug#29726: 25.1; SIGSEGV in find-file
Date: Sat, 16 Dec 2017 12:44:32 -0800 [thread overview]
Message-ID: <1513457072.13815.38.camel@bloodnok.com> (raw)
In-Reply-To: <83o9myqvwd.fsf@gnu.org>
On Sat, 2017-12-16 at 22:07 +0200, Eli Zaretskii wrote:
> > From: Marc Munro <marc@bloodnok.com>
> > Cc: 29726@debbugs.gnu.org
> > Date: Sat, 16 Dec 2017 11:43:08 -0800
> >
> > > doesn't pop up a completions frame, but instead shows this in the
> > > mininbufer:
> > >
> > > DISPLAY BUFFER ACTOR *Backtrace* nil
> >
Oooh. I just re-read this. And although this a debug message, it's
not the same as the one's that I get. What appears to be failing for
you, is the debugger being invoked. I guess that's failing because of
my code.
Replacing the "unless" at the start of k-frame::display-buffer-actor
with the following may allow the backtrace to be shown:
(unless (string= (buffer-name buffer) "*Backtrace*")
My guess is that whatever version you are using is resistant to the
crash and instead reports on whatever stupid thing I have done.
__
Marc
next prev parent reply other threads:[~2017-12-16 20:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 21:48 bug#29726: 25.1; SIGSEGV in find-file Marc Munro
2017-12-16 9:35 ` Eli Zaretskii
2017-12-16 19:43 ` Marc Munro
2017-12-16 20:07 ` Eli Zaretskii
2017-12-16 20:31 ` Marc Munro
2017-12-16 20:35 ` Marc Munro
2017-12-16 20:48 ` Eli Zaretskii
[not found] ` <1513457838.13815.40.camel@bloodnok.com>
2017-12-17 17:23 ` Eli Zaretskii
2017-12-17 19:27 ` Marc Munro
2017-12-23 12:07 ` Eli Zaretskii
2017-12-23 21:05 ` Marc Munro
2017-12-24 3:21 ` Eli Zaretskii
2017-12-16 20:44 ` Marc Munro [this message]
2017-12-16 20:56 ` Eli Zaretskii
2017-12-16 9:42 ` martin rudalics
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=1513457072.13815.38.camel@bloodnok.com \
--to=marc@bloodnok.com \
--cc=29726@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.