From: JRSS <jarss@protonmail.com>
To: mankoff@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Mark vacation days
Date: Sun, 27 Jan 2019 20:41:36 +0000 [thread overview]
Message-ID: <25cGT-vHP6TRHpUf59QT6DPhIS6TBUAg6PcYJq4Fy6xvPgUCL-SPVnFBGyLY6F31fO2wn6j7PKPouypYiR1qB0mXpOXied-NVG7q7vLfvTY=@protonmail.com> (raw)
In-Reply-To: <87y375g7o1.fsf@geus3064linuxwsm.geus.dk>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
What if you set the category in the function? So the function has something like cond (( or (org-category vacation) (org-category f_event)
(background: red))
I obviously don't know how to write it, but the idea is that the categories are already set in the function. I won't have many, three tops, and I won't change them often -- no need to be fully dynamic.
Sent from ProtonMail mobile
-------- Original Message --------
On Jan 27, 2019, 15:35, Ken Mankoff wrote:
> Hi,
>
> On 2019-01-27 at 12:20 -0800, JRSS <jarss@protonmail.com> wrote...
>> This is a bit over my head still. I'm trying to wrap my head around it.
>>
>> I see what it does (colors day-of-the-week 1 and day-of-the-week-3,
>> which are Monday and Wednesday, red) but not sure how to tie it to a
>> category (so say, category "vacation" would be red).
>>
>> Once I have the function do that, I can go in and change it so that
>> different categories will be different colors.
>
> It's a bit over my head for this use case too. Sorry. When I saw it I thought the use case was a list of holidays, which is easier to implement. You could maintain this list in an easy-to-access format as a variable near where you implement this function. A dynamic list based on tagged Org items is certainly more complicated.
>
> -k.
[-- Attachment #2: Type: text/html, Size: 1560 bytes --]
next prev parent reply other threads:[~2019-01-27 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-27 15:20 Mark vacation days JRSS
2019-01-27 19:27 ` Ken Mankoff
2019-01-27 20:20 ` JRSS
2019-01-27 20:35 ` Ken Mankoff
2019-01-27 20:41 ` JRSS [this message]
2019-02-03 14:49 ` John Lee
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='25cGT-vHP6TRHpUf59QT6DPhIS6TBUAg6PcYJq4Fy6xvPgUCL-SPVnFBGyLY6F31fO2wn6j7PKPouypYiR1qB0mXpOXied-NVG7q7vLfvTY=@protonmail.com' \
--to=jarss@protonmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.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).