From: Adam Porter <adam@alphapapa.net>
To: emacs-orgmode@gnu.org
Subject: Re: specify different agenda item colors for different custom agenda views
Date: Wed, 03 Jan 2018 01:30:18 -0600 [thread overview]
Message-ID: <87bmibv1px.fsf@alphapapa.net> (raw)
In-Reply-To: 871sj8o616.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Rainer Stengele <rainer.stengele@online.de> writes:
>
>> These posts which stay unanswered - either they are too stupid or too
>> complicated?!
>
> AFAIC, questions about the Agenda tend to belong to the second
> category.
Indeed! :)
>> Anybody an idea, a hint?
>
> It may help to know what you have tried so far. For example, how is your
> block configuration, including the settings part (see
> `org-agenda-custom-commands' docstring)?
>
> Note that it might not be possible to achieve what you want.
Probably the way to do it would be to wrap the agenda code which
operates on certain files, and let-bind the org-agenda-done face around
that code depending on which file it is. That would probably require
copying the function in question and overriding it with advice.
Certainly doable (on first glance, anyway), but not easy for someone
unfamiliar with elisp or the agenda code.
I would guess that a more general solution, which could bind certain
variables to certain values depending on which file the agenda is being
constructed from, could be useful in other ways as well. It might be
possible to integrate this with org-agenda-custom-commands, or in a
customizeable variable mapping files to lists of variables, to make it
fairly straightforward to use.
prev parent reply other threads:[~2018-01-03 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 13:32 specify different agenda item colors for different custom agenda views Rainer Stengele
2018-01-02 11:03 ` Rainer Stengele
2018-01-02 11:26 ` Nicolas Goaziou
2018-01-03 7:30 ` Adam Porter [this message]
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=87bmibv1px.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).