From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Problems with whole buffer Custom functions. Date: Mon, 23 Jan 2006 03:47:07 +0200 Organization: JURTA Message-ID: <8764obk6ul.fsf@jurta.org> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1137983994 28117 80.91.229.2 (23 Jan 2006 02:39:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 23 Jan 2006 02:39:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 23 03:39:52 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F0rcU-0004oS-7y for ged-emacs-devel@m.gmane.org; Mon, 23 Jan 2006 03:39:50 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F0rf6-0000Zd-7g for ged-emacs-devel@m.gmane.org; Sun, 22 Jan 2006 21:42:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F0rep-0000Vz-RO for emacs-devel@gnu.org; Sun, 22 Jan 2006 21:42:15 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F0reo-0000Ub-8U for emacs-devel@gnu.org; Sun, 22 Jan 2006 21:42:15 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F0ren-0000Tt-RP for emacs-devel@gnu.org; Sun, 22 Jan 2006 21:42:13 -0500 Original-Received: from [194.126.101.111] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1F0rjS-0002xv-Tl for emacs-devel@gnu.org; Sun, 22 Jan 2006 21:47:03 -0500 Original-Received: from mail.neti.ee (80-235-32-219-dsl.mus.estpak.ee [80.235.32.219]) by Relayhost1.neti.ee (Postfix) with ESMTP id 2E580CB80; Mon, 23 Jan 2006 04:39:28 +0200 (EET) Original-To: "Drew Adams" In-Reply-To: (Drew Adams's message of "Sun, 22 Jan 2006 13:28:46 -0800") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee 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:49429 Archived-At: > I assume you mean that there would be a separate M-n/M-p history for > each value (editable field). I meant a history mechanism like is used in modern GUI applications, e.g. in Firefox typing M-down in an editable field opens a list of values previously entered into the same field. There is also Emacs-like completion that filters out values based on the contents of the field. > What would be the extent (limit) of the proposed history list(s)? Would > the limit be the current Emacs session? the current access to Customize > for that field? Or would the histories be persistent (e.g. via > savehist.el)? Adding a new history variable with a list (or alist with one sublist per option/field or per widget class) of previously entered values would automatically allow saving it with savehist.el or desktop.el. > What would constitute an entry in such a history list: would it be each > individual edit (a la undo) or each value that the user sets or saves > (via Set for Current Session or Save...)? I think preserving each value that the user sets or saves is more useful than preserving mini changes undoable with the ordinary undo. This would work exactly like history lists work in the minibuffer: in the minibuffer history list gets updated after exiting with RET, in editable fields this could be done after activating the field. -- Juri Linkov http://www.jurta.org/emacs/