From: Sebastian Rose <sebastian_rose@gmx.de>
To: Andreas Burtzlaff <andy13@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] org-fstree: insert directory subtrees into org buffers
Date: Sun, 29 Mar 2009 03:57:36 +0200 [thread overview]
Message-ID: <87ab756qgf.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <20090329005415.014ca2c3.andy13@gmx.net> (Andreas Burtzlaff's message of "Sun, 29 Mar 2009 00:54:15 +0100")
Andreas Burtzlaff <andy13@gmx.net> writes:
> Hello everyone,
>
> the idea is now implemented as an extension to org-mode.
>
> Available here: http://www.burtzlaff.de/org-fstree/org-fstree.el
>
> org-fstree inserts the filesystem subtree for a given directory.
> Each file/directory is formatted as a headline, provides links back
> to all headlines that are associated with it (by containing links to the file)
> and is assigned their tags.
>
> Usage:
> - enter a line containing "#+BEGIN_FSTREE: <dir>" into an org buffer,
> where <dir> is the directory, that is to be inserted.
> - while the cursor is in the line mentioned, press "C-c C-c"
>
> Hope someone else than Sebastian and me finds this useful.
I find this useful! Thans for putting this in elisp.
Some additions I could thing of:
* a customizable list of directory names to skip.
'("CVS" "_MTN" ".git" ".hg" "RCS") might be a good default.
* Add directory names to the skip list
#+begin fstree -sd (nogo notes)
* Skip files by suffix
#+begin fstree -sf (.jpg .gif ...)
* Maybe require the option `-r' to be recursive.
Files are often grouped in directories for a purpose. If I jott down
some notes it would be great to just add files in that one directory
that contains files related to the sections content.
* Add a slash to the directory names to make the list more
readable. As an alternative, I could imagine to use folder icons
like speedbar, or use headlines without links for directories (the
links all look the same, wether they are headlines or leaves).
- Sebastian
next prev parent reply other threads:[~2009-03-29 1:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 3:11 combine orgmode and file system browsing Andreas Burtzlaff
2009-03-21 2:20 ` Sebastian Rose
2009-03-21 5:12 ` Andreas Burtzlaff
2009-03-23 11:59 ` Sebastian Rose
2009-03-28 23:54 ` [ANN] org-fstree: insert directory subtrees into org buffers Andreas Burtzlaff
2009-03-29 1:30 ` Cameron Horsburgh
2009-03-29 1:57 ` Sebastian Rose [this message]
2009-03-29 12:41 ` [ANN] org-fstree 0.2 Andreas Burtzlaff
2009-03-29 17:10 ` Sebastian Rose
2009-03-30 6:39 ` Carsten Dominik
2009-03-31 9:48 ` Alan E. Davis
2009-04-01 1:12 ` Andreas Burtzlaff
2009-04-01 4:22 ` Carsten Dominik
2009-04-01 23:50 ` Andreas Burtzlaff
2009-04-03 9:45 ` Carsten Dominik
2009-04-04 3:01 ` Andreas Burtzlaff
2009-04-04 3:04 ` Carsten Dominik
2009-06-10 19:14 ` [ANN] org-fstree: insert directory subtrees into org buffers Lindsay Todd
2009-06-12 3:56 ` [ANN] org-fstree: insert directory subtrees into org buffers / UPDATE Andreas Burtzlaff
2009-06-18 22:35 ` Lindsay Todd
2009-06-19 12:39 ` Andreas Burtzlaff
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=87ab756qgf.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=andy13@gmx.net \
--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).