emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: emacs org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org files and directory hierarchies
Date: Thu, 08 Jan 2009 11:07:51 -0600	[thread overview]
Message-ID: <87vdsp3evs.fsf@fastmail.fm> (raw)
In-Reply-To: <20090108155834.GE14694@stats.ox.ac.uk> (Dan Davison's message of "Thu\, 8 Jan 2009 15\:58\:34 +0000")


Hi Dan,

Dan Davison <davison@stats.ox.ac.uk> writes:

>
> So is there any future in thinking about an org extension that would
> automatically maintain a directory hierarchy, mirroring the hierarchy
> of headings in certain org files?
>
> But if the structure of org is truly reflecting the structure of my
> life / thoughts, then wouldn't it make sense for the structure of my
> directories to be doing that too? If so, then the job of maintaining
> the correspondence between org and the directory hierarchy should be
> left to the computer.

Good news. Something like this already exists: 

http://orgmode.org/manual/Attachments.html#Attachments

> This would give rise to an org which is a text-based "map" of ones
> working directories, with org files providing semantics and metadata
> to the directory hierarchy and its files. The directory hierarchy
> could be edited by org's structure editing commands. Etc.

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.

- Matt

  reply	other threads:[~2009-01-08 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 15:58 org files and directory hierarchies Dan Davison
2009-01-08 17:07 ` Matthew Lundin [this message]
2009-01-08 20:40   ` David Lord
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:
  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=87vdsp3evs.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --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).