From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 16115@debbugs.gnu.org
Subject: bug#16115: 24.3.50; doc string of `display-buffer-in-side-window' - there is no SIDE arg
Date: Thu, 12 Dec 2013 11:50:42 -0800 (PST) [thread overview]
Message-ID: <23c0d954-512b-424f-af95-c4b5af6d1cd8@default> (raw)
In-Reply-To: <52A9FBDA.6050207@gmx.at>
> >> `display-buffer-below-selected' or something similar might be the
> >> answer. Side windows serve a completely different purpose.
> >
> > Sorry, I don't understand. The requester wanted the buffer to pop up on
> > the right, not below. And AFAICT the code I proposed does that. Can
> > you elaborate?
>
> If it makes a "side window", the effect is that the new window will be
> permanent unless explicitly deleted. Does the requester want that?
Dunno. I don't even know what a "permanent" window is. When you do
`C-x 3' is the new window permanent?
> > What is the right way to pop to a buffer in a window to the right? IOW,
> > the request was to get the effect of `C-x 3' but with the chosen buffer,
> > not the same buffer, in the new window on the right.
>
> If the frame is wide enough, `display-buffer-below-selected' will
> display it on the right of the selected window, otherwise below. This
> can be tuned via `split-height-/width-threshold'.
Apparently the OP would like the behavior to be similar to what `C-x 3'
does. Is that what `display-buffer-below-selected' always does? Perhaps
you'd like to post an answer to him directly on StackOverflow.
Of if not, I can transfer any answer you provide here to him there.
But I would just be an uninformed middleman, as I'm no authority on
`display-buffer-below-selected' or `split-height-/width-threshold',
to put it mildly.
next prev parent reply other threads:[~2013-12-12 19:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:59 bug#16115: 24.3.50; doc string of `display-buffer-in-side-window' - there is no SIDE arg Drew Adams
2013-12-11 17:55 ` martin rudalics
2013-12-11 18:57 ` Drew Adams
2013-12-11 19:01 ` Drew Adams
2013-12-12 10:14 ` martin rudalics
2013-12-12 16:18 ` Drew Adams
2013-12-12 18:09 ` martin rudalics
2013-12-12 19:50 ` Drew Adams [this message]
2013-12-14 11:22 ` martin rudalics
2013-12-13 21:54 ` Juri Linkov
2013-12-14 11:23 ` martin rudalics
2013-12-14 16:20 ` Drew Adams
2013-12-14 17:17 ` martin rudalics
2013-12-14 17:16 ` martin rudalics
2013-12-15 19:56 ` Juri Linkov
2013-12-16 10:10 ` martin rudalics
2013-12-16 20:19 ` Juri Linkov
2013-12-17 17:31 ` martin rudalics
2013-12-11 23:54 ` Juri Linkov
2013-12-12 10:15 ` martin rudalics
2013-12-12 18:25 ` Stefan Monnier
2013-12-13 10:13 ` martin rudalics
2013-12-13 10:56 ` Eli Zaretskii
2013-12-14 11:23 ` martin rudalics
2013-12-14 12:09 ` Eli Zaretskii
2013-12-14 13:45 ` martin rudalics
2013-12-14 14:06 ` Eli Zaretskii
2013-12-13 1:18 ` Juri Linkov
2013-12-13 10:13 ` 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
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=23c0d954-512b-424f-af95-c4b5af6d1cd8@default \
--to=drew.adams@oracle.com \
--cc=16115@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).