[Orgmode] Re: minor option conflict

[Samuel Wales]

On Thu, Feb 12, 2009 at 01:53, Carsten Dominik <address@hidden> wrote:
> Why don't you simply set the variable `org-cycle-separator-lines'
> to its default value 2?

That works OK, and so does 0 (although ISTR for some reason that when
I first wrote the bug it didn't, although I don't know why that would
be as the code probably didn't change).

I think what must have happened is that I wrote the
bug as a quick and minor note on consistency when I was able to, then
conflated it with consistency with CLOSED
 minor option conflict report as a minor consistency thing
 There are various subtleties, like what happens when you move or
refile the entry with the trailing blanks, etc., but they are mostly
only important for automation that I don't do and perhaps others don't
do either.  So I guess it was too low a priorirty of a bug report --
there are ...

>
> This would mean that 2 empty lines are needed to get an empty
> line in the collapsed outline.
>
> I guess I could fix the problem you are describing, but there
> are more cases where Org automatically inserts stuff and maybe
> (depending on exact context) an empty line.
>
>> I also like Wanrong's idea of putting state changes in drawers  to
>> keep syntax separate from the body.
>
> I will look into this.
>
> - Carsten
>
>



-- 
Myalgic encephalomyelitis denialists are causing massive suffering and
25-years-early death by grossly corrupting science.
http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm