From: Samuel Wales <samologist@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Culling org files
Date: Thu, 4 Mar 2021 14:11:37 -0700 [thread overview]
Message-ID: <CAJcAo8tjnJkC2v0Ju2_icHU-g9Pq96_=Kq6TD254JZrQaxn2Vg@mail.gmail.com> (raw)
In-Reply-To: <8735xa1xyf.fsf@gmail.com>
trs> [smaller files] My agenda is not cluttered.
it is not clear to me why more smaller files and shallower trees in
the outline would improve the agenda. sounds good though.
tim> naming convention ... to determine what is included
this is also what i do. org-agenda-files is just set at startup
according to basename pattern.
On 3/4/21, Tim Cross <theophilusx@gmail.com> wrote:
>
> TRS-80 <lists.trs-80@isnotmyreal.name> writes:
>
>> On 2021-03-03 16:59, Samuel Wales wrote:
>> I have come to similar conclusion about "don't let org files get too
>> big." Besides agenda speed, I think it is just easier to
>> conceptualize things when each file covers only a limited scope, trees
>> are more shallow, etc.
>>
>> So, lately (last year or more), I have been trying a "many small (up
>> to perhaps medium)" instead of "few big" files approach (along with
>> some custom tooling) and it has been working /a lot/ better for me. I
>> really feel on top of things for the first time in a long time. My
>> agenda is not cluttered. I can focus on important things, while not
>> losing track of the rest, etc.
>>
>
> I agree with this. I have a similar approach. I consider the file system
> and org files to be the initial 'structure' and have many smaller files
> rather than a couple of very large ones. Only a subset of files play a
> role in the agenda (I'm still experimenting with two different
> approaches for this - one uses a couple of functions which can
> dynamically change the agenda list and the other uses a naming
> convention which is used as the basis of a search to determine what is
> included in the agenda. Final rsult will likely be a combination).
>
> My use pattern also constantly evolves as my requirements and priorities
> change. It is and probably always will be, a work in progress!
>
> --
> Tim Cross
>
>
--
The Kafka Pandemic
Please learn what misopathy is.
https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
next prev parent reply other threads:[~2021-03-04 21:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:59 Culling org files Samuel Wales
2021-03-04 17:10 ` TRS-80
2021-03-04 19:25 ` Tim Cross
2021-03-04 21:11 ` Samuel Wales [this message]
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='CAJcAo8tjnJkC2v0Ju2_icHU-g9Pq96_=Kq6TD254JZrQaxn2Vg@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
/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).