From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Q: Attachments and IDs?
Date: Sun, 14 Jul 2024 10:16:11 -0700 [thread overview]
Message-ID: <LV8P223MB09208DEC7A72787F183240E2A2A02@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87sewcjn1m.fsf@localhost> (Ihor Radchenko's message of "Sun, 14 Jul 2024 10:16:53 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> I do not think that we need an appendix - most of the terms are simply
> introduced one by one while reading the manual.
My problem may be in treating the user's manual as a reference manual.
So, if a term is introduced (and explained) in another section(s) that I
didn't think applied to my particular issue, I might not see it or even
know where to look for it without reading the whole manual. Coupled
with fading memory, I forget what I read a few months ago that might
apply. The appendix idea was simply to get all the key terminology in
one area (which could then reference out to other sections in the
manual) like Main Index. Wait a sec -- Main Index? I hadn't really
thought about that before, but I think that's what I meant by appendix.
Duh. Thanks for putting *up* with me.
--
David Masterson
next prev parent reply other threads:[~2024-07-14 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 22:34 Q: Attachments and IDs? David Masterson
2024-07-11 13:46 ` Ihor Radchenko
2024-07-13 3:34 ` David Masterson
2024-07-13 13:35 ` Ihor Radchenko
2024-07-14 4:18 ` David Masterson
2024-07-14 10:16 ` Ihor Radchenko
2024-07-14 17:16 ` David Masterson [this message]
2024-07-11 16:18 ` Daniel Fleischer
2024-07-13 3:09 ` David Masterson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=LV8P223MB09208DEC7A72787F183240E2A2A02@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.