habitual is a simple application to send reminders for things which are on a fixed, repeated schedule.
You can tell habitual which application to use using --exec. The default is notify-send. The application should take one argument – the name of the reminder. If you need to pass more, create a wrapper script and call that. The default is notify-send, but you may want to send to other services like Pushbullet or Pushover, for example.
Configuration
Reminders are is typically stored at ~/.config/habitual/habitual, and are automatically reloaded when the file is changed. The format is like so:
cron|name
For example, here’s how someone’s reminders might look:
0 0 10-20 ? * * *|Drink water 0 0 1 ? * * *|Start winding down
1 maintainer
Metadata
1 maintainer
Release files for habitual 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| habitual-0.1.1.tar.gz | 2.7 kB | Without provenance | Details |
Release files / habitual-0.1.1.tar.gz
| Download URL | habitual-0.1.1.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
683529829ac36c4dd62dec2379577f0631e8655a8ab4e3246418abe3e6fb150c
|
|
BLAKE2b-256 checksum How to use checksums |
f54e73eb49449b4733fc46f4d11ddd16def920fd9a211fb997fe7fd38a735d83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.8.2
|
Security for habitual 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
