From: Carsten Dominik <carsten.dominik@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: syntax for blocks that the exporter should not render?
Date: Thu, 5 Sep 2013 13:57:19 +0200 [thread overview]
Message-ID: <3C681BE5-05DA-41A9-8277-7180063D2642@gmail.com> (raw)
In-Reply-To: <20130905114303.GB2392@kuru.dyndns-at-home.com>
On Sep 5, 2013, at 1:43 PM, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> Hi Carsten,
>
> On Thu, Sep 05, 2013 at 01:27:57PM +0200, Carsten Dominik wrote:
>>
>> On Sep 5, 2013, at 12:09 PM, Nicolas Goaziou <n.goaziou@gmail.com> wrote:
>>
>>>>> #+/home/matt/Matt_headshots/Matt Price/IMG_9367_.jpg
>>>>> http://2013.hackinghistory.ca/wp-content/uploads/2013/08/wpid-IMG_9367_2.jpg
>>>>
>>>> I don't think this is the right behavior, such lines should not be rendered.
>>>> Suvayu is right, with a space after the # they are treated as commendt, but I think
>>>> they should also be ignored with the plus.
>>>>
>>>> Nicolas, what is the reasoning behind rendering them?
>>>
>>> Because this isn't valid Org syntax, so it is treated as regular text
>>> (i.e. a paragraph). Something similar happens for unbalanced blocks:
>>
>> So in a way this is a "syntax error" message. :)
>>
>> OK, I get that point. Is that behaviour documented?
>
> I think it is more of a "I don't recognise this as special syntax; it
> must be text". In that case, I'm not sure what can be documented, one
> can have infinitely many text blurbs which look very similar to valid
> Org syntax but isn't.
>
> I have noticed quite a few posts on the list with this kind of
> misunderstanding. I think the confusion arises from thinking of special
> keywords like "#+options:", "#+attr_latex:", etc as comments. AFAIU,
> they are not. Lines starting with "#+" are possible keywords, whereas
> lines starting with "# " are comments.
Yes, and I just checked what we have in the manual:
Lines starting with zero or more whitespace characters followed by one
@samp{#} and a whitespace are treated as comments and will never be exported.
So indeed, the white space after the # is in the manual. I had forgotten about this.
>
> I can see how that can be confusing, but can't think of a way to resolve
> this. I have two possibilities in mind:
> 1. change "# " to something more distict like: "//", or "##",
> 2. use different faces for the two.
Another way to do this would be that every line starting with "#" (no space) is a comment line, except when it is starting with "#+". This was how I used to think about lines starting with "#". BUt it is not bad the way it is now - we just need to be aware and tell people - we just did.
Thanks
- Carsten
>
> (1) is probably too big a change, whereas (2) might be feasible.
>
> Nicolas will probably have a better feeling about what is more
> appropriate here.
>
> Cheers,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
next prev parent reply other threads:[~2013-09-05 11:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 15:32 syntax for blocks that the exporter should not render? Matt Price
2013-09-03 15:59 ` Jambunathan K
2013-09-05 12:09 ` Carsten Dominik
2013-09-04 17:40 ` Suvayu Ali
2013-09-05 3:34 ` Carsten Dominik
2013-09-05 10:09 ` Nicolas Goaziou
2013-09-05 11:27 ` Carsten Dominik
2013-09-05 11:43 ` Suvayu Ali
2013-09-05 11:57 ` Carsten Dominik [this message]
2013-09-05 14:51 ` Matt Price
2013-09-05 14:40 ` Matt Price
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C681BE5-05DA-41A9-8277-7180063D2642@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.