From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: ANN: org-super-agenda
Date: Sat, 29 Jul 2017 14:41:50 -0500 [thread overview]
Message-ID: <87bmo3vxmp.fsf@alphapapa.net> (raw)
In-Reply-To: 87inibwmp3.fsf@delle7240.chemeng.ucl.ac.uk
Hi Eric,
Thanks for your email. First off, the package is on MELPA now, and I've
added several more features, so feel free to give it a shot. :)
> I guess my challenge is understanding how to specify what I want in
> your super agenda specifications. For instance, how do I get a list
> of tasks with deadlines as a separate entry?
That's the :deadline selector.
> How do I get un-prioritised TODO entries listed?
I don't have a selector for unprioritized TODO entries...yet. I'll look
into that. :)
> These all come at the end, in the "catch-all" section, for me which is
> not what I want.
Ok, I think I see the problem. You see, your example command is
actually a series of custom commands, and the "todo" custom command
selects items without regard for their timestamp, without regard for
whether they'd appear in an daily/weekly "agenda" command. So you may
need to define org-super-agenda-groups for individual commands in the
series.
Just to be sure we're on the same page, this package is for grouping
together items that are already selected by an agenda command (and the
:discard selector can be used as a filter, but that's not the package's
primary purpose).
> The same with the clock report: it would be good to be able to place
> this where I want it.
That's actually handled by Org itself, not this package. To modify
where that goes, I think, would require modifying the agenda commands,
like org-agenda-list, to change when in the insertion sequence it adds
the clock report. That would be a nice feature, but it's something that
should be addressed in Org itself.
I apologize for the confusion. Since you wrote that email, I refactored
the code so that I no longer override the agenda commands, but just the
org-agenda-finalize-entries function, which is much simpler. So while I
could have changed the clock report position before, now I can't. But
it's better this way...for me, at least. ;)
I don't know if this is quite what you're looking for, but maybe this
will give you some ideas:
#+BEGIN_SRC el
(let ((org-agenda-span 'day)
(org-agenda-custom-commands
'(("v" "Startup View"
((todo "TODO" ((org-agenda-overriding-header "Currently active tasks: ")))
(todo "WAITING" ((org-agenda-overriding-header "Tasks waiting on others: ")))
(todo "SOMEDAY" ((org-agenda-overriding-header "Tasks for sometime later: ")))
(agenda "" ((org-agenda-time-grid nil)
(org-deadline-warning-days 365)
(org-agenda-entry-types (quote (:deadline)))
(org-agenda-skip-entry-if (quote scheduled))
(org-agenda-ndays 1)
(org-agenda-overriding-header "Unscheduled upcoming deadlines:")))
(agenda "" ((org-agenda-ndays 1)
(org-deadline-warning-days 1)))
(todo "" ((org-agenda-overriding-header "Unscheduled No Deadline TODO: "))))
;; Settings for all commands in the set
((org-super-agenda-groups
'((:deadline t))))))))
(org-agenda nil "v"))
#+END_SRC
Thanks for your feedback!
next prev parent reply other threads:[~2017-07-29 19:42 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
[not found] ` <fbe13af252304f5f9a39fab52999d40c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-07-29 10:40 ` Eric S Fraga
2017-07-29 19:41 ` Adam Porter [this message]
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
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=87bmo3vxmp.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 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).