schedrem 1.0.0

A cross-platform task scheduler and reminder configured in YAML.

Schedrem

A cross-platform task scheduler and reminder configured in YAML.

How it Works

Schedrem is a Python package that provides a tool for scheduling tasks and setting reminders.

As a resident program, it monitors changes in the configuration file, triggers tasks to execute commands or display message boxes as reminders. It also validates the configuration format every time the file is saved.

The configuration file, which is a YAML file, is easy to read and write. You can use your favorite text editor to configure your schedules.

Audible alarm using a sound file (currently WAV format only) is available.

Installation

Python 3.11 or later is required.

From PyPI

Install from PyPI using pip:

python -m pip install -U schedrem

From Source Using Pip

git clone https://github.com/hikyae/schedrem
cd schedrem
python -m pip install -e .

From AUR

There also exists an AUR package.

Install from AUR using a helper such as yay or paru:

yay -S schedrem

paru -S schedrem

From Source Using Makepkg

git clone https://aur.archlinux.org/packages/schedrem
cd schedrem
makepkg -si

Configuration

Schedrem searches for the configuration file in the order specified below and uses the first one that is found. The actual path depends on the platform and environment variables.

The file format must be YAML. Use your favorite text editor to edit the file.

Schedrem will automatically detect the changes you've made to the configuration file. If there is an error in the file, a message box will pop up and it will try to tell you the reason. Please fix the file and save it, then close the message box. Otherwise, the message box will keep popping up.

Note that there is no configuration file used to configure defaults for command-line parameters such as --config or --debug.

Path Specified by Command-Line Parameter

You can set the file path by passing it as a command-line parameter:

schedrem --config path/to/config

Default Paths for Linux/macOS

• ${XDG_CONFIG_HOME}/schedrem/config.yml
• ${XDG_CONFIG_HOME}/schedrem/config.yaml
• ${HOME}/.config/schedrem/config.yml
• ${HOME}/.config/schedrem/config.yaml

Default Paths for Windows

• %USERPROFILE%\.config\schedrem\config.yml
• %USERPROFILE%\.config\schedrem\config.yaml
• %APPDATA%\schedrem\config.yml
• %APPDATA%\schedrem\config.yaml

Examples

Please refer to the examples directory in this repository.

Structure

Schedules

All the schedules should be listed here.

Each schedule is an item in the list of schedules, denoted by a leading hyphen (-). It can have description (abbreviated as desc), time, wait, and an action that consists of message (abbreviated as msg), yesno, command (abbreviated as cmd), sound, and font. Basically, every key is optional with a few exceptions. If there is no action specified out of message, yesno, or command, an error occurs.

schedules:
  - message: This is the simplest schedule that is triggered every minute.

  - description: This is a more complex schedule that is triggered every day at 6 o'clock.
    time:
      hour: 6
      minute: 0
    message: Good morning.

Time

The time specification is similar to cron, but more readable.

Specify integers or a list of integers for year, month, day, hour, minute to schedule the date(s). Specify string or a list of strings for weekday (abbreviated as dow) to schedule the day(s) of the week.

If you omit any of them, then the schedule is triggered at any of the times within that range. This is similar to using * in a crontab.

If you don't specify the time, then the task is triggered every minute.

Wait

The time to wait before triggering the task. The task won't be triggered until the specified time has elapsed.

You can specify integers for year, month, day, hour, minute, but only year is mandatory.

Action

The "action" is a conceptual term, not a configuration file key. The configuration file consists of the following keys: message (abbreviated as msg), yesno, command (abbreviated as cmd), sound, and font.

The structure of these keys is as follows:

• message: A string to show in a message box with an OK button.
• yesno: A string to show in a message box asking for a Yes or No response. If the user presses "Yes", the command will be executed.
• command: A string of an arbitrary shell command.
• sound: A string of the path to a sound file to play, or a boolean (true/false, yes/no, on/off) to set whether the default sound should be played while showing a message box. The only acceptable sound file format is WAV.
• font: A string specifying the font family and font size to use in the message box, in the format <font family> <font size>, for example, "Cica 40".

Optional global settings

These are optional settings that affect all schedules.

• disabled: A boolean (true/false, yes/no, on/off) to set whether Schedrem should run or not. Set this to true when you want Schedrem to stop waiting for all schedules or when you want all running tasks, including all visible message boxes, to be killed. The default value is false.

  disabled: true
  

• weekdaynames: A list of lists of strings to set the names for the days of the week. They start from Monday and are case-insensitive. The default value is [mon, tue, wed, thu, fri, sat, sun].

  weekdaynames:
    - [mon, tue, wed, thu, fri, sat, sun]
    - [月, 火, 水, 木, 金, 土, 日]
  
  schedules:
    - description: Time to take out the burnable trash
      time:
        hour: 7
        minute: 50
        weekday: 月
      message: 燃えるゴミを捨てる
  

• font: A string specifying the font family and font size to use in the message box, in the format <font family> <font size>, for example, "Cica 40". If you set this value outside of schedules, each action will use this font setting unless the font is explicitly set within the action. The default value is Arial 19.

  font: Arial 70
  
  schedules:
    - description: You will see the huge text every minute
      message: HUGE
  

• aliases: Thanks to the YAML specification, it is possible to make aliases for values for schedules. The naming of the key aliases is not mandatory.

aliases:
  - &workdays [mon, tue, wed, thu, fri]
  - &friday13th
    day: 13
    dow: fri

schedules:
  - desc: Time to go
    time:
      hour: 8
      minute: 0
      dow: *workdays
    msg: Go to work

  - desc: Beware of unluckiness in the morning
    time:
      hour: 8
      minute: 0
      <<: *friday13th
    msg: Good morning, and beware!

Usage

First, you need to put your configuration file into one of the places described in the Configuration section.

Try starting Schedrem from a terminal to check for any errors:

schedrem --debug

This starts Schedrem in the foreground with the debug option, displaying configuration information if there are no issues. If no errors appear, you're good to proceed. You can stop the process by pressing <Ctrl>+C.

Set the config path if you put it besides the defaults:

schedrem --config path/to/config

Auto-starting

On Linux, to start Schedrem as a background program in a stand-alone window manager, add the following line to your startup script, such as ~/.xinitrc:

schedrem &

The trailing ampersand "&" means that the program should run in the background. To stop Schedrem, just type pkill schedrem.

In a desktop environment (such as GNOME, KDE, Xfce, MATE, Cinnamon, etc.), you can simply add Schedrem to the list of autostarted applications without the trailing "&".

On Windows, you need to create a shortcut for the command:

1. Open the Startup Folder:
   • Press Win + R, type shell:startup, and press Enter.
2. Create a New Shortcut:
   • Right-click inside the Startup folder, then select New > Shortcut.
3. Enter the Shortcut Target:
   • In the Location field, use PowerShell to run the command in hidden mode. Enter this command:

     powershell -windowstyle hidden -command "schedrem"
     

On macOS, you need to put a plist file as ~/Library/LaunchAgents/com.yourusername.schedrem.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.yourusername.schedrem</string>
    <key>ProgramArguments</key>
    <array>
        <string>schedrem</string> <!-- Assuming "schedrem" is accessible via PATH -->
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>

Tips

• There is a command-line option --action that can receive a JSON string as an action. This option is used internally for executing tasks. You can also manually execute it as a command.

schedrem --action '{"msg":"test","sound":true}'

• Unlike cron, you can configure the time with constraints on both the day of the month and the day of the week.