=== Hmm... I myself went through several refactors of my Org file structures. Exactly because things become unmaintainable over time. It is hard to design a good structure without enough experience with the old one. ===
[my forest structure is actually pretty good. it is partly that i ahve more stuff than i need from years of adding stuff. regular tasks to organize and delete stuff is not within my capabilities at this time. so i am trying to delete stuff as i go. if i get annoyed enough by a search that i can't find anything, then i can in principle go through results sometimes and doneify while trying to find what i want.] one issue with this great thing called capture is that there is nothing quite so convenient that does the exact opposite. [you can regularly purge, if your life/forest is simple enough or you have the physical ability to do things. but you can't just org-doneify-lower-value-stuff-i-captured-when-wasn't-sure-of-their-value-at-the-time without adding energy, concentration, time, etc.] On 12/20/21, Samuel Wales <samolog...@gmail.com> wrote: > well, i implied it at least. > > On 12/20/21, Samuel Wales <samolog...@gmail.com> wrote: >> more below. >> >> On 12/20/21, Ihor Radchenko <yanta...@gmail.com> wrote: >>> If more people are interested, I do not see why next-error integration >>> cannot be included into Org. >> >> nitpick: it already is integrated for sparse tree matches in the >> outline. i suggested that if next-error worked for more things, like >> agenda text and tag matches, then it would be consistent with the >> existing org next-error functionality. user would know to try it. >> >> -- >> The Kafka Pandemic >> >> A blog about science, health, human rights, and misopathy: >> https://thekafkapandemic.blogspot.com >> > > > -- > The Kafka Pandemic > > A blog about science, health, human rights, and misopathy: > https://thekafkapandemic.blogspot.com > -- The Kafka Pandemic A blog about science, health, human rights, and misopathy: https://thekafkapandemic.blogspot.com