From: Steven Haryanto <stevenharyanto@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: parsing fixed with section
Date: Thu, 11 Aug 2011 18:22:20 +0700 [thread overview]
Message-ID: <CAOivSP8rzCRyZZjvtcdhB1dme5cGV2F=izgSCcm8nCdnxw449g@mail.gmail.com> (raw)
In-Reply-To: <8762m4l1da.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1201 bytes --]
On Thu, Aug 11, 2011 at 4:54 PM, Nicolas Goaziou <n.goaziou@gmail.com>wrote:
> Hello,
>
> Steven Haryanto <stevenharyanto@gmail.com> 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.
> >
> > :<spc>line1
> > :<spc>
> > :<spc>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:
> >
> > :<spc>line1
> > :
> > :<spc>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.
>
>
Thanks for clearing this up, I've also updated the Org::Parser Perl module.
--
sh
[-- Attachment #2: Type: text/html, Size: 1829 bytes --]
prev parent reply other threads:[~2011-08-11 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-11 8:41 parsing fixed with section Steven Haryanto
2011-08-11 9:54 ` Nicolas Goaziou
2011-08-11 11:22 ` Steven Haryanto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOivSP8rzCRyZZjvtcdhB1dme5cGV2F=izgSCcm8nCdnxw449g@mail.gmail.com' \
--to=stevenharyanto@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).