This is the start and end of my 117k lines long org-file which I use as a
work log-book. I'm still editing it daily:
#+OPTIONS: ^:{} toc:nil num:nil html-postamble:nil
#+STARTUP: hidestars org-startup-with-inline-images showall
* <2010-12-22 Wed>
- Spoke with Ran on phone. Agreed to call them next week about coming for
a visit.
* <2010-12-28 Tue>
CLOCK: [2010-12-28 Tue 15:00]--[2010-12-28 Tue 18:00] => 3:00
** Meeting with Ran about block diagram of system
:
* <2025-02-26 Wed>
** Done/Todo
:
On Wed, Feb 26, 2025 at 11:20 AM Rudolf Adamkovič <[email protected]>
wrote:
> Sébastien Gendre <[email protected]> writes:
>
> > I have a question for other Org-mode users: [...]
>
> I tried both and currently use one big file.
>
> The disadvantages are: sirupy load times and impractical exporting into
> multiple files, like multiple HTML pages, in one go (Texinfo saves the
> day, but is limited).
>
> The advantages are: simple navigation (headings versus headings and
> files), fast agenda (to the point of being usable), simple agenda (no
> need to maintain the list of agenda files), good tangling (concatenation
> works across headings but not across files), and more.
>
> > But having one big file can make finding an information challenging.
> > We can still use narrow to focus on one item, and imenu to navigate.
>
> I use speed commands [*] and `org-goto' configured as follows:
>
> (with-eval-after-load 'org
> (setq org-goto-interface 'outline-path-completion
> org-goto-max-level 100
> org-outline-path-complete-in-steps nil))
>
> The key is to make everything you might want to search for or jump to
> into a heading. With that, Org shines, being an outliner.
>
> [*] Beware: Speed commands do not work reliably in macros; they will
> screw up your document behind your back! (CC-ing Ihor WRT this.)
>
> Rudy
> --
> "The whole science is nothing more than a refinement of everyday
> thinking." --- Albert Einstein, 1879-1955
>
> Rudolf Adamkovič <[email protected]> [he/him]
> http://adamkovic.org
>
>
