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: Mon, 24 May 2010 22:45:56 -0400 Message-ID: References: <4BF79AE5.6010007@gmx.at> <4BF91C9B.4020404@gmx.at> <4BF97C61.9050606@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1274755583 5582 80.91.229.12 (25 May 2010 02:46:23 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 25 May 2010 02:46:23 +0000 (UTC) Cc: emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 25 04:46:09 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 1OGk9f-0007rp-0L for ged-emacs-devel@m.gmane.org; Tue, 25 May 2010 04:46:07 +0200 Original-Received: from localhost ([127.0.0.1]:53611 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGk9e-0000Bb-CZ for ged-emacs-devel@m.gmane.org; Mon, 24 May 2010 22:46:06 -0400 Original-Received: from [140.186.70.92] (port=51834 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OGk9Z-0000AZ-2w for emacs-devel@gnu.org; Mon, 24 May 2010 22:46:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OGk9X-0000ld-9z for emacs-devel@gnu.org; Mon, 24 May 2010 22:46:00 -0400 Original-Received: from mail-yw0-f194.google.com ([209.85.211.194]:53960) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OGk9X-0000l0-6Z for emacs-devel@gnu.org; Mon, 24 May 2010 22:45:59 -0400 Original-Received: by ywh32 with SMTP id 32so2774901ywh.5 for ; Mon, 24 May 2010 19:45:57 -0700 (PDT) Original-Received: by 10.151.92.3 with SMTP id u3mr7536370ybl.218.1274755557018; Mon, 24 May 2010 19:45:57 -0700 (PDT) Original-Received: by 10.151.143.21 with HTTP; Mon, 24 May 2010 19:45:56 -0700 (PDT) In-Reply-To: <4BF97C61.9050606@gmx.at> X-Google-Sender-Auth: 9ZKWXIEjRHiRkdDHS0vmu_iio14 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:125221 Archived-At: On Sun, May 23, 2010 at 3:05 PM, martin rudalics wrote: > How would this relate to the issue at hand? If I understand what is at issue, any code (lisp-side or C-side) that interacts with buffer state has to set buffers modified (unless the ``strongly'' vodoo is in effect) whenever changes take place. This is (or may sometimes be) one aspect of a series of actions which need occur when a buffer is in a state of frob'dness. > Because I studied the code. Wow! So you are sure. > the current buffer is not shown in any window. Why should anyone want > to do that? No clue. Maybe they haven't studied the code. :) > martin /s_P\