From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Custom agenda -- running functions, not just setting vars
Date: Wed, 09 Nov 2011 21:49:45 +0100 [thread overview]
Message-ID: <80boslja1i.fsf@somewhere.org> (raw)
In-Reply-To: 80zkg5wkbx.fsf@somewhere.org
Hi Bernt,
> Bernt Hansen wrote:
>> Tommy Kelly <tommy.kelly-ABZRMiVa18FBDgjK7y7TUQ@public.gmane.org> writes:
>> (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.
>
> I don't think that's a bug: this seems to be handled -- see parameter
> `require-timed' in the doc:
The problem is well that, if you force the timegrid even when there is no
timed event to show, you'll always have it.
It's nice for the daily agenda view, where one could want it, with or without
timed event foreseen.
It's much less nice for a block view where you have a couple of sub-agendas
(one with appointments only, one with deadlines only, one with scheduled
entries only: you get the timegrid displayed 3 times).
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-11-09 20:49 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
2011-11-09 12:29 ` Sebastien Vauban
2011-11-09 12:47 ` Sebastien Vauban
2011-11-09 20:49 ` Sebastien Vauban [this message]
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=80boslja1i.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).