From mboxrd@z Thu Jan 1 00:00:00 1970 From: Darlan Cavalcante Moreira Subject: Re: Attachments and refiling Date: Thu, 28 Jul 2011 14:31:50 -0300 Message-ID: <4e319ffc.1292970a.6d14.1f1a@mx.google.com> References: <87ei1rrdzd.fsf@gnu.org> <4e21b345.c74cec0a.7e49.3340@mx.google.com> <87mxg3v32m.fsf@altern.org> <877h76u7l7.fsf@gnu.org> <4e2d91f9.8188ec0a.1582.1369@mx.google.com> <87vcum6d5p.fsf@altern.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([140.186.70.92]:41313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmUdM-0000Az-O0 for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 13:44:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmUdL-0006LJ-Dn for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 13:44:32 -0400 Received: from mail-gw0-f49.google.com ([74.125.83.49]:46910) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmUdL-0006L9-BA for emacs-orgmode@gnu.org; Thu, 28 Jul 2011 13:44:31 -0400 Received: by gwb1 with SMTP id 1so2412844gwb.36 for ; Thu, 28 Jul 2011 10:44:30 -0700 (PDT) In-Reply-To: <87vcum6d5p.fsf@altern.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Gustav =?UTF-8?B?V2lrc3Ryw7Zt?= , emacs-orgmode@gnu.org Regarding (2), is this a design decision? Currently I have the ATTACH_DIR property of some headings set to a relative path from the org file and it works perfectly. That is, it is possible to use either absolute or relative path for the ATTACH_DIR property right now. But if this is a design decision then I should not consider this behavior as granted, right? Also, Suvayu's suggestion for the default attachments directory is the best solution IMHO. That is, the default attach directory should be relative to org-directory. -- Darlan At Thu, 28 Jul 2011 09:51:54 +0200, Bastien wrote: > > 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