From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: require-hard-newlines to use newline Date: Fri, 11 Mar 2005 09:32:52 -0500 Message-ID: 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=us-ascii X-Trace: sea.gmane.org 1110551665 16048 80.91.229.2 (11 Mar 2005 14:34:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 Mar 2005 14:34:25 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, "Kim F. Storm" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 11 15:34:24 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D9lDO-0002f2-PZ for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2005 15:34:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9lSU-0002Cm-G9 for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2005 09:49:46 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D9lRp-0001wM-3X for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:49:06 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D9lRk-0001sg-IF for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:49:02 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9lRk-0001sE-An for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:49:00 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D9lCD-0001T6-9a; Fri, 11 Mar 2005 09:32:57 -0500 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id C1328340011; Fri, 11 Mar 2005 09:32:56 -0500 (EST) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 6072E4AC28C; Fri, 11 Mar 2005 09:32:52 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 452F14BD52; Fri, 11 Mar 2005 09:32:52 -0500 (EST) Original-To: "Chong Yidong" In-Reply-To: <3222.220.255.169.59.1110546234.squirrel@www.stupidchicken.com> (Chong Yidong's message of "Fri, 11 Mar 2005 08:03:54 -0500 (EST)") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.821, requis 5, autolearn=not spam, AWL 0.08, BAYES_00 -4.90) 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:34471 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34471 > + (defvar before-kill-functions nil > + "List of functions called on the region before killing. > + This abnormal hook is run before `kill-region' and > + `copy-region-as-kill', with the beginning and end positions of > + the killed region as the arguments.") 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. Stefan