all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
Cc: 'Emacs Devel' <emacs-devel@gnu.org>
Subject: Re: lru-window, window--try-to-split-window, split-width-threshold
Date: Fri, 22 Aug 2008 19:02:29 +0200	[thread overview]
Message-ID: <48AEF125.4060506@gmx.at> (raw)
In-Reply-To: <001301c90470$cb24e1d0$0200a8c0@us.oracle.com>

 > `split-width-threshold' was apparently introduced recently. Depending on its
 > value, the lru-window can now get split horizontally to display *Completions*
 > during minibuffer input.
 >
 > I have code that changes the display of completions (columns, spacing etc.),
 > depending on the width *Completions* will have when it is displayed. Before it
 > is displayed, I obtain (window-width (get-lru-window)) and use that as the
 > assumed window width.
 >
 > This is no longer adequate, however, because the effective width might be, say,
 > half of that if the lru window gets split horizontally to display *Completions*.
 > And I can't simply use half of that width systematically, because there might be
 > no horizontal split, depending on `split-width-threshold'. I don't know a way to
 > know ahead of time whether a horizontal split will occur (without reproducing
 > all of the code/logic of `window--try-to-split-window' - checking for dedicated
 > windows etc.).

So you can't fill the buffer _after_ the splitting occurred?  Relying on
someone else to always choose the LRU window is not very clean in the
first place.

 > I tried this: (window--try-to-split-window (get-lru-window)), figuring that I
 > might as  well split the lru-window myself, if it is going to be split, so that
 > I can get its new width and use that.
 >
 > The problem with this is that once the split occurs the window that was split is
 > apparently no longer the lru window, so *Completions* gets displayed by
 > splitting yet another window.

Are you sure?  The LRU status changes with `select-window' IIUC.

 > If I have two full-frame-width windows (frame
 > split vertically), the effect is that both windows get split when *Completions*
 > is displayed (and then unsplit when *Completions* is finished).
 >
 > Any suggestions? What am I missing? Is there some way, say, after splitting the
 > lru window myself, that I can make it (or the new one) the lru again, so that
 > `display-buffer' will use it for *Completions*? IOW, is there a way to *set* the
 > lru window? Any help is welcome.

The only way I currently can think of is a dolist selecting all other
windows but the one you've chosen.

martin





  reply	other threads:[~2008-08-22 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 16:04 lru-window, window--try-to-split-window, split-width-threshold Drew Adams
2008-08-22 17:02 ` martin rudalics [this message]
2008-08-22 23:45   ` Drew Adams
2008-08-27 21:14     ` Stefan Monnier
2008-08-27 21:51       ` Drew Adams

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=48AEF125.4060506@gmx.at \
    --to=rudalics@gmx.at \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@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.