From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Helmut Eller Newsgroups: gmane.emacs.devel Subject: Re: help-window-select and info-lookup-symbol Date: Sun, 26 Jul 2009 14:30:25 +0200 Message-ID: References: <4A6439A9.6080406@gmx.at> <4A65C23E.3010801@gmx.at> <4A65CCD6.7060505@gmx.at> <4A66E5DB.6090007@gmx.at> <4A6C2991.8070908@gmx.at> <4A6C3751.5050501@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1248611464 26087 80.91.229.12 (26 Jul 2009 12:31:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 26 Jul 2009 12:31:04 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 26 14:30:57 2009 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.50) id 1MV2sS-00046B-0b for ged-emacs-devel@m.gmane.org; Sun, 26 Jul 2009 14:30:56 +0200 Original-Received: from localhost ([127.0.0.1]:38325 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MV2sR-0001O8-CN for ged-emacs-devel@m.gmane.org; Sun, 26 Jul 2009 08:30:55 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MV2sL-0001Mg-8A for emacs-devel@gnu.org; Sun, 26 Jul 2009 08:30:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MV2sF-0001EL-Uc for emacs-devel@gnu.org; Sun, 26 Jul 2009 08:30:48 -0400 Original-Received: from [199.232.76.173] (port=45639 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MV2sF-0001E9-Py for emacs-devel@gnu.org; Sun, 26 Jul 2009 08:30:43 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:55847 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MV2sF-0002HQ-CW for emacs-devel@gnu.org; Sun, 26 Jul 2009 08:30:43 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1MV2s8-0003az-GK for emacs-devel@gnu.org; Sun, 26 Jul 2009 12:30:36 +0000 Original-Received: from dial-180077.pool.broadband44.net ([212.46.180.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Jul 2009 12:30:36 +0000 Original-Received: from eller.helmut by dial-180077.pool.broadband44.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 26 Jul 2009 12:30:36 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 27 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dial-180077.pool.broadband44.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:L8jAv1gvFu0VPpAuWa1LdyC5MhI= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:113160 Archived-At: * martin rudalics [2009-07-26 13:00+0200] writes: >> I was thinking that a new function or macro would delete the >> buffer-local variable before displaying the buffer, something like >> with-help-window. display-buffer would be called in the process but >> display-buffer would know nothing about the buffer-local variable. > > The functions that could safely decide whether a buffer-local-variable > shall be deleted is the "any function calling `display-buffer' but the > help/info type ones". It's impossible to enumerate them all because > someone might add a new one tomorrow. I think we aren't talking with each other. If there is a (single) function to initialize help buffers, let's call it display-help-buffer, then there is exactly one function to enumerate. The callers of display-help-buffer don't count. > What could be done is provide a variable `do-not-wipe-out-old-value' > which is normally nil but the help/info type functions bind to t around > their `display-buffer' calls. And `display-buffer' wouldn't wipe out > the old value if that variable is t. display-buffer doesn't need to know what display-help-buffer does with buffer-local variables. Actually, display-buffer is already complicated enough that it would be better to keep that separated. Helmut