From: Carsten Dominik <carsten.dominik@gmail.com>
To: Andreas Rottmann <a.rottmann@gmx.at>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Proper way to "link" external files into a project?
Date: Mon, 3 Aug 2009 06:33:44 +0200 [thread overview]
Message-ID: <3C7C4E28-99EB-4B36-A1D1-5330089DB9CE@gmail.com> (raw)
In-Reply-To: <871voh3crm.fsf@vir.lan>
On Jul 15, 2009, at 10:35 PM, Andreas Rottmann wrote:
> Sebastian Rose <sebastian_rose@gmx.de> writes:
>
>> Andreas Rottmann <a.rottmann@gmx.at> writes:
>>> Hi!
>>>
>>> I'd like to include several files into an org-mode project that live
>>> outside the project tree. I tried to just symlink them into the
>>> appropriate place into my project, and thought that might suffice
>>> to get
>>> them published correctly, but that doesn't work out, as org-mode
>>> doesn't
>>> consider the symlink's name, but the "true" filename; for example, I
>>> have this:
>>
>>
>> First of all: How about hardlinks?
>>
> I'd rather not use them in this case.
>
>>
>> Second:
>>
>> See
>> http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php#sec-7.1
>>
>> That shows how you can share files between projects, simply by
>> pulling
>> them in through a special export project.
>> I use this technique a lot. One advantage is that each project has a
>> complete set of files.
>> The drawbacks are minor for my use-case, but that might vary. But as
>> linking was enough, this approach should be fine.
>>
> Thanks! I'm now using this approach, and it works well. The only
> drawback for me is that I have to "pollute" the included projects' org
> files with a line like this:
>
> #+SETUPFILE: ~/.emacs.d/org-templates/level-2.org
IIUC, you don't need to do this. Since you are only linking to
these files, you can simply define a project component that will
make sure these files will be copied into the correct location.
Then use links with relative path, and this should do the trick.
The level-dependent setupfiles Sebastian describes in his tutorial
are for different purposes.
- Carsten
>
> Ideally, I'd like to have that information inferred, or at least
> external to the included projects, as they should not have to "know"
> at
> which location they are used. You don't know about a trick how to get
> around this? I'd also be willing to write some elisp to that end...
>
> Regards, Rotty
> --
> Andreas Rottmann -- <http://rotty.yi.org/>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2009-08-03 4:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:52 Proper way to "link" external files into a project? Andreas Rottmann
2009-07-14 23:58 ` Sebastian Rose
2009-07-15 20:35 ` Andreas Rottmann
2009-08-03 4:33 ` Carsten Dominik [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=3C7C4E28-99EB-4B36-A1D1-5330089DB9CE@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=a.rottmann@gmx.at \
--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).