From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#4748: 23.1; least recently used window - is it? Date: Sun, 18 Oct 2009 12:24:56 +0200 Message-ID: <4ADAECF8.7020200@gmx.at> References: <4D3E3BC7322D4F79988F82996F46CE28@us.oracle.com> Reply-To: martin rudalics , 4748@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1255863188 4023 80.91.229.12 (18 Oct 2009 10:53:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Oct 2009 10:53:08 +0000 (UTC) To: Drew Adams , 4748@emacsbugs.donarmstrong.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Oct 18 12:52:58 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MzTNi-0005Li-B8 for geb-bug-gnu-emacs@m.gmane.org; Sun, 18 Oct 2009 12:52:58 +0200 Original-Received: from localhost ([127.0.0.1]:40721 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzTNh-0002Cl-Km for geb-bug-gnu-emacs@m.gmane.org; Sun, 18 Oct 2009 06:52:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MzTII-0000Ys-HO for bug-gnu-emacs@gnu.org; Sun, 18 Oct 2009 06:47:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MzTIB-0000Vt-Fq for bug-gnu-emacs@gnu.org; Sun, 18 Oct 2009 06:47:19 -0400 Original-Received: from [199.232.76.173] (port=52240 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MzTIA-0000VR-Jc for bug-gnu-emacs@gnu.org; Sun, 18 Oct 2009 06:47:14 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:36321) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MzTIA-0003H1-2J for bug-gnu-emacs@gnu.org; Sun, 18 Oct 2009 06:47:14 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n9IAlBtn013757; Sun, 18 Oct 2009 03:47:12 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.14.3/8.14.3/Submit) id n9IAU8V2010896; Sun, 18 Oct 2009 03:30:08 -0700 Resent-Date: Sun, 18 Oct 2009 03:30:08 -0700 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: martin rudalics Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs 2Resent-Date: Sun, 18 Oct 2009 10:30:08 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 4748 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 4748-submit@emacsbugs.donarmstrong.com id=B4748.125586150510022 (code B ref 4748); Sun, 18 Oct 2009 10:30:08 +0000 Original-Received: (at 4748) by emacsbugs.donarmstrong.com; 18 Oct 2009 10:25:05 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with SMTP id n9IAP2Bl009928 for <4748@emacsbugs.donarmstrong.com>; Sun, 18 Oct 2009 03:25:04 -0700 Original-Received: (qmail invoked by alias); 18 Oct 2009 10:24:56 -0000 Original-Received: from 62-47-61-9.adsl.highway.telekom.at (EHLO [62.47.61.9]) [62.47.61.9] by mail.gmx.net (mp011) with SMTP; 18 Oct 2009 12:24:56 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1/rkqwzN9PrDgO07e1EwvSTKxMvYq9X/n8YEh2blN Jpz1YgBuXNtxPj User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <4D3E3BC7322D4F79988F82996F46CE28@us.oracle.com> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.64 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Resent-Date: Sun, 18 Oct 2009 06:47:19 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:32057 Archived-At: > Why shouldn't `get-lru-window' respect strictly what its name implies, > instead of having this exception that has *nothing* to do with recency > of usage? > > "If any full-width windows are present, it only considers these." > > Actually, it's not clear whether that description from the Elisp > manual refers only to the behavior of function `get-lru-window' or to > the definition of "least recently used window" itself. I'm guessing > it's both. (What is "it" in the sentence quoted?) "it" usually refers to the function or variable described. In the particular case "it" means `get-lru-window' and not the identity of the least recently used window per se. > So my question is really why the "least recently used window" isn't in > fact always the least recently used window? I suppose it's for historical reasons. `get-lru-window' should provide a window useful for displaying a buffer. On older displays full-width windows were probably more useful. > It seems clear that code cannot depend on this lru concept behaving > according to the chronology of window access. To control which window > is the lru means you must consider not only window-access chronology > but whether there are full-width windows etc. Yes. > What I would really like to be able to is to _set_ the least recently > used window - however Emacs wants to define that. You can do that by temporarily selecting all other windows ... > I would do that so > that code that then uses the least recently used window would use the > window I specified (by having set it as the least recently used). ... and you can't do that unless that window is full-width ... > That > might even be the selected window in some cases. ... in particular if there is only one window ;-) > Currently, it doesn't seem easy to predict or control which window is > used by things such as `pop-to-buffer' that try to use another window. > Being able to set the so-called lruw that such functions use would > make things a lot more straightforward. We can easily remove the FULL-WIDTH feature. But _who_ would be responsible for "touching" windows in order to make them LRU? martin