org-mobile-push and agenda IDs

org-mobile-push and agenda IDs

[Tom Tobin]

I recently upgraded my org-mode, and found that org-mobile-push
started to litter my org files with property drawers.  I finally
figured out how to turn these off (via
org-mobile-force-id-on-agenda-items), but the org-mode manual makes it
sound like they're necessary for the proper operation of MobileOrg
[1].  I have a ton of TODO items on my agenda, and I really don't want
property drawers all over my files (even if they're collapsed to a
single line); is there a better way to handle this in my case?

[1] <http://orgmode.org/manual/Pushing-to-MobileOrg.html> "While
creating the agendas, Org-mode will force1 an ID property on all
entries referenced by the agendas, so that these entries can be
uniquely identified if MobileOrg flags them for further action."

Re: org-mobile-push and agenda IDs

[Richard Moreland]

Hi Tom,

They are not required, but they eliminate potential problems that may
be encountered with the simple path-based node identification scheme.
The risk level is fairly low, and you should be fine with the force
option disabled.

The path-based id scheme fails if you have this:

* Parent
** A name
*** A node you didn't edit
** A name
*** A node you edited

The path to the node you edited is ambiguous and will cause a sync
conflict.  As long as you keep this in mind, you should be fine.

Hope this helps,
Richard


On Fri, Jan 15, 2010 at 12:02 PM, Tom Tobin <korpios@korpios.com> wrote:
> I recently upgraded my org-mode, and found that org-mobile-push
> started to litter my org files with property drawers.  I finally
> figured out how to turn these off (via
> org-mobile-force-id-on-agenda-items), but the org-mode manual makes it
> sound like they're necessary for the proper operation of MobileOrg
> [1].  I have a ton of TODO items on my agenda, and I really don't want
> property drawers all over my files (even if they're collapsed to a
> single line); is there a better way to handle this in my case?
>
> [1] <http://orgmode.org/manual/Pushing-to-MobileOrg.html> "While
> creating the agendas, Org-mode will force1 an ID property on all
> entries referenced by the agendas, so that these entries can be
> uniquely identified if MobileOrg flags them for further action."
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>

Re: org-mobile-push and agenda IDs

[Tom Tobin]

On Fri, Jan 15, 2010 at 12:12 PM, Richard Moreland <rlm@ncogni.to> wrote:
> Hi Tom,
>
> They are not required, but they eliminate potential problems that may
> be encountered with the simple path-based node identification scheme.
> The risk level is fairly low, and you should be fine with the force
> option disabled.
>
> The path-based id scheme fails if you have this:
>
> * Parent
> ** A name
> *** A node you didn't edit
> ** A name
> *** A node you edited
>
> The path to the node you edited is ambiguous and will cause a sync
> conflict.  As long as you keep this in mind, you should be fine.

So as long as I don't duplicate names in the same level, I should be
okay?  I don't see myself ever doing that anyway, so that seems
harmless enough.

Aside — there's no way to cycle the visibility of drawers to
*completely* hidden, is there?  I wouldn't mind the property drawers
as much if I could completely ignore their existence during routine
org-mode editing.  :-)