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: Sun, 13 Mar 2005 22:42:30 -0500 (EST) Message-ID: <42708.203.116.59.23.1110771750.squirrel@203.116.59.23> 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 1110772439 10654 80.91.229.2 (14 Mar 2005 03:53:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 14 Mar 2005 03:53:59 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 14 04:53:58 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DAgeK-0008QE-Uf for ged-emacs-devel@m.gmane.org; Mon, 14 Mar 2005 04:53:49 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DAgtw-0002Lb-Fn for ged-emacs-devel@m.gmane.org; Sun, 13 Mar 2005 23:09:56 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DAgsE-00020G-PW for emacs-devel@gnu.org; Sun, 13 Mar 2005 23:08:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DAgs3-0001ux-29 for emacs-devel@gnu.org; Sun, 13 Mar 2005 23:08:04 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DAgs0-0001tS-2d for emacs-devel@gnu.org; Sun, 13 Mar 2005 23:07:56 -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 1DAgTg-0007MS-8w; Sun, 13 Mar 2005 22:42:48 -0500 Original-Received: from stupidch by shark.dnsvelocity.com with local (Exim 4.44) id 1DAgTO-0005jv-Qu; Sun, 13 Mar 2005 22:42:30 -0500 Original-Received: from 203.116.59.23 ([203.116.59.23]) (SquirrelMail authenticated user cyd@stupidchicken.com); by www.stupidchicken.com with HTTP; Sun, 13 Mar 2005 22:42:30 -0500 (EST) In-Reply-To: Original-To: rms@gnu.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a 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:34564 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34564 > Anyway, what about my other suggestion? The suggestion to make > longlines.el use after-change-functions to discover all new text inserted > in the buffer, and do longlines processing on that text? I am already making longlines.el use post-command-hook to process text yanked *into* the longlines buffer. But I need a separate mechanism to process text yanked *out of* the buffer, and neither post-command-hook nor after-change-functions are suitable for this. By the time the hook is called, the text has already been put into the kill ring and clipboard. > No, buffer-substring should not call them. That's why I said "a > variant of buffer-substring". Some places would call this new > variant, but some would continue to call the existing, ordinary > buffer-substring function. In that case, I don't think our ideas are so different. I'll alter my patch to implement the `kill-filters' variable, and make the appropriate functions use it before calling buffer-substring. So far, these functions are `kill-region', `copy-region-as-kill', and `copy-to-register'; are there others?