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 13:09:34 -0700 Message-ID: References: <85slnogtol.fsf@lola.goethe.zz> 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 1146859823 15066 80.91.229.2 (5 May 2006 20:10:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 5 May 2006 20:10:23 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 05 22:10:14 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 1Fc6cj-0003L7-DB for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 22:10:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fc6ci-0006Uq-Kj for ged-emacs-devel@m.gmane.org; Fri, 05 May 2006 16:10:00 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Fc6cV-0006TA-0L for emacs-devel@gnu.org; Fri, 05 May 2006 16:09:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Fc6cU-0006SG-83 for emacs-devel@gnu.org; Fri, 05 May 2006 16:09:46 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Fc6cT-0006Rf-NS for emacs-devel@gnu.org; Fri, 05 May 2006 16:09:45 -0400 Original-Received: from [148.87.113.118] (helo=rgminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1Fc6ch-0002CP-MJ for emacs-devel@gnu.org; Fri, 05 May 2006 16:09:59 -0400 Original-Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by rgminet01.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id k45K9hjm010143 for ; Fri, 5 May 2006 14:09:43 -0600 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 k45K9gkH031018 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Fri, 5 May 2006 14:09:42 -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: <85slnogtol.fsf@lola.goethe.zz> 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:53974 Archived-At: > > I am not interested in considering such a complex proposal. > > There is nothing complex about it (with the latest > add-to-history) version. > > I was talking about a different proposal, one involving > properties to control lengths. It was very complex. > > To be clear, was it this proposal from Juri: > > 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. I don't know how you gather this I don't gather anything. It was meant as a question: "Was it this proposal?" when Richard directly replied to the posting of yours ... containing the proposal: I think that for most uses of a history it makes no sense to keep duplicates. I'd vote for making the default value be t and letting those few modes where duplicates might make sense (e.g. shell-mode?) bind it to nil unless the user has explicitly specified otherwise. IOW the option values could be: nil - means never remove duplicates t (default) - means remove duplicates, but this can be overridden by a mode (e.g. shell-mode) non-nil, non-t - means always remove duplicates (never override) This would require code changes only for those few modes that want to override the default (t). Plus a change to the defcustom. Precisely why I asked RMS for clarification. You make me glad I did, because I suspect that you, too, might be confused in trying to interpret Richard's message. My proposal said nothing about "properties to control lengths", and I don't think it was very "complex". Juri's email was a reply to mine, and he did propose something fairly complex about controlling history-list lengths using symbol properties. Juri changed the subject to "a related feature" of his choice without changing the Subject line. In spite of Juri's mention of "a related feature", there is no real connection between the two proposals. RMS's reply (sent to me, you are correct) was not clear (to me). Richard has told me before that he pays little or no attention to the To: destination. I suspect that he perhaps hit Reply to my email but wrote his response to Juri's after reading it (!?). Otherwise, I don't understand his reply. Clarification welcome. I think things would be clearer if people used emacs-devel (only) in the To: field and cc'd any additional destinations (it would also be good if emacs-devel was the default To: value for a Reply). This is, I suspect, a good example of the confusion that can arise from 1) not paying attention to To: and 2) not explicitly referencing what you're talking about. #2 is more important than #1: be clear what you are referring to. This has been a long thread with multiple proposals. Richard: please clarify your position(s).