From: Bernt Hansen <bernt@norang.ca>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Custom agenda -- running functions, not just setting vars
Date: Wed, 09 Nov 2011 07:18:24 -0500 [thread overview]
Message-ID: <87y5vpebfz.fsf@norang.ca> (raw)
In-Reply-To: <CAMg28OvqVBoNTp1yqo7OzxrSrOnnUE0h=onWAWuYMW+UuzEugw@mail.gmail.com> (Tommy Kelly's message of "Wed, 9 Nov 2011 11:32:12 +0000")
Tommy Kelly <tommy.kelly@verilab.com> writes:
> I'm trying to set up a custom agenda view such that when I enter my
> agenda I get, automatically:
>
> - daily view mode (for today)
> - log file mode on
> - grid on
> - Follow mode on
>
> I can see from the docs how to modify the various variables that
> control some of how agendas look. But the above are controlled by
> functions and I'm not sure how to have those invoked when I open an
> agenda.
>
> I've been messing with org-mode-agenda-hook and
> org-agenda-after-show-hook, but I clearly don't know what I'm doing.
>
> Any ideas?
>
> thanks,
> Tommy
Something like this:
(setq org-agenda-custom-commands
(quote (( "x" "Test Agenda" agenda ""
((org-agenda-start-with-follow-mode t)
(org-agenda-span 'day)
(org-agenda-start-with-log-mode t))))))
but it doesn't handle the grid - I have that on by default by setting
(setq org-agenda-time-grid (quote ((daily today remove-match)
#("----------------" 0 16 (org-heading t))
(830 1000 1200 1300 1500 1700))))
which you can probably add to the above agenda definition but I didn't
bother. If there are no items to display on the agenda there is a bug
where the grid is not shown but otherwise I think this works.
Regards,
Bernt
next prev parent reply other threads:[~2011-11-09 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 11:32 Custom agenda -- running functions, not just setting vars Tommy Kelly
2011-11-09 12:18 ` Bernt Hansen [this message]
2011-11-09 12:29 ` Sebastien Vauban
2011-11-09 12:47 ` Sebastien Vauban
2011-11-09 20:49 ` Sebastien Vauban
2011-11-09 21:00 ` Sebastien Vauban
2011-11-09 13:19 ` Tommy Kelly
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=87y5vpebfz.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.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).