From: "rgb" <rbielaws@i1.net>
Subject: Re: dedicated frames
Date: 10 Jan 2007 06:42:08 -0800 [thread overview]
Message-ID: <1168440128.297662.237650@i56g2000hsf.googlegroups.com> (raw)
In-Reply-To: <mailman.2895.1168353667.2155.help-gnu-emacs@gnu.org>
Kevin Rodgers wrote:
> rgb wrote:
> > Has someone written a version of next-buffer that doesn't
> > display buffers that are already displayed in dedicated frames?
> >
> > It appears to me to be terribly difficult to tell if a given buffer
> > happens to be associated with a dedicated window or frame.
>
> How about:
>
> (defun get-buffer-dedicated-window (buffer &optional all-frames)
> "Return a dedicated window displaying BUFFER, or nil if none.
> BUFFER can be a buffer or a buffer name.
> ALL-FRAMES determines which frames are considered; see `walk-windows'."
> (catch 'window
> (mapc (lambda (window)
> (when (or (window-dedicated-p window)
> (frame-parameter (window-frame window) 'unsplittable))
> (throw 'window window)))
> (get-buffer-window-list buffer nil all-frames))
> nil))
You make it look easy.
Thanks.
Exactly what I needed.
prev parent reply other threads:[~2007-01-10 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 14:15 dedicated frames rgb
2007-01-09 14:40 ` Kevin Rodgers
[not found] ` <mailman.2895.1168353667.2155.help-gnu-emacs@gnu.org>
2007-01-10 14:42 ` rgb [this message]
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=1168440128.297662.237650@i56g2000hsf.googlegroups.com \
--to=rbielaws@i1.net \
/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).