emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Lord <dlordster@gmail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org files and directory hierarchies
Date: Thu, 8 Jan 2009 20:40:37 +0000	[thread overview]
Message-ID: <1FEB88C0-5145-4D72-A9CA-DF455AEA4548@gmail.com> (raw)
In-Reply-To: <87vdsp3evs.fsf@fastmail.fm>

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.

David Lord

  reply	other threads:[~2009-01-08 20:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 15:58 Dan Davison
2009-01-08 17:07 ` Matthew Lundin
2009-01-08 20:40   ` David Lord [this message]
2009-01-08 21:33     ` Carsten Dominik
2009-01-09 11:04       ` David Lord

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:

  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=1FEB88C0-5145-4D72-A9CA-DF455AEA4548@gmail.com \
    --to=dlordster@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --subject='Re: org files and directory hierarchies' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).