Collect your thoughts and notes without leaving the command line.
Find a file
Jonathan Wren ecb4562c29 Make sure testing cleans up after itself (#940)
This adds the ability to run commands in a cache directory without the
test writer knowing where the cache directory is located. This will let
us expand later if we want to start using system temp folders, without
having to rewrite any of our tests.

* clean up extra directories after running behave
* clean up white space issues
* move repeated code into function
* clean up behave code for creating cache directories
* Fix for windows shell parsing in our test suite

Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
2020-05-06 18:13:36 -07:00
.build Stop multipe changelog generators from crashing into each other 2020-04-10 11:51:56 -07:00
.github GitHub Pull Request Template Update (#927) 2020-05-02 12:06:23 -07:00
docs Change github new issue link to issue template chooser (#936) 2020-05-05 12:51:03 -07:00
features Make sure testing cleans up after itself (#940) 2020-05-06 18:13:36 -07:00
jrnl Prevent filtered delete from deleting journal (#935) 2020-05-06 13:47:39 -07:00
.github_changelog_generator update changelog generator settings to be less verbose, fix links 2020-04-10 11:51:56 -07:00
.gitignore Ensure exported entries end in a newline for Markdown and YAML exporters (#908) 2020-04-18 12:35:46 -07:00
.travis.yml Update Windows Python versions (#910) 2020-04-18 12:35:46 -07:00
CHANGELOG.md Updating changelog [ci skip] 2020-05-06 20:55:08 +00:00
CODE_OF_CONDUCT.md Update the code of conduct (#913) 2020-04-18 12:35:46 -07:00
CONTRIBUTING.md Update and reorganize CONTRIBUTING (#885) 2020-04-10 11:51:56 -07:00
LICENSE.md Upgrade license to GPLv3 (#918) 2020-04-18 13:31:25 -07:00
Makefile update makefile to match pipeline better 2020-04-18 13:58:57 -07:00
mkdocs.yml Update site description (#841) 2020-04-10 11:51:56 -07:00
poetry.lock Allow most recent pytz version and update dependencies (#937) 2020-05-05 12:49:24 -07:00
pyproject.toml Allow most recent pytz version and update dependencies (#937) 2020-05-05 12:49:24 -07:00
README.md Clean up readme file (#924) 2020-04-25 13:15:55 -07:00

jrnl Build Status Downloads Version

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.

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.