Collect your thoughts and notes without leaving the command line.
Find a file
2020-04-10 11:51:55 -07:00
.github [GH-607] Add stalebot config 2020-04-10 11:51:55 -07:00
docs Add instructions for VS Code (#544) 2018-06-26 11:28:23 -07:00
features #5 Removing DayOne tests 2020-04-10 11:51:55 -07:00
jrnl #6 allowing template interpreter to interpret common Python commands 2020-04-10 11:51:55 -07:00
.gitignore Update .gitignore 2015-04-14 15:58:56 -06:00
.travis.yml update python version for ci 2020-04-10 11:51:55 -07:00
CHANGELOG.md Doc changes 2014-09-12 14:28:03 -07:00
CODE_OF_CONDUCT.md [GH-602] Add a code of conduct file (rather than adding to contributing) 2020-04-10 11:51:55 -07:00
CONTRIBUTING.md [GH-598] Changing references from jrnl-plus back to jrnl and ensuring the URLs are valid (except build badge) 2020-04-10 11:51:55 -07:00
LICENSE Mark jrnl as 3.4 compatible 2014-05-22 14:18:15 -07:00
Makefile New make options 2014-06-30 11:14:25 +02:00
MANIFEST.in Manifest update 2014-07-27 12:43:26 +09:00
README.md [GH-605] pointing to a more comprehensive GitHub issue re DayOne 2020-04-10 11:51:55 -07:00
setup.py Fix behave tests by adding asteval dependency (#469) 2017-03-09 11:56:44 -08: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 angsty teenagers and 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, 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 to clean the house and spent 4h on 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 to clean the house and spent 4h on 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.

Known Issues

jrnl used to support integration with Day One, but no longer supports it since Day One 2 was released with a different backend. See the GitHub issue for more information.

Authors

Current maintainers:

Original maintainer: