Clarification on pulling/modifying files in mobileorg

[John Hendy via mobileorg-android]

After getting mobileorg setup and being back at work, I was finally able to
start using it. I was a bit surprised at the results of running
org-mobile-pull from emacs on the desktop. Just wanted clarification that
the way this works is that mobileorg puts everything in the file declared
in org-mobile-inbox-for-pull and then the user must manually refile these
to the correct place.

Is that accurate?

[mobileorg-android on behalf of Matthew Jones]

Pretty much... unless you are editing a node or adding a node to the
existing hierarchy (which is a fairly new feature in org-mode). Note that
we are just following the built-in org-mode mechanism for pulling in
additions and changes. It seems pretty absurd on the surface but
supporting something more advanced from both org-mode and MobileOrg is a
very tricky problem.


On Mon, Jan 14, 2013 at 1:33 PM, John Hendy via mobileorg-android <

Post by John Hendy via mobileorg-android
After getting mobileorg setup and being back at work, I was finally able
to start using it. I was a bit surprised at the results of running
org-mobile-pull from emacs on the desktop. Just wanted clarification that
the way this works is that mobileorg puts everything in the file declared
in org-mobile-inbox-for-pull and then the user must manually refile these
to the correct place.
Is that accurate?
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/FuvorvRARSIJ.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[mobileorg-android on behalf of John Hendy]

I'll have to play around with that. I thought even the new node added
to an existing file/headline (as in new node was level two) put things
into my inbox file vs. transferring to the file itself.

I really think taking advantage of the new org-sync git features that
resulted from the google summer of code would be amazing. Git itself
would be great and I know that's already in the issues as a feature
request; the org-sync bit just makes it nearly seamless to use org
with git and might side step some of these problems.


Thanks,
John

On Mon, Jan 14, 2013 at 12:36 PM, mobileorg-android on behalf of

Post by mobileorg-android on behalf of Matthew Jones
Pretty much... unless you are editing a node or adding a node to the
existing hierarchy (which is a fairly new feature in org-mode). Note that
we are just following the built-in org-mode mechanism for pulling in
additions and changes. It seems pretty absurd on the surface but supporting
something more advanced from both org-mode and MobileOrg is a very tricky
problem.
On Mon, Jan 14, 2013 at 1:33 PM, John Hendy via mobileorg-android

Post by John Hendy via mobileorg-android
After getting mobileorg setup and being back at work, I was finally able
to start using it. I was a bit surprised at the results of running
org-mobile-pull from emacs on the desktop. Just wanted clarification that
the way this works is that mobileorg puts everything in the file declared in
org-mobile-inbox-for-pull and then the user must manually refile these to
the correct place.
Is that accurate?
--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/FuvorvRARSIJ.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[mobileorg-android on behalf of Matthew Jones]

adding a node to an existing headline should file it under that headline
when you sync... is that not what you are seeing?

org-sync does sound great... but there's only so much time we have to
hammer out new features. If it's something you'd really like to see then
we'd certainly appreciate your help in implementing it.


On Mon, Jan 14, 2013 at 1:55 PM, mobileorg-android on behalf of John Hendy <

Post by mobileorg-android on behalf of John Hendy
I'll have to play around with that. I thought even the new node added
to an existing file/headline (as in new node was level two) put things
into my inbox file vs. transferring to the file itself.
I really think taking advantage of the new org-sync git features that
resulted from the google summer of code would be amazing. Git itself
would be great and I know that's already in the issues as a feature
request; the org-sync bit just makes it nearly seamless to use org
with git and might side step some of these problems.
Thanks,
John
On Mon, Jan 14, 2013 at 12:36 PM, mobileorg-android on behalf of

Post by mobileorg-android on behalf of Matthew Jones
Pretty much... unless you are editing a node or adding a node to the
existing hierarchy (which is a fairly new feature in org-mode). Note

that

Post by mobileorg-android on behalf of Matthew Jones
we are just following the built-in org-mode mechanism for pulling in
additions and changes. It seems pretty absurd on the surface but

supporting

Post by mobileorg-android on behalf of Matthew Jones
something more advanced from both org-mode and MobileOrg is a very tricky
problem.
On Mon, Jan 14, 2013 at 1:33 PM, John Hendy via mobileorg-android <

Post by John Hendy via mobileorg-android
After getting mobileorg setup and being back at work, I was finally able
to start using it. I was a bit surprised at the results of running
org-mobile-pull from emacs on the desktop. Just wanted clarification

that

Post by mobileorg-android on behalf of Matthew Jones

Post by John Hendy via mobileorg-android
the way this works is that mobileorg puts everything in the file

declared in

Post by mobileorg-android on behalf of Matthew Jones

Post by John Hendy via mobileorg-android
org-mobile-inbox-for-pull and then the user must manually refile these

to

Post by mobileorg-android on behalf of Matthew Jones

Post by John Hendy via mobileorg-android
the correct place.
Is that accurate?
--
You received this message because you are subscribed to the Google

Groups

Post by mobileorg-android on behalf of Matthew Jones

Post by John Hendy via mobileorg-android
"mobileorg-android" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/mobileorg-android/-/FuvorvRARSIJ.

.

Post by mobileorg-android on behalf of Matthew Jones

Post by John Hendy via mobileorg-android
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

--
You received this message because you are subscribed to the Google Groups
"mobileorg-android" group.
To unsubscribe from this group, send email to
For more options, visit this group at
http://groups.google.com/group/mobileorg-android?hl=en.

[mobileorg-android on behalf of hjh]

On Jan 15, 2013 2:57 AM, "mobileorg-android on behalf of Matthew Jones" <

Post by mobileorg-android on behalf of Matthew Jones
adding a node to an existing headline should file it under that headline

when you sync... is that not what you are seeing?

I can confirm, it *does* work like this much of the time. Sometimes, for an
as-yet-unknown reason, org (on the emacs side) incorrectly identifies the
location of the new node's parent and places the new node under what should
have been its grandparent. I have a TODO item to troubleshoot it;
unfortunately, org doesn't (yet?) have a feature to slow down the earth's
rotation just enough that I could finish the TODO.

It seems to be an org bug rather than MobileOrg. I've seen it for parent
nodes identified by olp (OutLine Path) and by org-id (the latter of which
really surprises me -- it must be finding the right location and then going
up a level? super weird).

hjh