From: "Joe" <Johannes.Labisch@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Splitting window displayed in special frame
Date: 29 Jan 2007 04:28:04 -0800 [thread overview]
Message-ID: <1170073684.920901.20240@h3g2000cwc.googlegroups.com> (raw)
In-Reply-To: <1169845176.969344.292070@l53g2000cwa.googlegroups.com>
On 26 Jan., 21:59, "rgb" <rbiel...@i1.net> wrote:
> On Jan 26, 6:41 am, "Joe" <Johannes.Labi...@gmail.com> wrote:
>
>
>
> > Hello,
>
> > I have set the variable special-display-buffer-names to
> > (("*SQL*" (width . 139) ))))
> > .
> > Whenever I create a "*SQL*" buffer, it is displayed in a new frame as
> > it should be.
> > The only problem is that if something is happening in the mini-buffer
> > that creates a (temporary) window, like completion, the buffer
> > *Completions* is displayed in a different frame.
> > For instance, if I do find-file and press tab to get the file
> > completions list, it is displayed in another (existing) frame instead
> > of splitting the window temporary as it is done for other windows.
>
> > I tried to set special-display-buffer-names to
> > (("*SQL*" (width . 139) (unsplittable . nil))))
> > but it had no effect.
>
> > It should not act different for *Completions* in the special-displayed
> > buffer from *Completions* of a function issued in a normal buffer.
> > How can I do that?
> I'ts hard to say if this is a bug or there is a good reason but
> special-display-popup-frame creates the frame like this:
>
> (make-frame (append args special-display-frame-alist))
>
> If unsplitable is non-nil in special-display-frame-alist it will
> appear after your nil version - which gets supplied from args.
>
> Making the frame happens in C code so I can't be sure
> exactly how and why but the conflict between the 2 sources
> of parameters is almost certainly the cause.
> If you're curious, look at x_get_arg, otherwise
> you might try reporting it as a bug and see what they say.
Interesting answer. Does that mean, there is currently no possibility
for me to change the behaviour?
I understand this: setting unsplittable is ignored because of the
way the special frame is created.
In that case it is definately a bug.
No, I am not THAT curious. :-)
next prev parent reply other threads:[~2007-01-29 12:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 12:41 Splitting window displayed in special frame Joe
2007-01-26 20:59 ` rgb
2007-01-29 12:28 ` Joe [this message]
2007-01-29 14:39 ` rgb
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=1170073684.920901.20240@h3g2000cwc.googlegroups.com \
--to=johannes.labisch@gmail.com \
--cc=help-gnu-emacs@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.
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).