From: Marcin Borkowski <mbork@mbork.pl>
To: "Tory S. Anderson" <webdev@toryanderson.com>
Cc: "Sébastien Gendre" <seb@k-7.ch>, emacs-orgmode@gnu.org
Subject: Re: Org-mode notes about school lessons
Date: Sat, 25 Feb 2023 09:08:43 +0100 [thread overview]
Message-ID: <87lekmcgl0.fsf@mbork.pl> (raw)
In-Reply-To: <87y1ont2nn.fsf@byu.edu>
On 2023-02-24, at 18:05, Tory S. Anderson <webdev@toryanderson.com> wrote:
>> As I need to write a lot for each lesson, and each lesson are mostly
>> independent from each other, I plan to have 1 file per lesson.
> This is a very stylistic, but I am a "all in one file" user, though
> I have a seperate directory and .org file per class, but no more split
> than that. I have always had =C-c s= bound in org files to something
> like =consult-org-heading= (or the helm equivalent, or selectrum
> equivalent, or even the vanilla emacs equivalent that I can't remember
> right now). To me, being able to easily go to headings/classes in one
> file fits my usage. I could see arguments for the other, though, since
> emacs is good at browsing/searching multiple files, too. And I suppose
> git version control might be more useful on the multiple-file setup.
This. To each his own, but I also can't see much benefit of having many
small files instead of a few larger ones. For example, linking to other
sections might be easier this way. But, as Tory said, this is also
about personal preference, so I'm not claiming here that my way is
objectively better.
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2023-02-25 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 12:08 Org-mode notes about school lessons Sébastien Gendre
2023-02-24 17:05 ` Tory S. Anderson
2023-02-25 4:37 ` Bob Newell
2023-02-25 8:08 ` Marcin Borkowski [this message]
2023-02-28 6:00 ` Jean Louis
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=87lekmcgl0.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=emacs-orgmode@gnu.org \
--cc=seb@k-7.ch \
--cc=webdev@toryanderson.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).