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: use and doc of function symbol properties [was: bug#11381: 23.3; isearch-search-and-update issue?] Date: Sat, 2 Jun 2012 09:57:45 -0700 Message-ID: <74A0397A1DA546A5BC5D4B07917D69C2@us.oracle.com> References: <4F9DC154.2000605@groveronline.com> <87ipgggtmw.fsf@mail.jurta.org> <878vhcc4nl.fsf@mail.jurta.org> <87vcjxdt5p.fsf@mail.jurta.org> <87vcjvwtxa.fsf@mail.jurta.org> <87r4ufhfmi.fsf@mail.jurta.org> <878vge3ri7.fsf@mail.jurta.org> <83pq9o1f9s.fsf@gnu.org> <09237F12532B42C381CDBC71FA09EA08@us.oracle.com> <83ehq419bn.fsf@gnu.org> <83d35o11fk.fsf@gnu.org> <838vg5d5k7.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1338656291 21303 80.91.229.3 (2 Jun 2012 16:58:11 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 2 Jun 2012 16:58:11 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: "'Eli Zaretskii'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 02 18:58:10 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SareR-0006n4-CQ for ged-emacs-devel@m.gmane.org; Sat, 02 Jun 2012 18:58:07 +0200 Original-Received: from localhost ([::1]:53230 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SareR-0004Mn-8s for ged-emacs-devel@m.gmane.org; Sat, 02 Jun 2012 12:58:07 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:45920) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SareP-0004Mh-79 for emacs-devel@gnu.org; Sat, 02 Jun 2012 12:58:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SareN-0006PP-JK for emacs-devel@gnu.org; Sat, 02 Jun 2012 12:58:04 -0400 Original-Received: from acsinet15.oracle.com ([141.146.126.227]:40845) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SareK-0006O8-Ao; Sat, 02 Jun 2012 12:58:00 -0400 Original-Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q52GvtdH014429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 2 Jun 2012 16:57:56 GMT Original-Received: from acsmt358.oracle.com (acsmt358.oracle.com [141.146.40.158]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q52GvsbG006787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Jun 2012 16:57:55 GMT Original-Received: from abhmt108.oracle.com (abhmt108.oracle.com [141.146.116.60]) by acsmt358.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q52Gvrkj026541; Sat, 2 Jun 2012 11:57:53 -0500 Original-Received: from dradamslap1 (/10.159.223.197) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 02 Jun 2012 09:57:53 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <838vg5d5k7.fsf@gnu.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Thread-Index: Ac1A32A7fwfRdigTR5CgBwT45VzHvwAAIwdg X-Source-IP: ucsinet21.oracle.com [156.151.31.93] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 1) X-Received-From: 141.146.126.227 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:150738 Archived-At: > Thanks. It would be nice to have all that in a doc string and/or a > manual near me, some time soon. +1 - that information/text or similar > > If the kill-ring entry to be yanked has the same text as > > the region, then first rotate the kill ring so that the > > yank will not be a no-op. > > This could use some more clarification. E.g., does it rotate the kill > ring until there's some entry that is different from the text in the > region, or just once? Just once. But it would no doubt be better to instead rotate through the list until we reach a non-identical entry (if there is one). > The "so the yank will not be a no-op" part is just the rationale, > so it should be worded as such (e.g., in parens). Agreed. But if improved as suggested then it would become the stop-rotating condition: "rotate the kill ring until the first kill is different" etc. In that case it need not be in parens. If there is no non-identical ring entry then punt (the yank operation becomes a no-op).