From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: parsing fixed with section Date: Thu, 11 Aug 2011 11:54:25 +0200 Message-ID: <8762m4l1da.fsf@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:39613) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrRyd-0002cV-72 for emacs-orgmode@gnu.org; Thu, 11 Aug 2011 05:55:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QrRyY-0004Wk-VY for emacs-orgmode@gnu.org; Thu, 11 Aug 2011 05:54:59 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:35167) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QrRyY-0004Wg-RD for emacs-orgmode@gnu.org; Thu, 11 Aug 2011 05:54:54 -0400 Received: by wyi11 with SMTP id 11so1533158wyi.0 for ; Thu, 11 Aug 2011 02:54:53 -0700 (PDT) In-Reply-To: (Steven Haryanto's message of "Thu, 11 Aug 2011 15:41:41 +0700") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Steven Haryanto Cc: emacs-orgmode@gnu.org Hello, Steven Haryanto writes: > As I understand it, a fixed width section (BTW, is "fixed width section" the > official term for this?) Yes. > is defined as a line which is started by zero or more spaces, and then > a colon, *and then a space*, and then zero or more characters. > > :line1 > : > :line3 > > But many editors (Emacs including) likes to trim trailing spaces, As far as I know, this doesn't happen in Emacs, unless you specify it explicitly (i.e. in some hook). > so when the file is saved, the second line loses its space: > > :line1 > : > :line3 > > Should the second line be parsed as a fixed width section too or not? I'd say yes. You may have noticed that exporters already treat that line as fixed-width section anyway. But this is inconsistent with fontification (and indentation) in the buffer. I've pushed a commit to fix this inconsistency in master. Thanks for pointing this out. Regards, -- Nicolas Goaziou