From: Manish <firstname.lastname@example.org>
To: Carsten Dominik <email@example.com>
Subject: Re: Attachment feature - Can I have custom directories?
Date: Mon, 19 Jan 2009 16:52:11 +0530 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Mon, Jan 19, 2009 at 1:57 PM, Carsten Dominik wrote:
> On Jan 11, 2009, at 2:47 AM, Jason Jackson wrote:
>> There are many times where I would like to associate an org-mode item with
>> a specific directory of my choosing for attachment directory.
>> Such that, C-c C-a f would open for example ~/docs/project1
>> and C-c C-a o would open the file inside
>> Of course, I still like the existing functionality of generating random
>> directory names too.
>> Can org-mode do this?
> You know, I think this could be very useful, so I have
> implemented it. Along with an idea I wanted to have in
> myself: Using the same directory to an entire subtree, so
> that a project may use a single attachment directory.
> If you get the new git version, `C-c C-a s' will allow to
> select a directory of your choice.
> And `C-c C-a i' will mark an entry as a parent whose children
> will inherit the attachment directory.
This is great! Thank you.
I attached an existing directory to a subtree. When I tried to open
an attachment, it offered me all the files available in the directory.
If it's supposed to offer all the files in the attachment directory
then what is the significance of ATTACHMENTS? I was under impression
that it will offer only the files explicitly listed/marked as
attachments (may be it can offer all files when called with a prefix.)
next prev parent reply other threads:[~2009-01-19 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 1:47 Attachment feature - Can I have custom directories? Jason Jackson
2009-01-19 8:27 ` Carsten Dominik
2009-01-19 11:22 ` Manish [this message]
2009-01-19 11:40 ` Carsten Dominik
2009-01-19 11:57 ` Manish
2009-01-19 13:34 ` Carsten Dominik
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 \
* 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).