Collect your thoughts and notes without leaving the command line.
Find a file
Jonathan Wren f53110c69b
Rework how all output and messaging works in jrnl (#1475)
* fix missed statement from last PR
* replace print statement for adding an entry to a journal
* clean up linting and format
* change print statement over to new print_msg function
* make print_msg always print to stderr
* change print statement over to new print_msg function
* update importer to use new message function
* update yaml format to use new message function
* code cleanup
* update yaml format to use new message function
* update yaml format to use new exception handling
* update Journal class to use new message function
* update install module to use new message function
* update config module to use new message function
* update upgrade module to properly use new message and exception handling
* fix typo
* update upgrade module to use new message handling
* update welcome message to use new handling
* update upgrade module to use new message handling
* update upgrade module journal summaries to use new message handling
* take out old code
* update upgrade module to use new message handling
* update upgrade module to use new message handling
* update more modules to use new message handling
* take out old comment
* update deprecated_cmd to use new message handling
* update text_exporter with new message handling, get rid of old color constants
* get rid of hardcoded text
* whitespace changes
* rework MsgType into MsgStyle so messages can have different styles
* add comment
* Move around code to separate concerns of each function a bit more
* update create_password and yesno prompt functions for new messaging
* fix missing newline for keyboard interrupts
* fix misc linting
* fix bug with panel titles always showing 'error' after one error
* fix missing import
* update debug output after uncaught exception
* update exception for new exception handling
* rewrite yesno function to use new centralized messages
* reduce the debug output slightly
* clean up print_msgs function
* clean up create_password function
* clean up misc linting
* rename screen_input to hide_input to be more clear
* update encrypted journal prompt to use new messaging functionality
* fix typo in message key
* move rich console into function so we can mock properly
* update password mock to use rich console instead of getpass
* add more helpful output to then step
* fix test by updating expected output
* update message to use new functionality
* rework mocks in test suite for new messaging functionality
* fix linting issue
* fix more tests
* fix more tests
* fix more tests
* fix more tests
* fix merge bug
* update prompt_action_entries to use new messaging functionality
* Add new input_method "type"
  This does the same thing as input_method "pipe" but is more clear what
  it's doing (typing text into the builtin composer)
* get rid of old commented code
* get rid of unused code
* move some files around

Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
2022-06-11 13:32:11 -07:00
.build Add changelog generation workflow to github actions (#1086) 2020-11-21 11:21:19 -08:00
.github Drop support for Python 3.7 and 3.8 (#1412) 2022-02-12 14:07:56 -08:00
docs Create folder if config ends with (back)slash (#1492) 2022-06-04 13:20:51 -07:00
docs_theme Document --change-time in web-based docs' command line reference (#1471) 2022-05-21 14:13:24 -07:00
jrnl Rework how all output and messaging works in jrnl (#1475) 2022-06-11 13:32:11 -07:00
tests Rework how all output and messaging works in jrnl (#1475) 2022-06-11 13:32:11 -07:00
.gitattributes Fix annoying poetry-generated Windows line endings 2021-07-03 15:49:18 -07:00
.gitignore Tidy up git ignore (#1414) 2022-02-17 15:38:11 -08:00
CHANGELOG.md Update changelog [ci skip] 2022-06-11 18:41:17 +00:00
CODE_OF_CONDUCT.md Update the code of conduct (#913) 2020-04-18 12:35:46 -07:00
CONTRIBUTING.md Migrate contributing.md to docs site (#1266) 2021-10-16 15:21:49 -07:00
issue_template.md Clean up templates and issues (#954) 2020-05-23 15:58:04 -07:00
LICENSE.md Upgrade license to GPLv3 (#918) 2020-04-18 13:31:25 -07:00
Makefile Add more steps to pytest, fully remove behave (#1347) 2021-10-09 12:10:08 -07:00
mkdocs.yml Add reference documentation to docs site and separate out "Tips and Tricks" and "External Editors" from "Recipes" (#1332) 2022-02-05 12:59:20 -08:00
poetry.lock Bump pyxdg from 0.27 to 0.28 (#1497) 2022-06-11 11:39:09 -07:00
pyproject.toml Rework how all output and messaging works in jrnl (#1475) 2022-06-11 13:32:11 -07:00
README.md Fix splash image for PyPi (I hope) and add changelog badge (#1339) 2021-09-18 12:31:45 -07:00
readthedocs.yml Pin jinja2 in docs requirements to keep readthedocs builds from failing (#1439) 2022-03-26 11:48:41 -07:00
SECURITY.md Add first draft of security.md (#1299) 2021-07-17 12:01:59 -07:00

jrnl Testing Downloads Version Homebrew Gitter Changelog

To get help, submit an issue on Github.

jrnl is a simple journal application for the command line.

You can use it to easily create, search, and view journal entries. Journals are stored as human-readable plain text, and can also be encrypted using AES encryption.

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.

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 the 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.