3c7dcbadbe
* First stab at adding Python 3.9 dev Travis builds * Dynamically replace Python max version for Python 3.9 beta builds * Fix allow_failures (3.9-dev, not 3.9) and fix Windows find-and-replace command to allow 3.9 * Fix allow_failures to allow all three Python 3.9 builds to fail * Use platform-independent Python script to allow all Python versions for 3.9 builds * Format changes and changing before_install to script for 3.9 builds * Install toml module to make it possible to run version-changing script before install * Properly populate before_install step with Mac and Windows Python 3.9, and remove extraneous unused python key * Add refreshenv to get python3 path included in WIndows * Ensure MacOS pyenv is up to date and attempt to reference Windows python3 directly * Use bash-friendly paths in Windows and check to see exactly what the Python 3.9 executable is * Confirm Python version in Windows and attempt to get pip a different way * Fiddling with Windows python references * Remove Python3.6 references and check for Python directory in root directory * Add Python 3.9 path to Windows build * Remove pip steps that should be unnecessary * Add upgrade pip to Windows Python 3.9 build * Attempt to resolve "access denied" error when upgrading pip on Windows * Use allow_all_python_version TOML script in nightly build instead of sed |
||
|---|---|---|
| .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 your command line. Journals are stored as human readable plain text files - you can put them into a Dropbox folder for instant syncing and you can be assured that your journal will still be readable in 2050, when all your fancy iPad journal applications will long be forgotten.
Optionally, your journal can be encrypted using the 256-bit AES.
Why keep a journal?
Journals aren't just for people who have too much time on their summer vacation. A journal helps you to keep track of the things you get done and how you did them. Your imagination may be limitless, but your memory isn't. For personal use, make it a good habit to write at least 20 words a day. Just to reflect what made this day special, or why you haven't wasted it. For professional use, consider a text-based journal to be the perfect complement to your GTD todo list - a documentation of what and how you've done it.
In a Nutshell
To make a new entry, just type
jrnl yesterday: Called in sick. Used the time cleaning the house and writing my book.
and hit return. yesterday: will be interpreted as a timestamp. Everything
until the first sentence mark (.?!) will be interpreted as the title, 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 cleaning the house and writing my book.
If you just call jrnl, you will be prompted to compose your entry - but you
can also configure jrnl to use your external editor.
For more information, please read our documentation.
Contributors
Maintainers
Our maintainers help keep the lights on for the project. Please thank them if you like jrnl.
- Jonathan Wren (wren)
- Micah Ellison (micahellison)
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.
