From: Bastien <bzg@altern.org>
To: Darlan Cavalcante Moreira <darcamo@gmail.com>
Cc: "Gustav Wikström" <gustav.erik@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Attachments and refiling
Date: Thu, 28 Jul 2011 09:51:54 +0200 [thread overview]
Message-ID: <87vcum6d5p.fsf@altern.org> (raw)
In-Reply-To: <4e2d91f9.8188ec0a.1582.1369@mx.google.com> (Darlan Cavalcante Moreira's message of "Mon, 25 Jul 2011 12:55:31 -0300")
Hi Darlan,
here is how I see the situation regarding attachments:
1. org-attach.el is nice because it makes it easy to attach a file to a
task, while not *worrying* about where the file is on the harddrive.
2. Adding an ATTACH_DIR property will always add an absolute path, so
there is no problem when moving an entry with an explicit ATTACH_DIR.
3. Refiling/archiving subtrees lose track of some attachments when the
attach directory "data/" is *relative* to the org file (which is the
default) and when the target org file is not in the same directory.
4. Moving an entry with an ATTACH_DIR_INHERIT will lose attachments
when the ATTACH_DIR of the target entry is different.
(3) and (4) are two distinct problems.
I suggest fixing problem (3) by making `org-attach-dir' defaulting to
"~/.org-attachments/". I
I suggest fixing problem (4) by explicitely replacing ATTACH_DIR_INHERIT
with the corresponding ATTACH_DIR when the target subtree has a
different ATTACH_DIR.
The core idea is that I want to avoid moving files themselves: I think
it's a risky road, and I hope the solutions above will make this road
unnecessary.
I'm interested in feedback and ideas about such proposed changes.
Thanks a lot!
--
Bastien
next prev parent reply other threads:[~2011-07-28 8:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:06 Attachments and refiling Gustav Wikström
2011-07-15 11:16 ` Bastien
2011-07-15 14:55 ` Gustav Wikström
2011-07-16 15:50 ` Darlan Cavalcante Moreira
2011-07-19 12:17 ` Gustav Wikström
2011-07-24 20:00 ` Bastien
2011-07-25 0:14 ` Brian van den Broek
2011-07-25 7:10 ` Gustav Wikström
2011-07-25 7:45 ` Bastien
2011-07-25 15:55 ` Darlan Cavalcante Moreira
2011-07-28 7:51 ` Bastien [this message]
2011-07-28 10:38 ` suvayu ali
2011-07-28 13:46 ` Nick Dokos
2011-07-28 13:49 ` suvayu ali
2011-07-28 14:33 ` Nick Dokos
2011-07-28 17:31 ` Darlan Cavalcante Moreira
2011-07-28 18:04 ` Bernt Hansen
2011-07-29 7:27 ` Gustav Wikström
2011-08-02 4:02 ` Matt Lundin
2011-08-29 12:04 ` Gustav Wikström
2011-07-24 20:07 ` Bastien
2011-07-25 7:21 ` Gustav Wikström
2011-07-29 8:33 ` Gustav Wikström
2011-07-29 20:58 ` Darlan Cavalcante Moreira
2011-08-18 17:33 ` Bastien
2011-08-18 20:37 ` Darlan Cavalcante Moreira
2011-08-19 8:46 ` Bastien
2011-08-19 16:29 ` Darlan Cavalcante Moreira
2011-08-24 14:12 ` Bastien
2011-08-24 14:56 ` Darlan Cavalcante Moreira
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=87vcum6d5p.fsf@altern.org \
--to=bzg@altern.org \
--cc=darcamo@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gustav.erik@gmail.com \
/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).