From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: force-mode-line-update ALL argument Date: Sun, 23 May 2010 21:05:05 +0200 Message-ID: <4BF97C61.9050606@gmx.at> References: <4BF79AE5.6010007@gmx.at> <4BF91C9B.4020404@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1274641522 27405 80.91.229.12 (23 May 2010 19:05:22 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 23 May 2010 19:05:22 +0000 (UTC) Cc: emacs-devel@gnu.org To: MON KEY Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 23 21:05:20 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OGGUC-0007pw-9R for ged-emacs-devel@m.gmane.org; Sun, 23 May 2010 21:05:20 +0200 Original-Received: from localhost ([127.0.0.1]:46520 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGGUB-00027N-CR for ged-emacs-devel@m.gmane.org; Sun, 23 May 2010 15:05:19 -0400 Original-Received: from [140.186.70.92] (port=59976 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGGU3-000262-On for emacs-devel@gnu.org; Sun, 23 May 2010 15:05:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OGGU2-0007TH-2W for emacs-devel@gnu.org; Sun, 23 May 2010 15:05:11 -0400 Original-Received: from mail.gmx.net ([213.165.64.20]:33609) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OGGU1-0007T1-MT for emacs-devel@gnu.org; Sun, 23 May 2010 15:05:10 -0400 Original-Received: (qmail invoked by alias); 23 May 2010 19:05:08 -0000 Original-Received: from 62-47-48-92.adsl.highway.telekom.at (EHLO [62.47.48.92]) [62.47.48.92] by mail.gmx.net (mp002) with SMTP; 23 May 2010 21:05:08 +0200 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+WMoVnk4qWUn3yjEJb4g6hqzB17G3qmlWNfq+78r 1z056z6kLRXw6T User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:125147 Archived-At: >> The entire idea is that `set-buffer' should not have an effect on the >> mode line, only `set-window-buffer' should. > > ,---- (documentation 'window-dedicated-p) > | Functions like `set-window-buffer' may change the buffer displayed > | by a window, unless that window is "strongly" dedicated to its > | buffer, that is the value returned by `window-dedicated-p' is t. > `---- > > IIRTC this says that `set-window-buffer' _should_ change display but > may not be depended upon to _always_ do so esp. when a window has > `strong' voodoo acting upon it. How would this relate to the issue at hand? >> set_buffer_temp doesn't enter here. >>> {...} >> record_buffer doesn't enter here either. > > Seriously, how can you be sure? Because I studied the code. >> in `force-mode-line-update' and the ALL argument has no effect. When >> {...} >> argument has been set. Now, usually the current buffer is shown in >> the selected window, so this went by unnoticed ever since that. > > I doubt it has gone unnoticed for 10+ years. More likely no one was > brave enough to assert that Fset_buffer_modified_p et al cover _all_ > cases. A "bug" occurs iff you call `force-mode-line-update' in a state where the current buffer is not shown in any window. Why should anyone want to do that? martin