From: Drew Adams <drew.adams@oracle.com>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: 21305@debbugs.gnu.org
Subject: bug#21305: 25.0.50; `get-buffer-window-list' doc - what order?
Date: Fri, 21 Aug 2015 09:32:16 -0700 (PDT) [thread overview]
Message-ID: <50fbb71c-8a6d-45b4-a467-a31bcc73ac09@default> (raw)
In-Reply-To: <1b17a036-c525-4dbc-84fa-cc8adc2b6488@default>
Sorry for drifting from the bug, but is something like this useful
generally? I will use it, but I'm thinking others might also.
(defun mru-window-for-buffer (buffer &optional minibuf all-frames)
"Return the most recently used window for BUFFER.
Optional args MINIBUF and ALL-FRAMES are as for `get-buffer-window-list'."
(let* ((wins (get-buffer-window-list buffer minibuf all-frames))
(mru-win (car wins)))
(dolist (win (cdr wins))
(unless (time-less-p win mru-win) (setq mru-win win)))
mru-win))
Similary, `lru-window-for-buffer'.
next prev parent reply other threads:[~2015-08-21 16:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<089f48ed-6ce9-4753-abcf-3f86d43a278e@default>
[not found] ` <<83vbc8iyut.fsf@gnu.org>
2015-08-21 13:21 ` bug#21305: 25.0.50; `get-buffer-window-list' doc - what order? Drew Adams
2015-08-21 13:51 ` Eli Zaretskii
2015-08-21 15:28 ` martin rudalics
2015-08-21 15:30 ` Drew Adams
2015-08-21 15:58 ` martin rudalics
2015-08-20 17:49 ` Drew Adams
2015-08-21 12:56 ` Eli Zaretskii
2015-08-21 16:12 ` Drew Adams
2015-08-21 16:32 ` Drew Adams [this message]
2015-08-21 17:42 ` Drew Adams
2015-08-22 6:40 ` martin rudalics
2015-08-22 14:31 ` Drew Adams
2015-08-22 16:01 ` Stefan Monnier
2015-08-22 17:23 ` Drew Adams
2015-08-22 17:30 ` Eli Zaretskii
2015-08-23 13:33 ` martin rudalics
2015-08-21 16:00 ` Drew Adams
[not found] <<5430f5a7-2939-4f96-8c6c-3e820ffcfd6b@default>
[not found] ` <<83oai0iwbc.fsf@gnu.org>
2015-08-21 15:08 ` Drew Adams
2015-08-21 15:21 ` Eli Zaretskii
[not found] ` <<55D74386.6010708@gmx.at>
[not found] ` <<7036da11-d296-45a9-b6ee-d7b68830927e@default>
[not found] ` <<55D74AA3.1070202@gmx.at>
[not found] ` <<1b17a036-c525-4dbc-84fa-cc8adc2b6488@default>
[not found] ` <<50fbb71c-8a6d-45b4-a467-a31bcc73ac09@default>
[not found] ` <<a18faa5f-a31e-49c2-809b-64fdd40fa273@default>
[not found] ` <<55D8195A.4040804@gmx.at>
[not found] ` <<9aa1dcd7-1781-41aa-bf47-7b280b26da1e@default>
[not found] ` <<jwvoahziaao.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <<cf171405-a9e3-4312-b456-ff68352d4052@default>
[not found] ` <<83a8tji626.fsf@gnu.org>
2015-08-22 19:01 ` Drew Adams
2015-08-23 22:34 ` Stefan Monnier
[not found] <<870b6a90-e498-4ed9-9e41-d498edf33aec@default>
[not found] ` <<83mvxkis5t.fsf@gnu.org>
2015-08-21 15:28 ` Drew Adams
2015-08-21 18:28 ` Eli Zaretskii
[not found] ` <<b7c7a7fe-1e8a-4add-8585-1698e16348cf@default>
[not found] ` <<83lhd4ijh3.fsf@gnu.org>
2015-08-21 19:18 ` 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
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=50fbb71c-8a6d-45b4-a467-a31bcc73ac09@default \
--to=drew.adams@oracle.com \
--cc=21305@debbugs.gnu.org \
--cc=eliz@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).