emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Viktor Rosenfeld <listuser36@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Per-file attachment directories
Date: Wed, 21 Sep 2011 11:49:39 +0200	[thread overview]
Message-ID: <20110921094939.GA1018@client199-150.wlan.hu-berlin.de> (raw)

Hi everybody,

so far I've only used one org file, but it's getting unwieldy and I've
decided to split it up.

I'd also like to split up my attachment directory to reduce clutter.
For example, if I have two org files "personal.org" and "work.org" I
would like attachments to go into automatically created directories
below "~/org/data/personal" and "~/org/data/work". If a file has no
custom attachment directory specified, attachments should be created
below a default path (same as now).

Is this possible?


             reply	other threads:[~2011-09-21  9:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  9:49 Viktor Rosenfeld [this message]
2011-09-21 16:34 ` Per-file attachment directories Darlan Cavalcante Moreira
2011-09-21 18:29   ` Viktor Rosenfeld
2011-09-22  1:34     ` Darlan Cavalcante Moreira
2011-09-22  7:08       ` Nick Dokos
2011-09-22  9:47         ` Viktor Rosenfeld
2011-09-22  7:32       ` Viktor Rosenfeld

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:

  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=20110921094939.GA1018@client199-150.wlan.hu-berlin.de \
    --to=listuser36@googlemail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).