From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Chong Yidong" Newsgroups: gmane.emacs.devel Subject: Re: require-hard-newlines to use newline Date: Fri, 11 Mar 2005 10:08:20 -0500 (EST) Message-ID: <3886.220.255.169.59.1110553700.squirrel@www.stupidchicken.com> References: <1483.220.255.172.231.1109730379.squirrel@www.stupidchicken.com> <200503020302.j2232fR21722@raven.dms.auburn.edu> <2750.220.255.172.231.1109734015.squirrel@www.stupidchicken.com> <1415.220.255.169.59.1109818150.squirrel@www.stupidchicken.com> <1404.220.255.169.59.1109889146.squirrel@www.stupidchicken.com> <200503040033.j240XD022473@raven.dms.auburn.edu> <50554.203.116.59.23.1109897782.squirrel@www.stupidchicken.com> <200503080005.j2805Kg28696@raven.dms.auburn.edu> <2451.220.255.169.59.1110299961.squirrel@www.stupidchicken.com> <2518.220.255.169.59.1110532203.squirrel@www.stupidchicken.com> <3222 NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1110554424 25573 80.91.229.2 (11 Mar 2005 15:20:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 Mar 2005 15:20:24 +0000 (UTC) Cc: emacs-devel@gnu.org, Stefan Monnier , rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 11 16:20:23 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D9lpH-0007su-Eq for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2005 16:13:19 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9m4N-0008Nz-Et for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2005 10:28:55 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D9m1x-0006hI-5r for emacs-devel@gnu.org; Fri, 11 Mar 2005 10:26:25 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D9m1r-0006c1-PQ for emacs-devel@gnu.org; Fri, 11 Mar 2005 10:26:23 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9m1p-0006aW-MM for emacs-devel@gnu.org; Fri, 11 Mar 2005 10:26:17 -0500 Original-Received: from [64.21.80.18] (helo=shark.dnsvelocity.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D9lkg-0004jB-NS; Fri, 11 Mar 2005 10:08:34 -0500 Original-Received: from stupidch by shark.dnsvelocity.com with local (Exim 4.44) id 1D9lkS-0000Am-II; Fri, 11 Mar 2005 10:08:20 -0500 Original-Received: from 220.255.169.59 ([220.255.169.59]) (SquirrelMail authenticated user cyd@stupidchicken.com) by www.stupidchicken.com with HTTP; Fri, 11 Mar 2005 10:08:20 -0500 (EST) In-Reply-To: Original-To: "Kim F. Storm" User-Agent: SquirrelMail/1.4.4 X-Priority: 3 (Normal) Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - shark.dnsvelocity.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [32675 33085] / [47 12] X-AntiAbuse: Sender Address Domain - stupidchicken.com X-Source: /usr/local/cpanel/3rdparty/bin/php X-Source-Args: /usr/local/cpanel/3rdparty/bin/php /usr/local/cpanel/base/3rdparty/squirrelmail/src/compose.php X-Source-Dir: :/base/3rdparty/squirrelmail/src 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34474 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34474 >> I think it's usually important to keep the property that killing doesn't >> modify the buffer's text (when used in copy-as-kill), so rather than >> having before-kill-functions modify the buffer's text just before it's >> put in the kill-ring, it would be more convenient to make it return the >> string, i.e. use it as a replacement for buffer-substring. > > I like the idea, but returning a value from a hook is rather > inconvenient -- if there are multiple functions on the hook, which > value should you use eventually? Another possibility is not to use a hook at all, e.g.: (defvar kill-filters nil "List of functions for converting a string before it is killed. Each function should accept a single argument, a string, and return a string. Whenever a string is killed, it is passed as an argument to the first function in the list, and the return value of each function is passed as the argument to the next. The final return value is the string that is actually put in the kill ring and passed to `interprogram-cut-function'.")