From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: MON KEY Newsgroups: gmane.emacs.devel Subject: Re: force-mode-line-update ALL argument Date: Sun, 23 May 2010 13:14:51 -0400 Message-ID: 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 X-Trace: dough.gmane.org 1274634908 7361 80.91.229.12 (23 May 2010 17:15:08 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 23 May 2010 17:15:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 23 19:15:07 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 1OGElW-0008Vg-Aw for ged-emacs-devel@m.gmane.org; Sun, 23 May 2010 19:15:06 +0200 Original-Received: from localhost ([127.0.0.1]:55609 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGElU-0002cZ-Vf for ged-emacs-devel@m.gmane.org; Sun, 23 May 2010 13:15:05 -0400 Original-Received: from [140.186.70.92] (port=59389 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGElM-0002bf-60 for emacs-devel@gnu.org; Sun, 23 May 2010 13:14:57 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OGElK-0003zE-AR for emacs-devel@gnu.org; Sun, 23 May 2010 13:14:56 -0400 Original-Received: from mail-yw0-f178.google.com ([209.85.211.178]:50116) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OGElK-0003z1-84 for emacs-devel@gnu.org; Sun, 23 May 2010 13:14:54 -0400 Original-Received: by ywh8 with SMTP id 8so1840469ywh.6 for ; Sun, 23 May 2010 10:14:51 -0700 (PDT) Original-Received: by 10.150.56.14 with SMTP id e14mr5647936yba.339.1274634891856; Sun, 23 May 2010 10:14:51 -0700 (PDT) Original-Received: by 10.151.143.21 with HTTP; Sun, 23 May 2010 10:14:51 -0700 (PDT) In-Reply-To: <4BF91C9B.4020404@gmx.at> X-Google-Sender-Auth: BneuF7cE79DrM580JQ_flycAda4 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:125137 Archived-At: On Sun, May 23, 2010 at 8:16 AM, martin rudalics wrote: > 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. > It does affect what? The volatile state of transient changedness with regards intermediate states of display. > set_buffer_temp doesn't enter here. >> {...} > record_buffer doesn't enter here either. Seriously, how can you be sure? > 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. Maybe you are the Obeah man willing to oust these demon zombies. There is much voodo in the (re)display engine. How powerful is your juju? May I suggest you keep some chickens handy for sacrificial offerings :) > Thanks, martin /s_P\