Re: [O] Blank lines after headline and before :PROPERTIES: etc

[Charles Millar]

Hi,

On 11/09/2016 06:28 PM, Nicolas Goaziou wrote:

Hello,

Charles Millar  writes:


Is it stated anywhere in the Org manual that blank lines are not
allowed after headlines or certain other elements.

Quoting (info "(org) Property syntax"),

   Properties are key-value pairs. When they are associated with a single
   entry or with a tree they need to be inserted into a special drawer
   (@pxref{Drawers}) with the name @code{PROPERTIES}, which has to be
   located right below a headline, and its planning line
   (@pxref{Deadlines and scheduling}) when applicable.

Improvements are welcome.

Also, see

   http://orgmode.org/worg/dev/org-syntax.html

Eventually,

   M-x org-lint

should report such issue. Actually, it doesn't, but I fixed it so it
will eventually report it.

Regards,


Thank you.

Re: [O] Blank lines after headline and before :PROPERTIES: etc

[Nicolas Goaziou]

Hello,

Charles Millar  writes:

> Is it stated anywhere in the Org manual that blank lines are not
> allowed after headlines or certain other elements.

Quoting (info "(org) Property syntax"),

  Properties are key-value pairs. When they are associated with a single
  entry or with a tree they need to be inserted into a special drawer
  (@pxref{Drawers}) with the name @code{PROPERTIES}, which has to be
  located right below a headline, and its planning line
  (@pxref{Deadlines and scheduling}) when applicable.

Improvements are welcome.

Also, see

  http://orgmode.org/worg/dev/org-syntax.html

Eventually,

  M-x org-lint

should report such issue. Actually, it doesn't, but I fixed it so it
will eventually report it.

Regards,

-- 
Nicolas Goaziou

[O] Blank lines after headline and before :PROPERTIES: etc

[Charles Millar]

Hi,

I am not  a programmer, coder, whatever, and realize that many of you 
are used to inferring certain conditions by examples given in manuals, etc.


Is it stated anywhere in the Org manual that blank lines are not allowed 
after headlines or certain other elements. If not, could such 
"enlightenment" be added to the manual? As an example,


* This is a headline
:PROPERTIES:
:EXPORT_FILE_NAME: /path/to/exported/file
:END:

works as expected whereas

* This is a headline

:PROPERTIES:
:EXPORT_FILE_NAME: /path/to/exported/file
:END:

exports to a file with the buffer name.

(The above sometimes occur when I kill and yank the properties block.

Another example would be the necessity that a table immediately follow 
all elements that are used to format and generate a table.


Charlie Millar