From: Martin Alsinet <martin@alsinet.com.ar>
To: Sharon Kimble <boudiccas@skimble.plus.com>, emacs-orgmode@gnu.org
Subject: Re: enhancement - cross-reference to another file?
Date: Sat, 14 Oct 2017 15:22:45 +0000 [thread overview]
Message-ID: <CABUJmkDBapFhAeZ6QA3a+aTvAU=eNXGq-gwwrj9r+Kz9pG8zvg@mail.gmail.com> (raw)
In-Reply-To: <87zi8tvqy3.fsf@skimble.plus.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Hello Sharon:
On Sat, Oct 14, 2017 at 7:45 AM Sharon Kimble <boudiccas@skimble.plus.com>
wrote:
>
> Is it possible to cross reference to another org-mode file in a
> different directory?
>
Yes, it is possible, you have to use the following syntax:
[[file:/path/to/other/org/file.org:* heading][My other org file]]
You can check the manual for the different link types and examples
http://orgmode.org/manual/External-links.html
> Example - cooking 1 has an entry for Mayonnaise, so can file 2 have an
> entry for mayonnaise but cross-referenced to cooking 1?
>
> --8<---------------cut here---------------start------------->8---
> id1=cooking1.org
>
> ** Mayonnaise
> [[*Mayonnaise][Mayonnaise]]
> blurb and blah
> --8<---------------cut here---------------end--------------->8---
>
> --8<---------------cut here---------------start------------->8---
> id2=cooking2.org
>
> ** Mayonnaise 3
>
> See also [[*id1:Mayonnaise][Mayonnaise]] and also [[*Mayonnaise
> 2][Mayonnaise 2]]
>
> --8<---------------cut here---------------end--------------->8---
>
>
In your example, the references would be written:
See also [[file:cooking1.org:** Mayonnaise][this mayonnaise recipe]] and
also [[*Mayonnaise 2][this other one]]
[-- Attachment #2: Type: text/html, Size: 2128 bytes --]
prev parent reply other threads:[~2017-10-14 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 12:45 enhancement - cross-reference to another file? Sharon Kimble
2017-10-14 15:22 ` Martin Alsinet [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABUJmkDBapFhAeZ6QA3a+aTvAU=eNXGq-gwwrj9r+Kz9pG8zvg@mail.gmail.com' \
--to=martin@alsinet.com.ar \
--cc=boudiccas@skimble.plus.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.