From: Bernt Hansen <bernt@norang.ca>
To: "Emin.shopper Martinian.shopper" <emin.shopper@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Links break when you archive; what are work arounds?
Date: Thu, 13 May 2010 13:15:43 -0400 [thread overview]
Message-ID: <87wrv7en9c.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <AANLkTikXw9vw9rbzV8Q4cJ7bipiTqQPWNpMlcITqlLgL@mail.gmail.com> (Emin shopper Martinian shopper's message of "Thu\, 13 May 2010 13\:04\:58 -0400")
"Emin.shopper Martinian.shopper" <emin.shopper@gmail.com> writes:
> Thanks, that sounds like a good idea. But how do you use ID links? I
> see an option for descriptive links and literal links but not id
> links. I have org-mode version 6.34c, is that too old?
I'm not sure if that is too old but I don't think so. You need to
customize the variable 'org-modules' and enable org-id which generates
globally unique ids.
This automatically adds the property id entry when you create a link for
a task using 'org-id-get-create'
-Bernt
>
> Thanks,
> -Emin
>
> On Thu, May 13, 2010 at 10:14 AM, Bernt Hansen <bernt@norang.ca> wrote:
>> This works for me when I use id links.
>>
>> I created two tasks
>>
>> ,----[ todo.org ]
>> | * Test task
>> | * TODO Test target
>> `----
>>
>> Then linked test task to test target by doing C-c l on '* Test target'
>> and copying the link into the body of '* Test Task' with C-c C-l
>>
>> This gives me this
>>
>> ,----[ todo.org ]
>> | * Test link
>> | [[id:c517f8d3-9cf3-4d86-b92d-b544874ef0af][Test target]]
>> | * TODO Test target
>> | :PROPERTIES:
>> | :ID: c517f8d3-9cf3-4d86-b92d-b544874ef0af
>> | :END:
>> `----
next prev parent reply other threads:[~2010-05-13 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 11:24 Links break when you archive; what are work arounds? Emin.shopper Martinian.shopper
2010-05-13 14:14 ` Bernt Hansen
2010-05-13 17:04 ` Emin.shopper Martinian.shopper
2010-05-13 17:15 ` Bernt Hansen [this message]
2010-05-13 20:38 ` Emin.shopper Martinian.shopper
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=87wrv7en9c.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=emin.shopper@gmail.com \
/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).