From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: ANN: org-super-agenda
Date: Sat, 29 Jul 2017 01:03:18 -0500 [thread overview]
Message-ID: <87k22req55.fsf@alphapapa.net> (raw)
In-Reply-To: 871sp0f45j.fsf@alphapapa.net
Adam Porter <adam@alphapapa.net> writes:
> After thinking about this some more, I have an idea: if I go ahead and
> import the agenda-building functions into my package and modify them, I
> can use a minor mode to override the standard functions with advice.
> That way users would only have to define the groups variable, and all
> the agenda commands would pick it up automatically, from the user's
> perspective. That would prevent users from having to define new agenda
> commands that call special functions; they could just use their existing
> custom agenda commands.
FYI, this idea worked out well. In fact, I only have to override one
function, org-agenda-finalize-entries. I haven't fully tested all the
different agenda commands yet, but it's working well so far. I'd
appreciate help testing further. :)
next prev parent reply other threads:[~2017-07-29 6:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bef0ca0ddb1848229ffa212f987e37e6@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-24 11:21 ` ANN: org-super-agenda Eric S Fraga
2017-07-27 7:55 ` Eric S Fraga
2017-07-29 1:00 ` Adam Porter
2017-07-29 6:03 ` Adam Porter [this message]
[not found] ` <fbe13af252304f5f9a39fab52999d40c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-29 10:40 ` Eric S Fraga
2017-07-29 19:41 ` Adam Porter
2017-07-29 23:11 ` Adam Porter
[not found] ` <910e863b18d740e492dd1681840ec9d8@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-30 8:20 ` Eric S Fraga
[not found] ` <4a14bcc89c8847aba15bb3f18e5af494@DB5PR01MB1895.eurprd01.prod.exchangelabs.com>
2017-07-30 8:15 ` Eric S Fraga
2017-07-23 22:49 Adam Porter
2017-07-24 3:11 ` Adam Porter
2017-07-29 19:47 ` Adam Porter
2017-08-01 6:32 ` Adam Porter
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=87k22req55.fsf@alphapapa.net \
--to=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 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.