ellipsis request; also inconsistency followup

ellipsis request; also inconsistency followup

[Samuel Wales]

The logbook feature is fantastic.  Thank you, Carsten.

Although this is workable around by making trailing blank lines not
split the outline, it seems worth pointing out the inconsistency for
completeness.

With the same settings as before, with the latest git, c-c c-x p
ordered RET t RET creates a properties drawer without a blank line
after it.

However, calling org-todo to set a todo state with (setf
org-log-state-notes-into-drawer t) inserts a logbook drawer and then a
blank line.

Also, re ellipsis:

Is it possible in emacs to distinguish the org-ellipsis for nodes that
have only drawers from the org-ellipsis for nodes that have body text?
 That would be useful for ignoring nodes that only have properties or
clocks or state changes.

Re: ellipsis request; also inconsistency followup

[Carsten Dominik]

On Feb 14, 2009, at 1:45 AM, Samuel Wales wrote:

> The logbook feature is fantastic.  Thank you, Carsten.
>
> Although this is workable around by making trailing blank lines not
> split the outline, it seems worth pointing out the inconsistency for
> completeness.
>
> With the same settings as before, with the latest git, c-c c-x p
> ordered RET t RET creates a properties drawer without a blank line
> after it.
>
> However, calling org-todo to set a todo state with (setf
> org-log-state-notes-into-drawer t) inserts a logbook drawer and then a
> blank line.

I have it on my list of things to look into.

>
>
> Also, re ellipsis:
>
> Is it possible in emacs to distinguish the org-ellipsis for nodes that
> have only drawers from the org-ellipsis for nodes that have body text?
> That would be useful for ignoring nodes that only have properties or
> clocks or state changes.

As far as I know this is not possible in the framework that Emacs  
outlining
provides.

- Carsten