emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: ANN: org-super-agenda
Date: Sat, 29 Jul 2017 11:40:24 +0100	[thread overview]
Message-ID: <87inibwmp3.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: fbe13af252304f5f9a39fab52999d40c@HE1PR01MB1898.eurprd01.prod.exchangelabs.com

[-- Attachment #1: Type: text/plain, Size: 2468 bytes --]

Hi Adam,

thanks for the long email explaining the process and issues.

I've updated to latest version.

> Well, as it stands, this package is mainly a way to group together items
> that the standard agenda view (i.e. the org-agenda-list function) has
> gathered.

Understood.  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?  How do I get
un-prioritised TODO entries listed?  These all come at the end, in the
"catch-all" section, for me which is not what I want.  The same with the
clock report: it would be good to be able to place this where I want
it.

I have my own customised view where I have the following:

#+begin_src emacs-lisp
  ("v" "Startup View"
   (
    (todo "INPR" (quote(org-agenda-overriding-header "Currently active tasks: ")))
    (todo "WAIT" (quote(org-agenda-overriding-header "Tasks waiting on others: ")))
    (todo "POST" (quote(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 "" (quote(org-agenda-overriding-header "Unscheduled No Deadline TODO: ")))))
#+end_src 

and I would like to mimick some of this behaviour.  Mind you, I can
simply use my view, of course!

> So the question becomes, how many Org agenda functions do I want to copy
> into my package and be responsible for fixing?

Probably not too many :-)

>> 3. a clock summary (equivalent to what one gets with "v c" in standard
>>    view)
>
> I confess that I have never used this feature before you mentioned it.

It's a useful feature but annoying in the default behaviour in that it
is either this or not at all.  (view log will display clocking
information but also task completion etc. which is more info than I
usually want [I know which jobs I finished])

> I will look into this and push it to the repo if it works.  Please let
> me know if you have any other ideas or suggestions.

Thanks.  I'll keep playing on and off.

-- 
: Eric S Fraga via Emacs 26.0.50, Org release_9.0.9-573-g09e612

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]

  parent reply	other threads:[~2017-07-29 10:43 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 [this message]
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

  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=87inibwmp3.fsf@delle7240.chemeng.ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).