From: Bastien <bzg@gnu.org>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible to exclude/include tags for agenda custom commands?
Date: Thu, 20 Feb 2020 08:23:34 +0100 [thread overview]
Message-ID: <87r1ypyb61.fsf@gnu.org> (raw)
In-Reply-To: <87k14hzza8.fsf@alphapapa.net> (Adam Porter's message of "Wed, 19 Feb 2020 21:57:19 -0600")
Hi Adam,
Adam Porter <adam@alphapapa.net> writes:
> Yes, I'd be glad for it to be listed on Worg. Feel free to add it if
> you like, or I might add it myself after I add a bit more content.
I'll let you add a link to your page on Worg when you have the time.
> I was thinking about working on Worg rather than making yet another
> resource, but:
>
> 1. I saw you mention that you're planning to reorganize Worg's content
> soon, and I wouldn't want to interfere with that.
Just to tell you a bit more about my plan: I will take the time to
work on Worg next week, creating a dedicated branch and publishing it
on orgmode.org/worg-next/ or something.
> 2. I sometimes feel hesitant to put a lot of effort into curating and
> organizing content on Worg because, like all wikis, that work can easily
> be invalidated if others come along later and add content in random
> places.
Yes, I understand. Worg was a place to gather contributions when the
Org users formed a small dedicated group. Org's "community" is larger
now, and I think Org should be a place with less textual contents and
more links to useful stuff. Like a giant structured FAQ, more than a
giant... mess.
> One of my goals for this "org-almanac" is to catalog content in a
> somewhat canonical way, to avoid the "wiki effect." For this project,
> I'd rather have less content that's organized more clearly, than have
> lots of content scattered about. Of course, I don't presume to say that
> the way I've done it is the best way, and I'm experimenting as I go.
>
> Anyway, do you have any more thoughts about these issues?
I think that your goals for org-almanac resemble the ones I have for
Worg: less content, clear structure, make it more maintainable, even
collectively. Without sacrificing the current richness, of course.
This will be more tangible when I start pushing worg-next/.
Thanks,
--
Bastien
next prev parent reply other threads:[~2020-02-20 7:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 19:03 Possible to exclude/include tags for agenda custom commands? Stig Brautaset
2020-02-12 22:30 ` Bastien
2020-02-13 19:39 ` Stig Brautaset
2020-02-14 10:02 ` Bastien
2020-02-14 22:05 ` Adam Porter
2020-02-18 13:05 ` Bastien
2020-02-20 3:57 ` Adam Porter
2020-02-20 7:23 ` Bastien [this message]
2020-02-20 16:50 ` Eric Abrahamsen
2020-02-20 17:24 ` Bastien
2020-02-20 17:48 ` Eric Abrahamsen
2020-02-20 19:02 ` Eric Abrahamsen
2020-02-20 19:08 ` Bastien
2020-02-20 19:51 ` Eric Abrahamsen
2020-02-23 13:24 ` Bastien
2020-02-23 20:55 ` Eric Abrahamsen
2020-02-24 9:14 ` Bastien
2020-02-24 17:03 ` Eric Abrahamsen
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=87r1ypyb61.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=adam@alphapapa.net \
--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 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).