From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: mb-pos.el (was: Minibuffer default values list) Date: Sun, 02 Dec 2007 16:27:17 -0500 Message-ID: References: <87zlycuhrd.fsf@jurta.org> <87hckbecc0.fsf@jurta.org> <87prygxtot.fsf@jurta.org> <87hcjjkrgy.fsf@jurta.org> <87ir3u9r5s.fsf@jurta.org> <87myt3zk65.fsf@jurta.org> <87y7cmh026.fsf_-_@jurta.org> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: ger.gmane.org 1196631063 15213 80.91.229.12 (2 Dec 2007 21:31:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 2 Dec 2007 21:31:03 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 02 22:31:11 2007 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 1IywP6-0002WE-VJ for ged-emacs-devel@m.gmane.org; Sun, 02 Dec 2007 22:31:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IywOq-0001hM-Fg for ged-emacs-devel@m.gmane.org; Sun, 02 Dec 2007 16:30:52 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IywLQ-0007H5-Vf for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IywLP-0007GK-47 for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IywLO-0007GE-Uv for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:18 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IywLO-0002oF-Ft for emacs-devel@gnu.org; Sun, 02 Dec 2007 16:27:18 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1IywLN-0006eu-OU; Sun, 02 Dec 2007 16:27:17 -0500 In-reply-to: <87y7cmh026.fsf_-_@jurta.org> (message from Juri Linkov on Sun, 25 Nov 2007 17:18:48 +0200) X-detected-kernel: by monty-python.gnu.org: 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:84506 Archived-At: The reason I added a new hook `goto-history-element-pre-hook' is to add later another symmetric hook `goto-history-element-post-hook' necessary for implementing another feature: with the recent improvements in the minibuffer functionality it became essential for the user to know the current minibuffer position in the history list or in the "future" values list. I don't understand what that refers to. Could you explain? If we want both kinds of hooks, we should make each of them work the right way, than make them artificially parallel if that is bad. The "pre-hook" should be a single function, not a hook, and ideally should only run when trying to move into the future, for the reasons I gave.