From: Oleh <ohwoeowho@gmail.com>
To: Xebar Saram <zeltakc@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: differnace between
Date: Tue, 25 Feb 2014 20:24:45 +0100 [thread overview]
Message-ID: <CAA01p3p31WZjHiSTaQegtRy-MsQ6nh_GMP0OU8EPCfXe-US=GQ@mail.gmail.com> (raw)
In-Reply-To: <CAOQHXPp0zcb+kZK+M+fCFQp95mbiaHei4c+qpjJ65TQujE6sNQ@mail.gmail.com>
> Hya all. i cant understand what the advantages of org-id links over internal
> ones?
> in both cases it uses a fixed path right? its not like if i move my org
> files to another PC with different paths then the links will all work? whats
> the use case scenario to use org-id over internal links?
>
As far as I understand, id links are unique, so you can have multiple
headings with same name, and move them about as much you like within
current file
or multiple files. You can't do that with plain links which are *very*
inflexible
and become stale fast.
Your scenario with another PC should also work, as org will search for
the needed id
across all known org files. So as long as the file you move across different PCs
is in the search path, the links will still work.
regards,
Oleh
prev parent reply other threads:[~2014-02-25 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 19:05 differnace between Xebar Saram
2014-02-25 19:24 ` Oleh [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='CAA01p3p31WZjHiSTaQegtRy-MsQ6nh_GMP0OU8EPCfXe-US=GQ@mail.gmail.com' \
--to=ohwoeowho@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=zeltakc@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).