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: shouldn't `delete-blank-lines' treat form-feed as whitespace? Date: Wed, 03 Mar 2010 23:28:36 -0500 Message-ID: References: <4CB6D99021EF440EAB10FFDB2740FE8B@us.oracle.com> <87mxyptfyp.fsf@mail.jurta.org> <45AE884B58464C6F8533A686709EB31B@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1267769323 16586 80.91.229.12 (5 Mar 2010 06:08:43 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 5 Mar 2010 06:08:43 +0000 (UTC) Cc: 'Juri Linkov' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 05 07:08:17 2010 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NnQY8-0007tq-8O for ged-emacs-devel@m.gmane.org; Fri, 05 Mar 2010 06:58:12 +0100 Original-Received: from localhost ([127.0.0.1]:34721 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NnPE5-0003MS-N5 for ged-emacs-devel@m.gmane.org; Thu, 04 Mar 2010 23:33:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NnPDz-0003MD-I4 for emacs-devel@gnu.org; Thu, 04 Mar 2010 23:33:19 -0500 Original-Received: from [140.186.70.92] (port=53211 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NnPDu-0003KQ-MT for emacs-devel@gnu.org; Thu, 04 Mar 2010 23:33:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NnPDq-0000VT-4Z for emacs-devel@gnu.org; Thu, 04 Mar 2010 23:33:14 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:11942 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NnPDq-0000VO-0Y for emacs-devel@gnu.org; Thu, 04 Mar 2010 23:33:10 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAEsYkEtMCo4j/2dsb2JhbACbQ3S3HoR9BIMXh3I X-IronPort-AV: E=Sophos;i="4.49,585,1262581200"; d="scan'208";a="57568317" Original-Received: from 76-10-142-35.dsl.teksavvy.com (HELO ceviche.home) ([76.10.142.35]) by ironport2-out.pppoe.ca with ESMTP; 04 Mar 2010 23:33:09 -0500 Original-Received: by ceviche.home (Postfix, from userid 20848) id C4A43B44D5; Wed, 3 Mar 2010 23:28:36 -0500 (EST) In-Reply-To: <45AE884B58464C6F8533A686709EB31B@us.oracle.com> (Drew Adams's message of "Wed, 3 Mar 2010 11:54:09 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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:121651 Archived-At: > Yes, I suppose the notion of whitespace is mode-dependent, and > [:space:] should capture that notion appropriately for each > mode. Good point. It's actually even more delicate than that. There's basically the notion of "blank" for characters that have no associated semantics in the corresponding language. And then there's the notion of "blank" for characters which *users* consider as having no semantics. Usually the first includes form-feed and other such things and is best handled by forward-comment. Usually the second only includes \s, \t, \n, \r but doesn't include form-feed. syntax-tables usually use the `space' syntax for \s, \t, form-feed, \r, and sometimes \n (but not always because of newline-terminated comments). So using the `space' syntax is usually not a good choice because of the \n issue and because it doesn't handle comments. Stefan