emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giacomo M <jackjackk@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Parent path for links
Date: Wed, 18 Feb 2015 17:55:13 -0800	[thread overview]
Message-ID: <CA+GKSr7SXcO_vnx6w-Vb5HrjGJhpwm9Kt0os8A_eRvLNwBS_6Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

Dear all,
I'm experimenting the following path structure:

1. ~/org/ is where I keep all my org files for organization purposes (e.g.
project.org contains all TODOs, notes, events, and links related to
"project") and is sync'd with a GIT server.

2. ~/working/project/ is where I keep all the non-organizational files
related to "project", which are potentially big and thus the folder is
saved on an external drive/Dropbox.

What happens is that in project.org I end up specifying a lot of links all
starting with ~/working/project/. This is useful as I can directly jump
from "organization" to "action", or just to switch in a quicker way across
project files.

I know there is an header arg (i.e. dir) for the path of code execution,
but I am not aware of anything similar for link referencing.

Would you have any suggestions for reducing the redundancy of a common
parent path for links in a subtree/file?

Thanks,

Giacomo

[-- Attachment #2: Type: text/html, Size: 1295 bytes --]

             reply	other threads:[~2015-02-19  1:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-19  1:55 Giacomo M [this message]
2015-02-19  5:17 ` Parent path for links Kyle Meyer
2015-02-19 23:49 ` Christian Wittern
2015-02-20  0:07   ` Kyle Meyer

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=CA+GKSr7SXcO_vnx6w-Vb5HrjGJhpwm9Kt0os8A_eRvLNwBS_6Q@mail.gmail.com \
    --to=jackjackk@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).