[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Orgmode] reloading causes visibility bug requiring restart

From: Carsten Dominik
Subject: Re: [Orgmode] reloading causes visibility bug requiring restart
Date: Tue, 7 Apr 2009 22:10:23 +0200

I have fixed org-reload, it will now only reload files
that actually have been loaded before.  Also, the reloading
will now also cover any files from the contrib/lisp directory.

- Carsten

On Apr 6, 2009, at 12:57 PM, Carsten Dominik wrote:

I believe I know what s causing this.  Reloading Org actually
does load *all* of org, including, for example,
org-inlinetask.  I think that this is what is causing the problems.

That will mean that org-reload needs fixing, and maybe that there is something wrong with the inline tasks. If more people could test the inline tasks, maybe some bug will be identified.

I don't use org-cycle-include-plain-lists, so it ma be that the interaction of inline tasks with plain list cycling causes some of the problems.

- Carsten

On Apr 6, 2009, at 7:56 AM, Manish wrote:

On Apr 5, 2009, at 8:18 PM, Samuel Wales wrote:

I can't do the typing to formally document this, so I will just ask if
others experience it. If not, it will take a while.

Repeatably, with the latest git, emacs 22 cocoa, reloading org causes folding/visibility/cycling problems that are not fixable by reverting.
Only restarting emacs fixes it.

The problems are weird enough that it should be obvious if you try it.
Seemingly random plain list items being the only visible part, etc.
There is no cycling state in which all is shown, either from bob or
from headline.

On Mon, Apr 6, 2009 at 12:57 AM, Carsten Dominik wrote:
Hi Samuel,

is this something that started recently, or that you have observed over a
longer period of time?

I also experienced those cycling issues in past two days (with no change in Org config, only git updates) but I have since Emacs a couple of times (for unrelated reasons.) I will try gather more details if I see it again.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]