From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org, Jean Louis <bugs@gnu.support>
Subject: Re: Emacs Calendar - Removing holidays
Date: Sat, 21 Nov 2020 21:16:14 +0100 [thread overview]
Message-ID: <trinity-672f29a8-9dd2-481f-804f-a082085a5912-1605989774723@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87wnye1ohl.fsf@web.de>
---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy
> Sent: Saturday, November 21, 2020 at 8:47 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org, "Jean Louis" <bugs@gnu.support>
> Subject: Re: Emacs Calendar - Removing holidays
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > Could you give some examples of "diary symbolic expressions" and how
> > they would be useful for setting work dates.
>
> The Emacs diary supports symbolic expressions that return a boolean
> value depending on the free variable `date'. Functions that can be used
> in such expressions are described in the manual. As a special non-nil
> value a string describing the event, and a cons (mark . string)
> including a mark type for the calendar are allowed. See
> `diary-lunar-phases' for an example.
>
> The good thing is that anything Elisp supports is allowed to be used in
> such expressions. The bad thing is that not so super many are
> predefined.
>
> > I am particularly interested in marking dates that are available for
> > deadlines, meetings. And another for those already set with
> > deadlines, meetings, etc.
>
> For org? For that you would need to have a predicate that would tell
> whether a given `date' is available or not. I guess someone on the
> org-mode user list might have an idea how to implement that. Maybe
> reusing some of the agenda code. Depending on how your meetings
> etc. are specified.
Yes, for org.
> Regards,
>
> Michael.
>
>
next prev parent reply other threads:[~2020-11-21 20:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 13:56 Emacs Calendar - Removing holidays Christopher Dimech
2020-11-19 14:02 ` Christopher Dimech
2020-11-19 14:09 ` Jean Louis
2020-11-19 15:21 ` Christopher Dimech
2020-11-19 15:32 ` Jean Louis
2020-11-19 15:37 ` Christopher Dimech
2020-11-19 15:43 ` Christopher Dimech
2020-11-19 16:05 ` Jean Louis
2020-11-19 16:38 ` Christopher Dimech
2020-11-19 16:26 ` Michael Heerdegen
2020-11-19 16:46 ` Christopher Dimech
2020-11-19 17:21 ` Christopher Dimech
2020-11-19 18:58 ` Michael Heerdegen
2020-11-19 19:06 ` Jean Louis
2020-11-19 19:40 ` Michael Heerdegen
2020-11-19 19:52 ` Jean Louis
2020-11-19 20:17 ` Christopher Dimech
2020-11-19 20:50 ` Michael Heerdegen
2020-11-19 20:59 ` Christopher Dimech
2020-11-19 21:11 ` Christopher Dimech
2020-11-21 19:47 ` Michael Heerdegen
2020-11-21 20:16 ` Christopher Dimech [this message]
2020-11-19 20:24 ` Michael Heerdegen
2020-11-19 20:36 ` Christopher Dimech
2020-11-19 19:52 ` Christopher Dimech
2020-11-19 20:09 ` Jean Louis
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-672f29a8-9dd2-481f-804f-a082085a5912-1605989774723@3c-app-mailcom-bs11 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).