From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lord Subject: Re: org files and directory hierarchies Date: Thu, 8 Jan 2009 20:40:37 +0000 Message-ID: <1FEB88C0-5145-4D72-A9CA-DF455AEA4548@gmail.com> References: <20090108155834.GE14694@stats.ox.ac.uk> <87vdsp3evs.fsf@fastmail.fm> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LL1gM-0000w8-FK for emacs-orgmode@gnu.org; Thu, 08 Jan 2009 15:40:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LL1gK-0000vQ-P2 for emacs-orgmode@gnu.org; Thu, 08 Jan 2009 15:40:45 -0500 Received: from [199.232.76.173] (port=52268 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LL1gK-0000vJ-KC for emacs-orgmode@gnu.org; Thu, 08 Jan 2009 15:40:44 -0500 Received: from mail-ew0-f13.google.com ([209.85.219.13]:47655) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LL1gK-0005W1-1n for emacs-orgmode@gnu.org; Thu, 08 Jan 2009 15:40:44 -0500 Received: by ewy6 with SMTP id 6so10210099ewy.18 for ; Thu, 08 Jan 2009 12:40:42 -0800 (PST) In-Reply-To: <87vdsp3evs.fsf@fastmail.fm> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Matthew Lundin Cc: emacs org-mode mailing list On 8 Ion 2009, at 17:07, Matthew Lundin wrote: > > One caveat. Org attach doesn't work in quite this way. The data > directory hierarchy isn't really human readable (i.e., it doesn't > mirror the org outline hierarchy). But that would be a nightmare to > make work, I imagine, because of constant changes to the org outline > structure. Rather, directories containing files are attached to > outline headings via automatically generated IDs. Well, why not allow the user to choose a directory, there's no real reason why the directory structure has to match the org file? I started using attachments when the feature came out and really liked them, especially the simple interface for choosing a file to attach (even better with ido). But after a while, I found the fact that I could only reasonably get to attachments through the org file difficult to work with - what happens when I've finished a task and archived it off? I've got to go hunting through the archive file to find the old task before I can find the attachments. So I stopped using them and decided I'd use normal hyperlinks instead. But then I found out just how awkward is is to have to either cut-and-paste the directory path or type it in manually whenever I want to link to a file. Regards David Lord