From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Culling org files
Date: Wed, 3 Mar 2021 14:59:46 -0700 [thread overview]
Message-ID: <CAJcAo8uG_NRv8uDTRBmPFQoJQ1eqYhq4XRxYgJsCvz-O+h-7Qg@mail.gmail.com> (raw)
along lines of reducing logbook entries, i often want to reduce org
files, and i wonder if anybody already had the same desire.
here are some random ideas. my org files are so
large i might have written this list a few times....
1) list links to duplicate headlines
2) list links to duplicate body text
3) list links to duplicate entries
4) list links to duplicate entries, body text, or
headlines using fuzzy matching
- suppose you captured an email slightly differently a
few times
5) show in agenda the biggest few tasks so you can go to
them and reduce them or doneify them
6) (waves hands) git magic to find old entries that might
be stale
7) show in agenda the tasks with biggest logbook drawers
so you can go to them and reduce them
8) find similar body text that are in distant subtrees
that might be candidates for refactoring using org-id
linking
9) show in agenda deepest olpath levels
10) indicate deep, shallow, text-filled, etc. top levels
11) show in agenda entries with most children
12) archive logbook drawer entries older than 1 year
- get rid of drawer if empty
- put the drawer entries into a logbook drawer in a
new task, with a similar header, that then gets
doneified. then that gets archived when you archive
stuff.
13) operate on lines matching a pattern
- e.g. "* [2021-02-17 Wed 20:35] whatever" lines
might be insubstantial notes that do not need to
clutter the inactive timestamp display in the agenda
and thus should be moved to a target location with
query
- that target location would presumably not be in an
agenda file
14) function to lint all agenda files
15) reduce false positives in lint
well, idk if htese are good ideas. just thought maybe we
could form a cult of "don't let org files get too big".
--
The Kafka Pandemic
Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
next reply other threads:[~2021-03-03 22:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:59 Samuel Wales [this message]
2021-03-04 17:10 ` Culling org files TRS-80
2021-03-04 19:25 ` Tim Cross
2021-03-04 21:11 ` Samuel Wales
2021-03-05 16:12 ` Culling org files (notion of Types, many small vs few big files) TRS-80
2021-03-05 20:32 ` Tim Cross
2021-03-05 20:51 ` Samuel Wales
2021-03-05 20:58 ` Samuel Wales
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=CAJcAo8uG_NRv8uDTRBmPFQoJQ1eqYhq4XRxYgJsCvz-O+h-7Qg@mail.gmail.com \
--to=samologist@gmail.com \
--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).