1a67fd5dec
* update pytest-bdd to 6.0 * update lock file * fix first test (inject command fixture to request) * fix some more tests * fix cli_run fixture * fix password fixture * Remove unused import * Fix greedy should_or_should_not parsing problems while also consolidating its parse/transformation-to-bool code * Prevent greedy matching in "we run" by using regular expression lookahead * Add missing "Outline" in scenario outlines with examples * Split "we use the config" and "we use no config" so pytest won't try to consume config_file as a fixture * Fix missing ShouldOrShouldNot * Formatting * fix get_fixture function * change output of failing test to be a little more useful * update lock file * update type builder to for should/should not to be in it's own file, rename some vars for readability * add parse-type new dev/testing dependency * update lock file --------- Co-authored-by: Jonathan Wren <jonathan@nowandwren.com> |
||
|---|---|---|
| .build | ||
| .github | ||
| docs | ||
| docs_theme | ||
| jrnl | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| issue_template.md | ||
| LICENSE.md | ||
| mkdocs.yml | ||
| package-lock.json | ||
| package.json | ||
| poetry.lock | ||
| pyproject.toml | ||
| README.md | ||
| readthedocs.yml | ||
| SECURITY.md | ||
| tasks.py | ||
jrnl
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:
- 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.
