From: James Harkins <jamshark70@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: TODO + org-mobile-push vs. org-store-link
Date: Tue, 04 Sep 2012 13:07:13 +0800 [thread overview]
Message-ID: <874nnepe9q.wl%jamshark70@dewdrop-world.net> (raw)
In-Reply-To: <87627upf17.wl%jamshark70@dewdrop-world.net>
At Tue, 04 Sep 2012 12:50:44 +0800,
James Harkins wrote:
> Now, if I also want to link to this item (why?*), I would hit C-c l on the TODO headline, which tries to assign another SHA id. Then I get a mess.
>
> ~~~
> * TODO A headline to link
>
> :PROPERTIES:
> :ID: 331b4df1-3974-4c1b-aa67-a519af8b7b3d
> :END:
> :END: ** A subheading
> ~~~
>
> (I'm not sure if the ID is the same before or after C-c l.)
>
> So we have two :END: markers and -- *worse* -- the subheading has been moved up to the previous line, where it is no longer a subheading.
>
> I'm quite sure I did org-mobile-push before storing the link. I suspect org-store-link may not be checking sufficiently for an existing ID, and trying to put the ID into a place where it expects to find no :PROPERTIES: block (but there is one).
Hm, wait, that's not quite right. The beamer trees are in a separate file specifically because I did not want to push them onto my phone.
So I'm not sure exactly what happened.
There's a link in one of my org-agenda/mobile files to the top heading of the beamer file. I did do an org-mobile-push in the morning. But I just confirmed with a quick test that mobile-push does NOT greedily scan through any org buffers and add IDs to TODOs, schedules. So the errant :PROPERTIES: block (which I assume is the source of the extra :END:) didn't come from there... but it did come from somewhere.
Ah... another dim memory... I copied this content out of a file that *is* pushed. Probably those headings acquired IDs when they were part of the other file, and I didn't delete the properties in the new file.
But I still can't reproduce it with a simple file :( so I don't know quite what causes it, only that something screwy happened when storing a link to a heading that had already been property-ified.
hjh
--
James Harkins /// dewdrop world
jamshark70@dewdrop-world.net
http://www.dewdrop-world.net
"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal." -- Whitman
blog: http://www.dewdrop-world.net/words
audio clips: http://www.dewdrop-world.net/audio
more audio: http://soundcloud.com/dewdrop_world/tracks
prev parent reply other threads:[~2012-09-04 5:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 4:50 TODO + org-mobile-push vs. org-store-link James Harkins
2012-09-04 5:07 ` James Harkins [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nnepe9q.wl%jamshark70@dewdrop-world.net \
--to=jamshark70@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).