I'm sorry to report, but org-mobile still occasionally misfiles entries. 
Usually it's fine, but something weird happened this morning.

The last commit in my active (local) branch is 307cc6d6, Oct 15 2014, 
"Merge branch 'master' of orgmode.org:org-mode." So it's safe to say I'm 
quite well up-to-date.

I'm trying to reconstruct the sequence of events in my mind. Unfortunately, 
I don't have the from-mobile.org entry, because org-mobile deletes entries 
that have been processed. I think this is what happened:

1. I had an entry under [Lessons > 1st-year > Electronic > Sessions > TODO 
1st-year electronic 07] with the heading "HW:..." and some notes on the 
homework I was going to assign.

2. After the lesson, I edited this entry, renaming it "HW" and putting some 
additional notes in the payload.

3. Sometime before syncing, I changed the entry's TODO state to DONE.

4. When I synced, this entry appeared as a second-level item under [Dates]. 
I believe the point in that buffer was located on the last second-level 
item within Dates.

If I've got this right, then I guess what happened is that org-mobile-pull 
couldn't find "TODO 1st-year electronic 07" (because its TODO state had 
changed). Instead of reporting this as an error, it just stuck the new 
content in wherever. So I guess that's a couple of possible bugs:

a. When trying to locate an item based on a slash-delimited path, should it 
ignore TODO state and priority? Or should it fail?

b. If the location for an edit can't be found, don't pretend that it was 
found. That should be an error for the user to resolve by manually getting 
the new content out of from-mobile.org.

hjh

-- 
You received this message because you are subscribed to the Google Groups 
"mobileorg-android" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mobileorg-android.
For more options, visit https://groups.google.com/d/optout.

Reply via email to