From xemacs-m  Wed Jul 16 09:10:35 1997
Received: from alphatech.com (erebus.alphatech.com [198.112.236.2])
	by xemacs.org (8.8.5/8.8.5) with SMTP id JAA13755
	for <xemacs-beta@xemacs.org>; Wed, 16 Jul 1997 09:10:33 -0500 (CDT)
Received: from venus.alphatech.com by alphatech.com (4.1/SMI-4.1)
	id AA22694; Wed, 16 Jul 97 09:59:31 EDT
Received: from pochacco.alphatech.com by venus.alphatech.com (4.1/SMI-4.1)
	id AA23678; Wed, 16 Jul 97 10:09:43 EDT
Received: by pochacco.alphatech.com (SMI-8.6/SMI-SVR4)
	id JAA27811; Wed, 16 Jul 1997 09:55:18 -0400
Sender: greg@pochacco.alphatech.com
From: greg@alphatech.com (Greg Klanderman)
To: karlheg+xemacs@inetarena.com (Karl M. Hegbloom)
Cc: XEmacs BETA <xemacs-beta@xemacs.org>
Subject: Re: [PATCH] `read-from-minibuffer' proposed change
References: <87g1tjqhrp.fsf@bittersweet.inetarena.com> <ug4t9wf7jj.fsf@pochacco.alphatech.com> <87g1tfvfmz.fsf@bittersweet.inetarena.com>
Reply-To: greg@alphatech.com
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Date: 16 Jul 1997 09:55:16 -0400
In-Reply-To: karlheg+xemacs@inetarena.com's message of 15 Jul 1997 20:29:24 -0700
Message-Id: <ug204zf6ez.fsf@pochacco.alphatech.com>
Lines: 40
X-Mailer: Gnus v5.4.37/XEmacs 19.15


Well, for more than a decade that's what I've been used to, and even
without that training of my fingers I believe the current behavior is
preferable.  When I'm searching back in the history, I know roughly
the order in which I did things so I can slow down when I see a
sequence of commands that I used shortly after the one I want.  
If you permute that order it screws up the context.  

Also, I imagine it would be rather irritating if emacs and tcsh
behaved differently wrt history.  Tcsh has 3 options:

   - always add the history item 
   - only add if not already in the history
   - only add if not the same as the previous history entry

None of these are the same as your proposed change - eg. the second
option does not add to the end and remove the previous matching entry.

Now that I look at the code, its actually the 3rd option that XEmacs
currently implements.  It might be nice to have all 4 available.  I
also don't see a history-max-length variable.

Greg


>>>>> "Karl" == Karl M Hegbloom <karlheg> writes:
Karl> 
>>>>> Greg Klanderman <greg@alphatech.com> writes:
Greg> Yuck - can you have a variable to toggle this behavior?
Karl> 
>>>>> "Karl" == Karl M Hegbloom <karlheg> writes:
Karl> [1 <text/plain; US-ASCII (7bit)>] 1997-07-13 Karl
Karl> M. Hegbloom <karlheg@inetarena.com>
Karl> 
Karl> * prim/minibuf.el: (read-from-minibuffer) Corrected
Karl> indentation, History lists don't contain dups anymore,
Karl> newest is put on top and removed from the cdr.
Karl> 
Karl>  Why do you want duplicates in the history list, Greg?
Karl> 

