emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Christopher M. Miles" <numbchild@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Rationale for org-directory (any?)
Date: Tue, 19 Feb 2019 20:48:46 +0800	[thread overview]
Message-ID: <87ef849c5t.fsf@gmail.com> (raw)
In-Reply-To: <CAELgYhdzqMtt4jF0mWrbW3S3xmidQby=dU5YWbKF6VFfOnCCVQ@mail.gmail.com>


I use it for dynamic folder sync, I can use it different machine, just
change the ~org-directory~ variable. I use this variable in many place
to concatenate a whole path.

Carlos Pita <carlosjosepita@gmail.com> writes:

> Hi all,
>
> I often wonder if the way org-directory is currently used has any
> sense or is just a historical artifact.
>
> I mean, when I list my refile targets and agenda files I have to
> specify full paths, which isn't very convenient. But if instead of a
> list I provide a file listing the paths, then the items in this list
> are taken to be relative to org-directory. Also, capture targets are
> relative to this variable. The result is a mix of relative and
> absolute paths in my init.el that makes me turn everything absolute in
> order to keep it sane.
>
> Why does it work that way? Is it because some paths are resolved
> relative to the current directory (unless they are configured as
> absolute paths) while others don't?
>
> Thanks!


-- 
[ stardiviner ]
       I try to make every word tell the meaning what I want to express.

       Blog: https://stardiviner.github.io/
       IRC(freenode): stardiviner, Matrix: stardiviner
       GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
      

      reply	other threads:[~2019-02-19 12:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-19  0:03 Rationale for org-directory (any?) Carlos Pita
2019-02-19 12:48 ` Christopher M. Miles [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=87ef849c5t.fsf@gmail.com \
    --to=numbchild@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).