From: Corwin Brust <corwin@bru.st>
To: David Masterson <dsmasterson@gmail.com>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Suggestion: User-contributed use-cases on orgmode.org ?
Date: Tue, 14 Nov 2023 21:23:52 -0600 [thread overview]
Message-ID: <CAJf-WoRekv3T-eRO6V4nwhOjXO77G-sg4mOyTLu0pr53NU8hCw@mail.gmail.com> (raw)
In-Reply-To: <LV8P223MB0920D5234213F4823397B95DA2B1A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM>
On Tue, Nov 14, 2023 at 8:16 PM David Masterson <dsmasterson@gmail.com> wrote:
>
> Max Nikulin <manikulin@gmail.com> writes:
>
> > On 14/11/2023 15:36, Russell Adams wrote:
> >> On Mon, Nov 13, 2023 at 09:09:54PM -0800, David Masterson wrote:
> >>>
> >>> Was thinking I'd like to see an archive of tagged use-cases for Org that
> >>> could be searched via tags or regexp.
> > [...]
> >> Have you looked at Worg?
> >
> > Specifically there is
> > https://orgmode.org/worg/org-hacks.html
> > "Org ad hoc code, quick hacks and workarounds"
> > page. No tags however. To my taste it is overwhelmingly large.
>
> Perhaps a Wiki would be better?
>
WORG is the Wiki for Org, or perhaps I'm not sure what you mean:
better than what?
Patches to WORG don't require assignment, btw.
Please do suggest significant restructuring. I think your organizing
things more in terms of use-cases could be something that will make
WORG more of a "first choice" for people to find and leave suggestions
for getting the most from org.
Alternatively, perhaps the key element of "wiki" for some is "web
accessible editing", in which case I wonder if using EmacsWiki would
make sense.
next prev parent reply other threads:[~2023-11-15 3:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 5:09 Suggestion: User-contributed use-cases on orgmode.org ? David Masterson
2023-11-14 8:36 ` Russell Adams
2023-11-14 10:31 ` Max Nikulin
2023-11-15 2:16 ` David Masterson
2023-11-15 3:23 ` Corwin Brust [this message]
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
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=CAJf-WoRekv3T-eRO6V4nwhOjXO77G-sg4mOyTLu0pr53NU8hCw@mail.gmail.com \
--to=corwin@bru.st \
--cc=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.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).