From: Carsten Dominik <carsten.dominik@gmail.com>
To: Darlan Cavalcante Moreira <darcamo@gmail.com>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Feature Request: changes regarding attachments and subtasks
Date: Thu, 3 Sep 2009 08:51:22 +0200 [thread overview]
Message-ID: <8D067FFB-DC0E-41B9-937E-3811AA4AC037@gmail.com> (raw)
In-Reply-To: <1251923376.14927.123.camel@gtelw26.gtel.ufc.br>
On Sep 2, 2009, at 10:29 PM, Darlan Cavalcante Moreira wrote:
> Hello orgers,
>
> I have a task with several subtasks and some of them are associated
> with
> an external PDF file. Since in this case each PDF file exists only for
> the corresponding subtask, I think using attachments is a better
> option
> then storing the PDFs somewhere and using hyperlinks.
>
> If each subtask has its own directory everything is fine and using
> "C-c
> C-a o" on a subtask with only one PDF will open the PDF without
> further
> questions. However, I'd like to have all subtasks files stored in the
> same folder but still be able to reference only the specific subtask
> file.
>
> For instance, I have set the :ATTACH_DIR: property of the parent
> task to
> something such as "parent_task_files" and the :ATTACH_DIR_INHERIT:
> property to "t". Then in a "subtask1" I have added the file
> "file1" (using C-c C-a a) and in "subtask2" I have added the file
> "file2". Both of them were added to the folder
> "data/parent_task_files" (which is what I want) but no information
> (property) is added to the subtasks. Therefore, if I go to subtask1
> and
> try to open the file with "C-c C-a o" it will ask me each file to
> open:
> file1 or file2.
>
> My suggestion is that when I add a file to a subtask in this case it
> should add the property :Atachments: "filename" such that even if all
> files are stored in the same folder, only the files that I added to
> this
> subtask is associated with it.
Hi Darlan,
The property with the list of attachments is occasionally updated
by org, using a directory listing. So the change you propose
would not persist.
One way out would be to create a link to the file: Visit it
when it is already in the attachment directory and store a link.
Another possibility would be a new link type attach: which
does find the correct directory using inheritance.
But I Guess this would be a fragile construct.
- Carsten
>
>
> ps: I'm using org 6.28e
>
>
> --
>
> _________________________
> Darlan Cavalcante Moreira
>
>
>
> _______________________________________________
> 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-09-03 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 20:29 Feature Request: changes regarding attachments and subtasks Darlan Cavalcante Moreira
2009-09-03 6:51 ` 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=8D067FFB-DC0E-41B9-937E-3811AA4AC037@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=darcamo@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).