Re: Question about cycle mode and sorting/refiling

[Keith Swartz <gnu@oneroad.com>]

Hi Carsten,

The changes in the latest git version appear to have fixed these 
problems. Thanks.

However, I've discovered a new problem, which is probably not related. 
If you refile one or more items to the same subtree, it wreaks havoc. In 
some cases, the item or entire subtree is apparently lost. It's late, 
but I'll try to submit a small test case soon.

Thanks,
Keith

Carsten Dominik wrote:
>
> On Jun 4, 2009, at 8:20 PM, Keith Swartz wrote:
>
>> A few weeks back, I asked about hooks when refiling and/or sorting, 
>> and am happy to report that these are working great for me ... /if/ I 
>> refile one item at a time. I'm unable to figure out why if I try to 
>> refile multiple items in a /region/, it doesn't have the same behavior.
>>
>> Here are my hook definitions:
>>
>> (setq org-after-refile-insert-hook
>>     '(lambda() (org-up-heading-safe) (org-sort-entries-or-items nil ?p))
>> (setq org-after-sorting-entries-or-items-hook
>>     '(lambda() (org-cycle) (org-cycle))
>
> There seem to be parenthesis missing from these definitions, but I
> am assuming that you do have them in your real setup.
>
>>
>> If I position the cursor on an item and refile it, it: a) resorts the 
>> destination tree by priority, and b) restores the visibility to 
>> folded, the way I like it.
>>
>> HOWEVER, if I select multiple items in a folded subtree (with 
>> transient-mark-mode on; I'm using emacs 22.3), and reflie those, it 
>> does not always work. I can't figure out the rules for when it does, 
>> and when it doesn't, but when it does work, that appears to be an 
>> abnormality.
>>
>> What happens in this scenario is that it will refile the items, but 
>> it will neither resort the destination folder (even though the hook 
>> is being called),
>
> I believe this problem is now solved, I needed to deactive the region
> before calling this hook.  Please upgrade to the latest git release
> and try again.
>
>>  the visibility of the refiled nodes is not reset. Plus, the 
>> visibility of all items below the current point in the /originating/ 
>> folder is also changed to children.
>
> I am not sure if I understand correctly.  Do you mean the outline node
> where the refiled items *originate* changes visibility?  I cannot
> reproduce this.  Maybe you can try with the latest version and then,
> if the problem persists, come up with a test case.
>
> HTH
>
> - Carsten
>
>