ebba342779
* Support Python 3.9 release in build instead of using 3.9 beta * Revert Linux and Mac 3.9 definitions since release versions are not working on either * Run poetry update * Try out Python 3.10 support on all platforms with allow_failures on * Adding c:\Python310 path reference for Python 3.10 Windows build * Clean up unnecessary TOML modification in 3.9 build and always upgrade pyenv in Mac builds * Clean up unnecessary before_install step on Mac and change 3.9-dev->3.9 definition on Linux * Reverting Linux Python version to 3.9-dev so that it will run |
||
|---|---|---|
| .build | ||
| .github | ||
| docs | ||
| features | ||
| jrnl | ||
| tests | ||
| .gitattributes | ||
| .github_changelog_generator | ||
| .gitignore | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| issue_template.md | ||
| LICENSE.md | ||
| Makefile | ||
| mkdocs.yml | ||
| poetry.lock | ||
| pyproject.toml | ||
| README.md | ||
| readthedocs.yml | ||
jrnl 
To get help, submit an issue on Github.
jrnl is a simple journal application for the command line.
Its goal is to facilitate the rapid creation and viewing of journal entries. It is flexible enough to support different use cases and organization strategies. It is powerful enough to search through thousands of entries and display, or "filter," only the entries you want to see.
jrnl includes support for 128-bit AES
encryption using
cryptography.Fernet.
In a Nutshell
To make a new entry, just enter
jrnl yesterday: Called in sick. Used the time to clean the house and write my
book.
yesterday: is interpreted by jrnl as a timestamp. Everything until the
first sentence ending (either ., ?, or !) is interpreted as the title, and
the rest as the body. In your journal file, the result will look like this:
[2012-03-29 09:00] Called in sick.
Used the time to clean the house and write my book.
Entering jrnl without any arguments launches an external editor where you can
write your entry. jrnl will generate a time stamp for the entry after you save
and close the editor window.
For more information, please read the documentation.
Contributors
Maintainers
Our maintainers help keep the lights on for the project:
- Jonathan Wren (wren)
- Micah Ellison (micahellison)
Please thank them if you like jrnl!
Code Contributors
This project is made with love by the many fabulous people who have contributed.
jrnl couldn't exist without each and every one of you!
If you'd also like to help make jrnl better, please see our contributing
documentation.
Financial Backers
Another way show support is through direct financial contributions. These funds
go to covering our costs, and are a quick way to show your appreciation for
jrnl.
Become a financial contributor and help us sustain our community.
