Bastien <b...@altern.org> writes:

> Actually, I'm thinking of another solution:
>
> - keep one-line option/environment keywords uppercase
>   #+NAME
>   #+HTML
>   #+TITLE
>   #+...
>
> - use lowercase for multi-lines environments keywords
>   #+begin_ascii
>   #+begin_html
>   #+results
>
> This is the only good criterium I can think of, and that
> way people using easy templates will not be surprised to
> see #+begin_xxx in the manual.

I tried this and I find the lowercase #+begin_xxx really
not readable enough in the manual.   So I use #+RESULTS:
and explained this convention in the manual.

-- 
 Bastien

Reply via email to