From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: should search ring contain duplicates? Date: Fri, 5 May 2006 19:05:12 -0700 Message-ID: References: <87k6906oq4.fsf@jurta.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1146881149 1417 80.91.229.2 (6 May 2006 02:05:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 6 May 2006 02:05:49 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 06 04:05:47 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 1FcCAu-00085w-AF for ged-emacs-devel@m.gmane.org; Sat, 06 May 2006 04:05:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FcCAt-00015a-RR for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 22:05:39 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FcCAi-00015U-4f for emacs-devel@gnu.org; Fri, 05 May 2006 22:05:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FcCAf-000159-RW for emacs-devel@gnu.org; Fri, 05 May 2006 22:05:27 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FcCAf-000152-OY for emacs-devel@gnu.org; Fri, 05 May 2006 22:05:25 -0400 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1FcCAx-0001e8-5H for emacs-devel@gnu.org; Fri, 05 May 2006 22:05:43 -0400 Original-Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k4625NDH031129 for ; Fri, 5 May 2006 21:05:24 -0500 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-82-144.vpn.oracle.com [141.144.82.144]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k4625M2Y011246 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 5 May 2006 20:05:23 -0600 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <87k6906oq4.fsf@jurta.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807 Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE 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:53992 Archived-At: > A related feature that specifies the maximum length of > the history list > uses the `history-length' _property_ of the history list _symbol_ > to override the default value of the _variable_ `history-length' > for a particular history list. Exactly the same thing could be > implemented for `history-delete-duplicates', i.e. the property > `history-delete-duplicates' would override its default value > for a particular history list. The first part of this paragraph is not a proposal. It describes how `history-length' already uses the property of the history symbol. The Lisp code of `add-to-history' Kim submitted to this list, demonstrates very simple implementation of this functionality as: (or (get history-var 'history-length) history-length) I proposed to do the same for history-delete-duplicates, i.e. to use the following condition in `add-to-history': (or (get history-var 'history-delete-duplicates) history-delete-duplicates) So my proposal is not very complex, and I don't think Richard replied to my email. Well, as I said, I do not understand what Richard was referring to - that's why I asked. He mentioned a proposal "involving properties to control lengths. It was very complex." Your proposal involves properties to control lengths. Mine doesn't have anything to do with that, and I don't see anything else in the thread about that. I can't speak to the complexity of your proposal, but mine seems trivial to implement, understand, use, and document. I guess we'll just have to wait until Richard decides to enlightens us as to what he meant.