From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-fstree.el overview over directories (but no comments are possible)
Date: Sun, 30 Oct 2022 13:56:01 +0000 [thread overview]
Message-ID: <871qqph0um.fsf@posteo.net> (raw)
In-Reply-To: <87a65d78zw.fsf@mat.ucm.es> (Uwe Brauer's message of "Sun, 30 Oct 2022 14:10:11 +0100")
Uwe Brauer writes:
> Well, since I tend to forget things, and it is very time consuming to
> open files and see what is the basic content, I thought of adding to
> each directory (with subdirectories if necessary) I find useful a
> README.org file, that contains a
>
> 1. Tree of the directory and
>
> 1. a short description of the content of each file
>
> I use bookmarks.el but that is an entirely different workflow, since I
> there only save files that I find useful, but sometimes I stumble across
> a directory I created some time ago and don't recall the content of
> each file.
I see. It's not exactly what you're looking for, but I often use
filetags.el (https://github.com/DerBeutlin/filetags.el) which allows you
to add tags to files and directories in Dired. You can add multiple
tags, remove or update them. It's not a panacea, because the tags are
added directly to the file/directory name (as part of the name, I mean),
but in general it's enough for me when I want to have a file tagged in
some way. I can then locate this files by tag names using helm-locate.
Perhaps a kind of ''dired-org-view'' could be interesting, to display a
dired directory as an Org buffer, where you could add (persistent) TODO
states, notes and tags. Well, it's a sudden occurrence, I don't know to
what extent it is feasible, but in case someone feels inspired... :-)
You also have this package (haven't tried it):
https://github.com/Boruch-Baum/emacs-diredc Adds a lot of functionality
to Dired, including file preview.
Best regards,
Juan Manuel
next prev parent reply other threads:[~2022-10-30 13:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 9:49 org-fstree.el overview over directories (but no comments are possible) Uwe Brauer
2022-10-30 12:52 ` Juan Manuel Macías
2022-10-30 13:10 ` Uwe Brauer
2022-10-30 13:56 ` Juan Manuel Macías [this message]
2022-10-30 14:01 ` Uwe Brauer
2022-10-30 15:40 ` Juan Manuel Macías
2022-10-30 16:42 ` Uwe Brauer
2022-10-30 17:16 ` Uwe Brauer
2022-10-30 18:17 ` Juan Manuel Macías
2022-10-30 18:48 ` Uwe Brauer
2022-10-30 19:04 ` Juan Manuel Macías
2022-10-30 19:21 ` Uwe Brauer
2022-10-30 19:26 ` [correction] (was: org-fstree.el overview over directories (but no comments are possible)) Uwe Brauer
2022-10-30 19:51 ` [correction] Juan Manuel Macías
2022-10-30 21:23 ` [correction] Uwe Brauer
2022-10-31 12:22 ` [correction] Juan Manuel Macías
2022-10-31 12:55 ` [correction] Uwe Brauer
2022-10-31 15:08 ` [correction] Juan Manuel Macías
2022-10-31 15:48 ` [correction] Uwe Brauer
2022-10-31 16:23 ` [correction] Juan Manuel Macías
2022-10-31 16:33 ` [correction] Uwe Brauer
2022-10-31 16:58 ` [correction] Uwe Brauer
2022-10-31 17:35 ` [correction] Juan Manuel Macías
2022-10-31 17:38 ` [correction] Uwe Brauer
2022-10-31 21:01 ` [correction] Juan Manuel Macías
2022-11-01 7:13 ` [correction] Uwe Brauer
2022-11-01 7:16 ` [correction] Uwe Brauer
2022-11-01 13:52 ` [correction] Juan Manuel Macías
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=871qqph0um.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=oub@mat.ucm.es \
/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).