From: David Masterson <dsmasterson@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Suggestion: User-contributed use-cases on orgmode.org ?
Date: Mon, 13 Nov 2023 21:09:54 -0800 [thread overview]
Message-ID: <LV8P223MB09203355A0BA7464EA418E2AA2B2A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
Just a suggestion (or maybe this is already handled?).
Was thinking I'd like to see an archive of tagged use-cases for Org that
could be searched via tags or regexp. The use-cases should include a
description of the problem, a general description of the answer, blocks
of elisp (general code) to setup the answer, and how to use the code to
do the work of the use-case. In fact, it could be recommended that the
use-cases be written in literate programming style (the first use-case
would have to provide the recommended example). As such, if written
properly in Org, it could (after a once over by maintainers) be exported
to HTML for inclusion on orgmode.org.
My reason for this is to have a ready reference for how other people
have setup functions/variables that I could then copy/modify for my
particular need. Many times, hacking other people's code is easier than
digging into the Elisp of the various parts of Org. Forty years of using
Emacs (off fand on) and hacking pieces of Elisp, I never really learned
programming in Elisp.
--
David Masterson
next reply other threads:[~2023-11-14 5:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 5:09 David Masterson [this message]
2023-11-14 8:36 ` Suggestion: User-contributed use-cases on orgmode.org ? Russell Adams
2023-11-14 10:31 ` Max Nikulin
2023-11-15 2:16 ` David Masterson
2023-11-15 3:23 ` Corwin Brust
2023-11-16 2:56 ` David Masterson
2023-11-16 9:43 ` Ihor Radchenko
2023-11-17 5:13 ` David Masterson
2023-11-17 9:31 ` Ihor Radchenko
2023-11-17 18:26 ` David Masterson
2023-11-18 10:51 ` Ihor Radchenko
2023-11-18 19:18 ` David Masterson
2023-11-19 15:38 ` Bastien Guerry
2023-11-15 2:14 ` David Masterson
2023-11-15 13:33 ` Russell Adams
2023-11-16 2:58 ` 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=LV8P223MB09203355A0BA7464EA418E2AA2B2A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.