Collect your thoughts and notes without leaving the command line.
Find a file
Carl Smedstad 4d99448cdd
Fix compatibility of step-functions matching on multiple lines
In pytest-bdd v8.0.0 it is no longer possible to match based on multiple
lines, which breaks essentially all steps that support docstrings. Solve
this by adding a wrapper-function for each of these instances, that
matches the docstring step, and calls the original function.

So, what used to be:

    @then(parse("the output should match\n{regex}"))
    @then(parse('the output should match "{regex}"'))
    def output_should_match(regex, cli_run):
        ...

Is now:

    @then(parse("the output should match"))
    def output_should_match_docstring(cli_run, docstring):
        output_should_match(docstring, cli_run)

    @then(parse('the output should match "{regex}"'))
    def output_should_match(regex, cli_run):
        ...

There is possibly a way around this that is much better than what I've
done here, but this is a start at least.
2024-11-16 21:19:04 +01:00
.build Add changelog generation workflow to github actions (#1086) 2020-11-21 11:21:19 -08:00
.github Update peter-evans/create-pull-request action to v7 (#1929) 2024-10-19 14:27:25 -07:00
docs Recommend pipx as easiest installation method for all OSes and remove warning about apt (#1889) 2024-06-13 19:34:31 -07:00
docs_theme Force brighter color with XML syntax highlighting (#1943) 2024-10-19 14:28:21 -07:00
jrnl Increment version to v4.2-beta 2024-10-19 22:04:52 +00:00
tests Fix compatibility of step-functions matching on multiple lines 2024-11-16 21:19:04 +01:00
.gitattributes Fix annoying poetry-generated Windows line endings 2021-07-03 15:49:18 -07:00
.gitignore Add flakeheaven_cache/ to gitignore and fix typo in comment (#1731) 2023-05-20 14:57:24 -07:00
.readthedocs.yaml Set new required build fields in the ReadTheDocs config file (#1803) 2023-10-17 08:33:58 -07:00
CHANGELOG.md Update changelog [ci skip] 2024-10-19 22:06:23 +00:00
CODE_OF_CONDUCT.md Update maintainer email (#1515) 2022-06-25 11:51:19 -07:00
CONTRIBUTING.md Update copyright notices for 2023 (#1660) 2023-01-07 13:39:07 -08: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
mkdocs.yml Support mkdocs 1.4.2 and fix its missing breadcrumb (#1691) 2023-02-25 12:16:33 -08:00
package-lock.json Update dependency pa11y-ci to v3.1.0 (#1831) 2024-02-01 19:36:08 -08:00
package.json Update dependency pa11y-ci to v3.1.0 (#1831) 2024-02-01 19:36:08 -08:00
poetry.lock Update dependency xmltodict to v0.14.2 (#1940) 2024-10-19 14:19:03 -07:00
pyproject.toml Increment version to v4.2-beta 2024-10-19 22:04:52 +00:00
README.md Update contributing.md links in documentation (#1726) 2023-04-29 11:57:57 -07:00
SECURITY.md Update maintainer email (#1515) 2022-06-25 11:51:19 -07:00
tasks.py Add config to pa11y to workaround github actions issue (#1933) 2024-10-01 20:28:11 -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.