<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Plan on WhyNotHugo</title><link>https://whynothugo.nl/tags/plan/</link><description>Recent content in Plan on WhyNotHugo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 30 Nov 2023 11:12:00 +0800</lastBuildDate><atom:link href="https://whynothugo.nl/tags/plan/posts.xml" rel="self" type="application/rss+xml"/><item><title>Specification and development status for valarmd</title><link>https://whynothugo.nl/journal/2023/11/30/specification-and-development-status-for-valarmd/</link><pubDate>Thu, 30 Nov 2023 11:02:38 +0800</pubDate><guid>https://whynothugo.nl/journal/2023/11/30/specification-and-development-status-for-valarmd/</guid><description>I have made a few mentions to valarmd, a project of mine which is paused for the moment. It is a daemon used to show desktop notifications for alarms in calendar entries. This is its specification. I hope to continue working on it after completing my current work on vdirsyncer.
Specification for valarmd[permalink] The basic usage is:
valarmd --socket /path/to/socket --vdir /path/to/vdir valarmd shall read icalendar components (both events and todos) from a local file-system directory, extracting their respective dates, alarms and summaries.</description></item></channel></rss>