From: Eli Zaretskii <eliz@gnu.org>
To: Marc Munro <marc@bloodnok.com>
Cc: 29726@debbugs.gnu.org
Subject: bug#29726: 25.1; SIGSEGV in find-file
Date: Sat, 16 Dec 2017 22:48:05 +0200 [thread overview]
Message-ID: <83mv2iqu0q.fsf@gnu.org> (raw)
In-Reply-To: <1513456260.13815.35.camel@bloodnok.com> (message from Marc Munro on Sat, 16 Dec 2017 12:31:00 -0800)
> From: Marc Munro <marc@bloodnok.com>
> Cc: 29726@debbugs.gnu.org
> Date: Sat, 16 Dec 2017 12:31:00 -0800
>
> > Can you point me to the part of your code which causes the
> > completions
> > to appear in a separate frame?
>
> Yep, it's in k-frame.el
>
> k-frame::display-buffer-actor is the controller for this. It is set up
> to take control from display-buffer by setting:
> display-buffer-overriding-action
>
> Its job is to find the best window for displaying a buffer, mostly
> without splitting windows. When it displays a buffer it highlights the
> window and allows the user to choose an alternative window if they
> don't like it (through F5). That's the theory anyway.
>
> The first (unless... in that function is a, disabled, hack that enables
> a work-around for the crash by treating completions buffers as special
> and doing nothing. The hack is currently disabled by the (and nil
> ....) expression.
OK, but your recipe says "completion frame appears", so somewhere a
new frame should be popped up. Can you point me to the code which
does that in your case? What's the display-buffer-overriding-action's
value in your case?
Also, why does the debug message says the buffer is *Backtrace* in my
case? Does the same happen for you? *Backtrace* is the buffer where
Emacs shows backtrace from Lisp errors, so perhaps something causes an
error in my case?
next prev parent reply other threads:[~2017-12-16 20:48 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 [this message]
[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
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=83mv2iqu0q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29726@debbugs.gnu.org \
--cc=marc@bloodnok.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.