.build/allow_all_python_version.py

@@ -1,8 +0,0 @@
-import toml
-
-pyproject = toml.load("pyproject.toml")
-
-pyproject["tool"]["poetry"]["dependencies"]["python"] = "*"
-
-with open("pyproject.toml", "w") as toml_file:
-    toml.dump(pyproject, toml_file)

.gitattributes

@@ -1,4 +0,0 @@
-*.journal text eol=lf
-*.feature text eol=lf
-poetry.lock text eol=lf
-pyrpoject.toml text eol=lf

.github/FUNDING.yml

@@ -1,12 +0,0 @@
-# These are supported funding model platforms
-
-github: # Replace with up to 4 GitHub Sponsors-enabled usernames e.g., [user1, user2]
-patreon: # Replace with a single Patreon username
-open_collective: jrnl
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: # Replace with a single IssueHunt username
-otechie: # Replace with a single Otechie username
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -1,74 +0,0 @@
-name: Bug Report
-description: Create a report to help us improve
-title: "Bug Report"
-labels: [ ":new:", "bug" ]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        # Bug Report
-        Hello, and thank you for reporting an issue!
-
-        Please fill out the points below, as it will make our process much easier.
-
-  - type: textarea
-    id: diagnostic
-    attributes:
-      label: Diagnostic output
-      description: Run `jrnl --diagnostic` and paste the output below
-      placeholder: Paste output here
-    validations:
-      required: true
-
-  - type: textarea
-    id: current-behavior
-    attributes:
-      label: Current Behavior
-      description: Please put a short description of what is currently happening.
-      placeholder: Tell us what is happening
-    validations:
-      required: true
-
-  - type: textarea
-    id: expected-behavior
-    attributes:
-      label: Expected Behavior
-      description: Please write a short description of what you would expect to happen
-      placeholder: Tell us what should be happening
-    validations:
-      required: true
-
-  - type: textarea
-    id: repro-steps
-    attributes:
-      label: Repro Steps
-      description: |
-        Provide the steps to reproduce the problem.
-
-        Please be as precise as possible, since more info will let us help you faster.
-      placeholder: Repro steps
-    validations:
-      required: true
-
-  - type: textarea
-    id: debug-output
-    attributes:
-      label: Debug output
-      description: |
-        Please provide the output of your command with the `--debug` flag on.
-      placeholder: "example: `jrnl --debug lorem ipsum`"
-    validations:
-      required: true
-
-  - type: textarea
-    id: other-info
-    attributes:
-      label: Other Information
-      description: >
-        Is there anything else we should know?
-
-        (e.g. more detailed explanation, stacktraces, related
-        issues, suggestions how to fix, links for us to have context, eg.
-        stackoverflow, gitter, etc)
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +0,0 @@
-blank_issues_enabled: false

.github/ISSUE_TEMPLATE/documentation.yaml

@@ -1,41 +0,0 @@
-name: Documentation Change
-description: Request or report any updates to our documentation (https://jrnl.sh)
-title: Documentation Change
-labels: [ ":new:", "documentation" ]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        # Documentation Change
-        Hello, and thank you for reporting an issue!
-
-        Please fill out the points below, as it will make our process much easier.
-
-  - type: textarea
-    id: affected-pages
-    attributes:
-      label: Affected Page(s)
-      description: >
-        Please tell us which page, or pages, from the documentation site
-        (https://jrnl.sh) are affected in this issue
-      placeholder: "example: https://jrnl.sh/en/stable/overview"
-    validations:
-      required: true
-
-  - type: textarea
-    id: what-could-be-better
-    attributes:
-      label: What Could Be Better?
-      description: >
-        Please write a short description of what you hope can be clarified or
-        further explained.
-    validations:
-      required: true
-
-  - type: textarea
-    id: other-info
-    attributes:
-      label: Other Information
-      description: Is there anything else we should know that might be helpful?
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -1,43 +0,0 @@
-name: Feature Request
-description: Suggest an idea for jrnl
-title: "Feature Report"
-labels: [ ":new:", "enhancement" ]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        # Feature Request
-        Hello, and thank you for reporting an issue!
-
-        Please fill out the points below, as it will make our process much easier.
-
-  - type: textarea
-    id: user-case
-    attributes:
-      label: Use Case/Motivation
-      description: What is the motivation / use case for changing the behavior?
-      placeholder: Tell us about your idea
-    validations:
-      required: true
-
-  - type: textarea
-    id: example-usage
-    attributes:
-      label: Example Usage
-      description: Please provide examples of the usage you would like to see.
-      placeholder: e.g `jrnl --new-flag="super cool new feature"`
-    validations:
-      required: true
-
-  - type: textarea
-    id: other-info
-    attributes:
-      label: Other Information
-      description: >
-        Is there anything else we should know?
-
-        (e.g. more detailed explanation, stacktraces, related
-        issues, suggestions how to fix, links for us to have context, eg.
-        stackoverflow, gitter, etc)
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/support_request.yaml

@@ -1,54 +0,0 @@
-name: Support Request
-description: Get help with jrnl
-title: Support Request
-labels: [ ":new:", "support" ]
-body:
-  - type: markdown
-    attributes:
-      value: |
-        # Support Request
-        Hello, and thank you for reporting an issue!
-
-        Please fill out the points below, as it will make our process much easier.
-
-  - type: textarea
-    id: diagnostic
-    attributes:
-      label: Diagnostic output
-      description: Run `jrnl --diagnostic` and paste the output below
-      placeholder: Paste output here
-    validations:
-      required: true
-
-  - type: textarea
-    id: current-behavior
-    attributes:
-      label: What are you trying to do?
-      description: Please put a short description of what is happening.
-      placeholder: Tell us what is happening
-    validations:
-      required: true
-
-  - type: textarea
-    id: tried
-    attributes:
-      label: What have you tried?
-      description: >
-        Have you tried anything to fix the problem? This can help give us more
-        information to help you with.
-      placeholder: Tell us what should be happening
-    validations:
-      required: true
-
-  - type: textarea
-    id: other-info
-    attributes:
-      label: Other Information
-      description: >
-        Is there anything else we should know?
-
-        (e.g. more detailed explanation, stacktraces, related
-        issues, suggestions how to fix, links for us to have context, eg.
-        stackoverflow, gitter, etc)
-    validations:
-      required: false

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,24 +0,0 @@
-<!--
-Thank you for wanting to contribute!
-
-Please fill out this description, and the checklist below.
-
-Here are some key points to include in your description:
-- What is this new code intended to do?
-- Are there any related issues?
-- What is the motivation for this change?
-- What is an example of usage, or changes to config files? (if applicable)
--->
-
-### Checklist
-
-- [ ] I have read the [contributing doc](https://github.com/jrnl-org/jrnl/blob/develop/docs/contributing.md).
-- [ ] I have included a link to the relevant issue number.
-- [ ] I have checked to ensure there aren't other open [pull requests](../pulls)
-  for the same issue.
-- [ ] I have written new tests for these changes, as needed.
-<!--
-NOTE: Your PR may not be reviewed if there are any failing tests. You can run
-tests locally with `poe test` (see the contributing doc if you need help with
-`poe`), or use our automated tests after you submit your PR.
--->

.github/actionlint-matcher.json

@@ -1,17 +0,0 @@
-{
-  "problemMatcher": [
-    {
-      "owner": "actionlint",
-      "pattern": [
-        {
-          "regexp": "^(?:\\x1b\\[\\d+m)?(.+?)(?:\\x1b\\[\\d+m)*:(?:\\x1b\\[\\d+m)*(\\d+)(?:\\x1b\\[\\d+m)*:(?:\\x1b\\[\\d+m)*(\\d+)(?:\\x1b\\[\\d+m)*: (?:\\x1b\\[\\d+m)*(.+?)(?:\\x1b\\[\\d+m)* \\[(.+?)\\]$",
-          "file": 1,
-          "line": 2,
-          "column": 3,
-          "message": 4,
-          "code": 5
-        }
-      ]
-    }
-  ]
-}

.github/actions/run_tests/action.yaml

@@ -1,46 +0,0 @@
-name: run jrnl tests
-description: Runs all jrnl tests on multiple platforms
-inputs:
-  cache-string:
-    description: 'Cache string secret. Change to bust the cache'
-    required: true
-runs:
-  using: "composite"
-  steps:
-  - run: git config --global core.autocrlf false
-    shell: bash
-
-  - name: Set up Python ${{ matrix.python-version }}
-    uses: actions/setup-python@v5
-    with:
-      python-version: ${{ matrix.python-version }}
-      allow-prereleases: true
-
-  - name: Capture full Python version in env
-    run: echo "PYTHON_FULL_VERSION=$(python --version)" >> $GITHUB_ENV
-    shell: bash
-
-  - name: poetry cache # Change CACHE_STRING secret to bust the cache
-    uses: actions/cache@v4
-    with:
-      path: .venv
-      key: ${{ runner.os }}-${{ hashFiles('poetry.lock') }}-${{ env.PYTHON_FULL_VERSION }}-${{ inputs.cache-string }}
-
-  - name: Install dependencies
-    run: |
-      echo '::group::poetry'
-      pip --disable-pip-version-check install poetry
-      poetry config --local virtualenvs.in-project true
-      echo '::endgroup::'
-
-      echo '::group::Other dependencies'
-      poetry sync
-      echo '::endgroup::'
-
-      echo 'DEPS_INSTALLED=true' >> $GITHUB_ENV
-    shell: bash
-
-  - name: Linting & Testing
-    if: ${{ env.DEPS_INSTALLED == 'true' }}
-    run: poetry run poe test
-    shell: bash

.github/lock.yml

@@ -1,39 +0,0 @@
-# Configuration for Lock Threads - https://github.com/dessant/lock-threads-app
-
-# Number of days of inactivity before a closed issue or pull request is locked
-daysUntilLock: 90
-
-# Skip issues and pull requests created before a given timestamp. Timestamp must
-# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
-skipCreatedBefore: false
-
-# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
-exemptLabels: []
-
-# Label to add before locking, such as `outdated`. Set to `false` to disable
-lockLabel: ':lock:'
-
-# Comment to post before locking. Set to `false` to disable
-lockComment: >
-  This thread has been automatically locked since there has not been
-  any recent activity after it was closed. Please open a new issue for
-  related bugs. You can link back here from your new issue to continue
-  the conversation.
-
-# Assign `resolved` as the reason for locking. Set to `false` to disable
-setLockReason: true
-
-# Limit to only `issues` or `pulls`
-# only: issues
-
-# Optionally, specify configuration settings just for `issues` or `pulls`
-# issues:
-#   exemptLabels:
-#     - help-wanted
-#   lockLabel: outdated
-
-# pulls:
-#   daysUntilLock: 30
-
-# Repository to extend settings from
-# _extends: repo

.github/renovate.json

@@ -1,14 +0,0 @@
-{
-  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "extends": [
-    "config:base"
-  ],
-  "schedule": [ "at any time" ],
-  "prConcurrentLimit": 10,
-  "prHourlyLimit": 10,
-  "reviewers": [
-    "wren",
-    "micahellison"
-  ],
-  "labels": [ "packaging" ]
-}

.github/stale.yml

@@ -1,17 +0,0 @@
-# Number of days of inactivity before an issue becomes stale
-daysUntilStale: 60
-# Number of days of inactivity before a stale issue is closed
-daysUntilClose: 7
-# Issues with these labels will never be considered stale
-exemptLabels:
-  - ':pushpin:'
-  - critical
-# Label to use when marking an issue as stale
-staleLabel: stale
-# Comment to post when marking an issue as stale. Set to `false` to disable
-markComment: >
-  This issue has been automatically marked as stale because it has not had
-  recent activity. It will be closed if no further activity occurs. Thank you
-  for your contributions.
-# Comment to post when closing a stale issue. Set to `false` to disable
-closeComment: false

.github/workflows/changelog.yaml

@@ -1,170 +0,0 @@
-# Copyright © 2012-2023 jrnl contributors
-# License: https://www.gnu.org/licenses/gpl-3.0.html
-
-name: Changelog
-
-on:
-  push:
-    branches:
-      - develop
-    tags:
-      - 'v*'
-
-jobs:
-  generate:
-    if: >
-      ! contains(github.event.head_commit.message, '[ci skip]') &&
-      ! (
-        startsWith(github.event.head_commit.message, 'Increment version to v') &&
-        startsWith(github.ref, 'refs/heads/')
-      )
-    runs-on: ubuntu-latest
-
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          token: ${{ secrets.JRNL_BOT_TOKEN }}
-
-      - name: Check branch for new commits, and env vars
-        run: |
-          echo "::group::git fetch origin --tags --force"
-          git fetch origin --tags --force
-          echo "::endgroup::"
-
-          TAG_REGEX='include-all'
-          echo "::debug::GITHUB_REF: $GITHUB_REF"
-          BRANCH="${GITHUB_REF##*/}"
-
-          if [[ $GITHUB_REF =~ ^refs/tags/ ]]; then
-            # This is a tag build (i.e. a release)
-            echo '::debug::Release build'
-            if [[ ! $BRANCH =~ ^v[0-9]+(\.[0-9]+){1,2}(-(alpha|beta)([0-9]+)?)?$ ]]; then
-              echo "::error::Invalid tag format: ${BRANCH}"
-              exit 1
-            fi
-
-            RELEASE=1
-            BRANCH=develop
-            git checkout $BRANCH
-
-            # if actual release (not pre), then changelog should exclude prereleases on update
-            prerelease_regex='(alpha|beta)'
-            if [[ ! ${GITHUB_REF##*/} =~ $prerelease_regex ]]; then
-              echo '::debug::Actual release (not a prerelease)'
-              TAG_REGEX="$prerelease_regex"
-              echo "FULL_RELEASE=true" >> "$GITHUB_ENV"
-            fi
-          fi
-          echo "::debug::TAG_REGEX: $TAG_REGEX"
-
-          if [[ "$(git rev-parse "origin/$BRANCH")" != "$GITHUB_SHA" ]]; then
-            # Normal build on a branch (no tag)
-            echo "::debug::BRANCH: $BRANCH $(git rev-parse "origin/$BRANCH")"
-            echo "::debug::GITHUB_SHA: $GITHUB_SHA"
-            echo "::error::$BRANCH has been updated since build started. Aborting changelog."
-            exit 1
-          fi
-
-          SINCE_TAG=$(git tag --sort=-creatordate | grep -Ev "$TAG_REGEX" | awk "NR==$(( 1 + ${RELEASE:-0} ))")
-
-          echo "::debug::BRANCH: $BRANCH"
-          echo "::debug::TAG_REGEX: $TAG_REGEX"
-          echo "::debug::FILENAME: CHANGELOG.md"
-          echo "::debug::SINCE_TAG: $SINCE_TAG"
-
-          {
-          echo "BRANCH=$BRANCH"
-          echo "TAG_REGEX=$TAG_REGEX"
-          echo "FILENAME=CHANGELOG.md"
-          echo "SINCE_TAG=$SINCE_TAG"
-          } >> "$GITHUB_ENV"
-
-      - name: Prep changelog file (clear out old lines)
-        run: |
-          # delete the top of the changelog up to the correct tag
-          tagline=$(grep -n "^## \[${SINCE_TAG}\]" "$FILENAME" | awk '{print $1}' FS=':' | head -1)
-          echo "tagline: ${tagline}"
-
-          if [[ -z $tagline ]]; then
-            echo "::error::Something is wrong. ${SINCE_TAG} isn't in the changelog."
-            exit 1
-          fi
-
-          if [[ $tagline == 1 ]]; then
-            echo "::error::Something is wrong."
-            echo "::error::The latest release ${SINCE_TAG} is the first line in the changelog,"
-            echo "::error::but the h1 '# Changelog' should always be the first line."
-            exit 1
-          fi
-
-          sed -i "1,$(( tagline - 1 ))d" "$FILENAME"
-          # delete generated line (or it will be added multiple times)
-          sed -i '/This Changelog was automatically generated by/d' "$FILENAME"
-          # delete trailing empty lines
-          sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' "$FILENAME"
-
-      - name: Generate changelog
-        uses: heinrichreimer/action-github-changelog-generator@v2.1.1
-        with:
-          # see: https://github.com/heinrichreimer/action-github-changelog-generator
-          repo: jrnl-org/jrnl
-          token: ${{ secrets.JRNL_BOT_TOKEN }}
-          base: CHANGELOG.md
-          addSections: '{"build":{"prefix":"**Build:**","labels":["build"]},"docs":{"prefix":"**Documentation:**","labels":["documentation"]},"packaging":{"prefix":"**Packaging:**","labels":["packaging"]}}'
-          issues: true
-          pullRequests: true
-          issuesWoLabels: false
-          unreleased: true
-          compareLink: true
-          includeLabels: bug,enhancement,documentation,build,packaging,deprecated
-          excludeLabels: stale,wontfix
-          excludeTagsRegex: ${{ env.TAG_REGEX }}
-          sinceTag: ${{ env.SINCE_TAG }}
-          maxIssues: 150
-          releaseUrl: https://pypi.org/project/jrnl/%s/
-          releaseBranch: develop
-          verbose: false
-          author: true
-
-      - name: Small fixes
-        run: |
-          # Change unreleased link to correct url
-          sed -i 's!https://pypi.org/project/jrnl/HEAD/!https://github.com/jrnl-org/jrnl/!' "$FILENAME"
-
-      - name: Diff and consistency check
-        run: |
-          git diff
-          if [[ $(grep -c '^# Changelog$' "$FILENAME") != 1 ]]; then
-            echo '::error::Something is wrong with the changelog.'
-            exit 1
-          fi
-          SOMETHING_CHANGED=false
-          git diff --exit-code || SOMETHING_CHANGED=true
-          echo "::debug::SOMETHING_CHANGED: $SOMETHING_CHANGED"
-          echo "SOMETHING_CHANGED=$SOMETHING_CHANGED" >> "$GITHUB_ENV"
-
-      - name: Commit
-        if: env.SOMETHING_CHANGED == 'true'
-        run: |
-          git config --global user.name "${{ secrets.JRNL_BOT_NAME }}"
-          git config --global user.email "${{ secrets.JRNL_BOT_EMAIL }}"
-          git add "$FILENAME"
-          git commit -m "Update changelog [ci skip]"
-          git push origin "$BRANCH"
-
-      - name: Update tag to include changelog
-        if: startsWith(env.GITHUB_REF, 'refs/tags/')
-        run: |
-          # This is a tag build (releases and prereleases)
-          # update the tag to include the changelog
-          git tag -fam "$GITHUB_REF_NAME" "$GITHUB_REF_NAME"
-          git push --tags --force
-
-      - name: Merge to Release branch
-        if: env.FULL_RELEASE == 'true'
-        run: |
-          git fetch --unshallow origin
-          git checkout release
-          git merge --ff-only "$BRANCH"
-          git push origin release
-

.github/workflows/docs.yaml

@@ -1,76 +0,0 @@
-# Copyright © 2012-2023 jrnl contributors
-# License: https://www.gnu.org/licenses/gpl-3.0.html
-
-name: Docs
-
-on:
-  push:
-    branches: [ develop, release ]
-    paths:
-    - 'docs/**'
-    - 'docs_theme/**'
-    - 'mkdocs.yml'
-    - 'readthedocs.yml'
-    - '.github/workflows/docs.yaml'
-    - 'tasks.py'
-    - 'pyproject.toml'
-  pull_request:
-    branches: [ develop ]
-    paths:
-    - 'docs/**'
-    - 'docs_theme/**'
-    - 'mkdocs.yml'
-    - 'readthedocs.yml'
-    - '.github/workflows/docs.yaml'
-    - 'tasks.py'
-    - 'pyproject.toml'
-
-jobs:
-  accessibility:
-    if: contains(toJson(github.event.commits), '[ci skip]') == false
-    runs-on: ubuntu-latest
-    strategy:
-      fail-fast: true
-      matrix:
-        python-version: [ '3.11' ]
-        os: [ ubuntu-latest ]
-
-    steps:
-    - uses: actions/checkout@v4
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: ${{ matrix.python-version }}
-
-    - name: Setup Node.js environment
-      uses: actions/setup-node@main
-
-    - name: Capture full Python version in env
-      run: echo "PYTHON_FULL_VERSION=$(python --version)" >> "$GITHUB_ENV"
-
-    - name: poetry cache
-      uses: actions/cache@v4
-      with:
-        path: .venv
-        key: ${{ runner.os }}-${{ hashFiles('poetry.lock') }}-${{ env.PYTHON_FULL_VERSION }}-${{ secrets.CACHE_STRING }}
-
-    - name: npm cache
-      uses: actions/cache@v4
-      with:
-        path: node_modules
-        key: ${{ runner.os }}-pa11y-v3
-
-    - name: Install dependencies
-      run: |
-        pip install poetry
-        poetry config --local virtualenvs.in-project true
-        poetry sync --no-root
-        npm install
-        echo "node_modules/.bin" >> "$GITHUB_PATH"
-
-    - name: Start docs server
-      run: poetry run poe docs-run &
-
-    - name: Accessibility testing (Pa11y)
-      run: poetry run poe docs-check

.github/workflows/release.yaml

@@ -1,109 +0,0 @@
-# Copyright © 2012-2023 jrnl contributors
-# License: https://www.gnu.org/licenses/gpl-3.0.html
-
-name: Release
-on:
-  workflow_dispatch:
-    inputs:
-      version:
-        description: 'Version (e.g. v2.5, v2.5.1-beta, v2.6-beta2)'
-        type: string
-        required: true
-      include_repo_version:
-        description: 'Update version in repo?'
-        type: boolean
-        required: true
-        default: true
-      include_pypi:
-        description: 'Publish to PyPI?'
-        type: boolean
-        required: true
-        default: true
-
-jobs:
-  validate:
-    name: "Validate version string"
-    runs-on: ubuntu-latest
-    steps:
-    - name: Validate version
-      run: |
-        JRNL_VERSION="${{ github.event.inputs.version }}"
-        echo "::debug::version: $JRNL_VERSION"
-        if [[ ! $JRNL_VERSION =~ ^v[0-9]+(\.[0-9]+){1,2}(-(alpha|beta)([0-9]+)?)?$ ]]; then
-          echo
-          echo "::error::Bad version"
-          echo
-          echo "Version string should match pattern above."
-          echo "Here are some examples of valid version numbers:"
-          echo
-          echo "  v2.5"
-          echo "  v2.5-alpha"
-          echo "  v2.5-beta"
-          echo "  v2.5.1"
-          echo "  v2.5.1-alpha"
-          echo "  v2.5.1-beta"
-          exit 1
-        fi
-
-  release_pypi:
-    needs: validate
-    name: "Release to PyPI"
-    runs-on: ubuntu-latest
-    outputs:
-      pypi_version: ${{ steps.pypi-version-getter.outputs.pypi_version }}
-    env:
-      HOME_REPO: ${{ secrets.HOME_REPO }}
-    steps:
-    - name: Get version
-      run: |
-        JRNL_VERSION="${{ github.event.inputs.version }}"
-        echo "::debug::version: $JRNL_VERSION"
-        echo "JRNL_VERSION=$JRNL_VERSION" >> "$GITHUB_ENV"
-
-    - name: Set up Python
-      uses: actions/setup-python@v5
-      with:
-        python-version: '3.13'
-
-    - name: Checkout repo
-      uses: actions/checkout@v4
-      with:
-        token: ${{ secrets.JRNL_BOT_TOKEN }}
-
-    - name: Config git user
-      run: |
-        git config --global user.name "${{ secrets.JRNL_BOT_NAME }}"
-        git config --global user.email "${{ secrets.JRNL_BOT_EMAIL }}"
-
-    - name: Install dependencies
-      run: pip install poetry
-
-    - name: Update version in files
-      if: ${{ github.event.inputs.include_repo_version == 'true' }}
-      run: |
-        poetry version "$JRNL_VERSION"
-        echo "__version__ = \"$JRNL_VERSION\"" > jrnl/__version__.py
-
-    - name: Commit updated files
-      if: ${{ github.event.inputs.include_repo_version == 'true' && github.repository == env.HOME_REPO }}
-      run: |
-        git add pyproject.toml jrnl/__version__.py
-        git commit -m "Increment version to ${JRNL_VERSION}"
-        git tag -a -m "$JRNL_VERSION" "$JRNL_VERSION"
-        git push
-        git push --tags
-
-    - name: Build
-      run: poetry build
-
-    - name: Deploy to PyPI
-      if: ${{ github.event.inputs.include_pypi == 'true' && github.repository == env.HOME_REPO }}
-      env:
-        POETRY_PYPI_TOKEN_PYPI: ${{ secrets.PYPI_TOKEN }}
-      run: poetry publish
-
-    - name: Get PyPI version
-      id: pypi-version-getter
-      run: |
-        pypi_version="$(find dist/jrnl-*.tar.gz | sed -r 's!dist/jrnl-(.*)\.tar\.gz!\1!')"
-        echo "pypi_version=$pypi_version" >> "$GITHUB_OUTPUT"

.github/workflows/testing_pipelines.yaml

@@ -1,35 +0,0 @@
-# Copyright © 2012-2023 jrnl contributors
-# License: https://www.gnu.org/licenses/gpl-3.0.html
-
-name: Testing Pipeline Files
-
-on:
-  push:
-    branches: [ develop, release ]
-    paths:
-    - '.github/workflows/**'
-    - '.github/actions/**'
-  pull_request:
-    branches: [ develop ]
-    paths:
-    - '.github/workflows/**'
-    - '.github/actions/**'
-  schedule:
-    - cron: '0 0 * * SAT'
-
-jobs:
-  test:
-    if: >
-      ! contains(github.event.head_commit.message, '[ci skip]')
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        os: [ ubuntu-latest ]
-    steps:
-      - run: git config --global core.autocrlf false
-      - uses: actions/checkout@v4
-      - name: Check workflow files
-        uses: docker://rhysd/actionlint:latest
-        with:
-          args: -color

.github/workflows/testing_prs.yaml

@@ -1,48 +0,0 @@
-# Copyright © 2012-2023 jrnl contributors
-# License: https://www.gnu.org/licenses/gpl-3.0.html
-
-name: Testing
-
-on:
-  push:
-    branches: [ develop, release ]
-    paths:
-    - 'jrnl/**'
-    - 'features/**'
-    - 'tests/**'
-    - 'poetry.lock'
-    - 'pyproject.toml'
-    - '.github/workflows/testing_prs.yaml'
-    - 'tasks.py'
-  pull_request:
-    branches: [ develop ]
-    paths:
-    - 'jrnl/**'
-    - 'features/**'
-    - 'tests/**'
-    - 'poetry.lock'
-    - 'pyproject.toml'
-    - '.github/workflows/testing_prs.yaml'
-    - 'tasks.py'
-
-defaults:
-  run:
-    shell: bash # needed to prevent Windows from using PowerShell
-
-jobs:
-  test:
-    if: >
-      ! contains(github.event.head_commit.message, '[ci skip]')
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: [ '3.10', '3.11', '3.12', '3.13' ]
-        os: [ ubuntu-latest, macos-latest, windows-latest ]
-    steps:
-      - run: git config --global core.autocrlf false
-      - uses: actions/checkout@v4
-      - name: Run tests
-        uses: ./.github/actions/run_tests
-        with:
-          cache-string: ${{ secrets.CACHE_STRING }}

.github/workflows/testing_schedule.yaml

@@ -1,28 +0,0 @@
-# Copyright © 2012-2023 jrnl contributors
-# License: https://www.gnu.org/licenses/gpl-3.0.html
-
-name: Testing
-
-on:
-  schedule:
-    - cron: '0 0 * * SAT'
-
-defaults:
-  run:
-    shell: bash # needed to prevent Windows from using PowerShell
-
-jobs:
-  test_all:
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        python-version: [ '3.10', '3.11', '3.12', '3.13' ]
-        os: [ ubuntu-latest, macos-latest, windows-latest ]
-    steps:
-      - run: git config --global core.autocrlf false
-      - uses: actions/checkout@v4
-      - name: Run tests
-        uses: ./.github/actions/run_tests
-        with:
-          cache-string: ${{ secrets.CACHE_STRING }}

.gitignore

@@ -1,63 +1,52 @@
-# Byte-compiled DLL and Shared Library files
 *.py[cod]
+
+# C extensions
 *.so
 
 # Packages
 *.egg
-*.egg-info/
+*.egg-info
+dist
+build
+eggs
+parts
+bin
+var
+sdist
+develop-eggs
 .installed.cfg
-bin/
-build/
-develop-eggs/
-dist/
-eggs/
-lib64/
-parts/
-sdist/
-.tox/
-var/
-node_modules/
-__pycache__/
-.pytest_cache/
-.flakeheaven_cache/
-
-# Versioning
-.python-version
-.tool-versions
+lib
+lib64
 
 # Installer logs
+pip-log.txt
 .DS_Store
 .travis-solo
 Icon
-pip-log.txt
 
 # Documentation
 _build
 _sources
 _static
-coverage.xml
-exp/
+*.html
 objects.inv
 searchindex.js
+docs/_themes/jrnl/static/css/jrnl.css
 
-# virtualenv
-.venv*/
+# MS Visual Studio (PyTools)
+obj
+*.pyproj
+*.sln
+*.suo
+
+# virtaulenv
 env/
 env*/
-venv*/
 
-# Editor and IDE specific files
-#  Since contributors may want to user a variety of development tools it is 
-#  recommended that editor specific file types be ignored globally by each
-#  contributor via a global gitignore. Instructions for setting up a global
-#  ignore file can be found here:
-#  https://docs.github.com/en/get-started/getting-started-with-git/ignoring-files
-#  (Configuring ignored files for all repositories on your computer)
-#  Examples of such files are:
-# MS Visual Studio (PyTools)
-#   obj
-#   *.suo
-# PyCharm
-#   .idea/
-# VS Code
-#   .vscode/settings.json
+docs/_themes/jrnl/static/less/3L.less
+
+# PyCharm Project files
+.idea/
+
+# export testing director
+exp/

.readthedocs.yaml

@@ -1,28 +0,0 @@
-# readthedocs.yml
-# Read the Docs configuration file
-# See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
-
-# Required
-version: 2
-
-# Set the OS
-build:
-  os: ubuntu-22.04
-  tools:
-    python: "3"
-
-
-# Build documentation in the docs/ directory
-mkdocs:
-  configuration: mkdocs.yml
-  fail_on_warning: false
-
-# Optionally build your docs in additional formats such as PDF
-formats:
-  - pdf
-  - epub
-
-# Optionally set the version of Python and requirements required to build your docs
-python:
-  install:
-    - requirements: docs_theme/requirements.txt

.travis.yml

@@ -0,0 +1,14 @@
+language: python
+python:
+  - "2.6"
+  - "2.7"
+  - "3.3"
+  - "3.4"
+install:
+  - "pip install -e . --use-mirrors"
+  - "pip install pycrypto>=2.6 --use-mirrors"
+  - "pip install -q behave"
+# command to run tests
+script:
+ - python --version
+ - behave

CODE_OF_CONDUCT.md

@@ -1,127 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by [emailing the maintainers](mailto:maintainers@jrnl.sh).
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior, harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
-
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see the FAQ at
-https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -1,8 +1,35 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
+Contributing
+============
 
-# Contributing
+If you use jrnl, you can totally make my day by just saying "thanks for the code" or by [tweeting about jrnl](https://twitter.com/intent/tweet?text=Write+your+memoirs+on+the+command+line.+Like+a+boss.+%23jrnl&url=http%3A%2F%2Fmaebert.github.io%2Fjrnl&via=maebert). It's your chance to make a programmer happy today! If you have a minute or two, let me know what you use jrnl for and how, it'll help me to make it even better. If you blog about jrnl, I'll send you a post card!
 
-See "[Contributing](docs/contributing.md)" in the `docs` directory.
+
+Docs & Typos
+------------
+
+If you find a typo or a mistake in the docs, just fix it right away and send a pull request. The Right Way™ to fix the docs is to edit the `docs/*.rst` files on the **master** branch. You can see the result if you run `make html` inside the project's root directory, and then open `docs/_build/html/index.html` in your browser. Note that this requires [lessc](http://lesscss.org/#using-less-installation) and [Sphinx](https://pypi.python.org/pypi/Sphinx) to be installed. Changes to the CSS or Javascript should be made on `docs/_themes/jrnl/`. The `gh-pages` branch is automatically maintained and updates from `master`; you should never have to edit that.
+
+Bugs
+----
+
+They unfortunately happen. Specifically, I don't have a Windows machine to test on, so expect a few rough spots. If you found a bug, please [open a new issue](https://www.github.com/maebert/jrnl/issues/new) and describe it as well as possible. If you're a programmer and have a little time time spare, go ahead, fork the code and fix bugs you spot, it'll be much appreciated!
+
+
+Feature requests and ideas
+--------------------------
+
+So, you have an idea for a great feature? Awesome. I love you. As with bugs, first you should [open a new issue](https://www.github.com/maebert/jrnl/issues/new) on GitHub, describe the use case and what the feature should accomplish. If we agree that this feature is useful, it will sooner or later get implemented. Even sooner if you roll up your sleeves and code it yourself ;-)
+
+Keep in mind that the design goal of jrnl is to be _slim_. That means
+
+* having as few dependencies as possible
+* creating as little interface as possible to boost the learning curve
+* doing one thing and one thing well
+
+Beyond that, it should also play nice with other software and tools -- however, avoid duplicating functionality that existing tools already provide. For example, we played around with the idea of a git integrated journal so new entries would be stored in commits. However, the proposed implementation required a rather heavy git module for python as an dependency, and the same feature could be implemented with a little bit of shell scripting around jrnl.
+
+
+A short note for new programmers and programmers new to python
+--------------------------------------------------------------
+
+Although jrnl grew quite a bit since I first started working on it, the overall complexity (for an end-user program) is fairly low, and I hope you'll find the code easy enough to understand -- if you have a question, don't hesitate to ask! Python is known for it's great community and openness to novice programmers. Feel free to fork the code and play around with it. If you think you created something worth sharing, create a pull request. I never expect pull requests to be perfect, idiomatic, instantly mergeable code, and we can work through it together. Go for it!

LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2014 Manuel Ebert
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

LICENSE.md

@@ -1,675 +0,0 @@
-### GNU GENERAL PUBLIC LICENSE
-
-Version 3, 29 June 2007
-
-Copyright (C) 2007 Free Software Foundation, Inc.
-<https://fsf.org/>
-
-Everyone is permitted to copy and distribute verbatim copies of this
-license document, but changing it is not allowed.
-
-### Preamble
-
-The GNU General Public License is a free, copyleft license for
-software and other kinds of works.
-
-The licenses for most software and other practical works are designed
-to take away your freedom to share and change the works. By contrast,
-the GNU General Public License is intended to guarantee your freedom
-to share and change all versions of a program--to make sure it remains
-free software for all its users. We, the Free Software Foundation, use
-the GNU General Public License for most of our software; it applies
-also to any other work released this way by its authors. You can apply
-it to your programs, too.
-
-When we speak of free software, we are referring to freedom, not
-price. Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-them if you wish), that you receive source code or can get it if you
-want it, that you can change the software or use pieces of it in new
-free programs, and that you know you can do these things.
-
-To protect your rights, we need to prevent others from denying you
-these rights or asking you to surrender the rights. Therefore, you
-have certain responsibilities if you distribute copies of the
-software, or if you modify it: responsibilities to respect the freedom
-of others.
-
-For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must pass on to the recipients the same
-freedoms that you received. You must make sure that they, too, receive
-or can get the source code. And you must show them these terms so they
-know their rights.
-
-Developers that use the GNU GPL protect your rights with two steps:
-(1) assert copyright on the software, and (2) offer you this License
-giving you legal permission to copy, distribute and/or modify it.
-
-For the developers' and authors' protection, the GPL clearly explains
-that there is no warranty for this free software. For both users' and
-authors' sake, the GPL requires that modified versions be marked as
-changed, so that their problems will not be attributed erroneously to
-authors of previous versions.
-
-Some devices are designed to deny users access to install or run
-modified versions of the software inside them, although the
-manufacturer can do so. This is fundamentally incompatible with the
-aim of protecting users' freedom to change the software. The
-systematic pattern of such abuse occurs in the area of products for
-individuals to use, which is precisely where it is most unacceptable.
-Therefore, we have designed this version of the GPL to prohibit the
-practice for those products. If such problems arise substantially in
-other domains, we stand ready to extend this provision to those
-domains in future versions of the GPL, as needed to protect the
-freedom of users.
-
-Finally, every program is threatened constantly by software patents.
-States should not allow patents to restrict development and use of
-software on general-purpose computers, but in those that do, we wish
-to avoid the special danger that patents applied to a free program
-could make it effectively proprietary. To prevent this, the GPL
-assures that patents cannot be used to render the program non-free.
-
-The precise terms and conditions for copying, distribution and
-modification follow.
-
-### TERMS AND CONDITIONS
-
-#### 0. Definitions.
-
-"This License" refers to version 3 of the GNU General Public License.
-
-"Copyright" also means copyright-like laws that apply to other kinds
-of works, such as semiconductor masks.
-
-"The Program" refers to any copyrightable work licensed under this
-License. Each licensee is addressed as "you". "Licensees" and
-"recipients" may be individuals or organizations.
-
-To "modify" a work means to copy from or adapt all or part of the work
-in a fashion requiring copyright permission, other than the making of
-an exact copy. The resulting work is called a "modified version" of
-the earlier work or a work "based on" the earlier work.
-
-A "covered work" means either the unmodified Program or a work based
-on the Program.
-
-To "propagate" a work means to do anything with it that, without
-permission, would make you directly or secondarily liable for
-infringement under applicable copyright law, except executing it on a
-computer or modifying a private copy. Propagation includes copying,
-distribution (with or without modification), making available to the
-public, and in some countries other activities as well.
-
-To "convey" a work means any kind of propagation that enables other
-parties to make or receive copies. Mere interaction with a user
-through a computer network, with no transfer of a copy, is not
-conveying.
-
-An interactive user interface displays "Appropriate Legal Notices" to
-the extent that it includes a convenient and prominently visible
-feature that (1) displays an appropriate copyright notice, and (2)
-tells the user that there is no warranty for the work (except to the
-extent that warranties are provided), that licensees may convey the
-work under this License, and how to view a copy of this License. If
-the interface presents a list of user commands or options, such as a
-menu, a prominent item in the list meets this criterion.
-
-#### 1. Source Code.
-
-The "source code" for a work means the preferred form of the work for
-making modifications to it. "Object code" means any non-source form of
-a work.
-
-A "Standard Interface" means an interface that either is an official
-standard defined by a recognized standards body, or, in the case of
-interfaces specified for a particular programming language, one that
-is widely used among developers working in that language.
-
-The "System Libraries" of an executable work include anything, other
-than the work as a whole, that (a) is included in the normal form of
-packaging a Major Component, but which is not part of that Major
-Component, and (b) serves only to enable use of the work with that
-Major Component, or to implement a Standard Interface for which an
-implementation is available to the public in source code form. A
-"Major Component", in this context, means a major essential component
-(kernel, window system, and so on) of the specific operating system
-(if any) on which the executable work runs, or a compiler used to
-produce the work, or an object code interpreter used to run it.
-
-The "Corresponding Source" for a work in object code form means all
-the source code needed to generate, install, and (for an executable
-work) run the object code and to modify the work, including scripts to
-control those activities. However, it does not include the work's
-System Libraries, or general-purpose tools or generally available free
-programs which are used unmodified in performing those activities but
-which are not part of the work. For example, Corresponding Source
-includes interface definition files associated with source files for
-the work, and the source code for shared libraries and dynamically
-linked subprograms that the work is specifically designed to require,
-such as by intimate data communication or control flow between those
-subprograms and other parts of the work.
-
-The Corresponding Source need not include anything that users can
-regenerate automatically from other parts of the Corresponding Source.
-
-The Corresponding Source for a work in source code form is that same
-work.
-
-#### 2. Basic Permissions.
-
-All rights granted under this License are granted for the term of
-copyright on the Program, and are irrevocable provided the stated
-conditions are met. This License explicitly affirms your unlimited
-permission to run the unmodified Program. The output from running a
-covered work is covered by this License only if the output, given its
-content, constitutes a covered work. This License acknowledges your
-rights of fair use or other equivalent, as provided by copyright law.
-
-You may make, run and propagate covered works that you do not convey,
-without conditions so long as your license otherwise remains in force.
-You may convey covered works to others for the sole purpose of having
-them make modifications exclusively for you, or provide you with
-facilities for running those works, provided that you comply with the
-terms of this License in conveying all material for which you do not
-control copyright. Those thus making or running the covered works for
-you must do so exclusively on your behalf, under your direction and
-control, on terms that prohibit them from making any copies of your
-copyrighted material outside their relationship with you.
-
-Conveying under any other circumstances is permitted solely under the
-conditions stated below. Sublicensing is not allowed; section 10 makes
-it unnecessary.
-
-#### 3. Protecting Users' Legal Rights From Anti-Circumvention Law.
-
-No covered work shall be deemed part of an effective technological
-measure under any applicable law fulfilling obligations under article
-11 of the WIPO copyright treaty adopted on 20 December 1996, or
-similar laws prohibiting or restricting circumvention of such
-measures.
-
-When you convey a covered work, you waive any legal power to forbid
-circumvention of technological measures to the extent such
-circumvention is effected by exercising rights under this License with
-respect to the covered work, and you disclaim any intention to limit
-operation or modification of the work as a means of enforcing, against
-the work's users, your or third parties' legal rights to forbid
-circumvention of technological measures.
-
-#### 4. Conveying Verbatim Copies.
-
-You may convey verbatim copies of the Program's source code as you
-receive it, in any medium, provided that you conspicuously and
-appropriately publish on each copy an appropriate copyright notice;
-keep intact all notices stating that this License and any
-non-permissive terms added in accord with section 7 apply to the code;
-keep intact all notices of the absence of any warranty; and give all
-recipients a copy of this License along with the Program.
-
-You may charge any price or no price for each copy that you convey,
-and you may offer support or warranty protection for a fee.
-
-#### 5. Conveying Modified Source Versions.
-
-You may convey a work based on the Program, or the modifications to
-produce it from the Program, in the form of source code under the
-terms of section 4, provided that you also meet all of these
-conditions:
-
--   a) The work must carry prominent notices stating that you modified
-    it, and giving a relevant date.
--   b) The work must carry prominent notices stating that it is
-    released under this License and any conditions added under
-    section 7. This requirement modifies the requirement in section 4
-    to "keep intact all notices".
--   c) You must license the entire work, as a whole, under this
-    License to anyone who comes into possession of a copy. This
-    License will therefore apply, along with any applicable section 7
-    additional terms, to the whole of the work, and all its parts,
-    regardless of how they are packaged. This License gives no
-    permission to license the work in any other way, but it does not
-    invalidate such permission if you have separately received it.
--   d) If the work has interactive user interfaces, each must display
-    Appropriate Legal Notices; however, if the Program has interactive
-    interfaces that do not display Appropriate Legal Notices, your
-    work need not make them do so.
-
-A compilation of a covered work with other separate and independent
-works, which are not by their nature extensions of the covered work,
-and which are not combined with it such as to form a larger program,
-in or on a volume of a storage or distribution medium, is called an
-"aggregate" if the compilation and its resulting copyright are not
-used to limit the access or legal rights of the compilation's users
-beyond what the individual works permit. Inclusion of a covered work
-in an aggregate does not cause this License to apply to the other
-parts of the aggregate.
-
-#### 6. Conveying Non-Source Forms.
-
-You may convey a covered work in object code form under the terms of
-sections 4 and 5, provided that you also convey the machine-readable
-Corresponding Source under the terms of this License, in one of these
-ways:
-
--   a) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by the
-    Corresponding Source fixed on a durable physical medium
-    customarily used for software interchange.
--   b) Convey the object code in, or embodied in, a physical product
-    (including a physical distribution medium), accompanied by a
-    written offer, valid for at least three years and valid for as
-    long as you offer spare parts or customer support for that product
-    model, to give anyone who possesses the object code either (1) a
-    copy of the Corresponding Source for all the software in the
-    product that is covered by this License, on a durable physical
-    medium customarily used for software interchange, for a price no
-    more than your reasonable cost of physically performing this
-    conveying of source, or (2) access to copy the Corresponding
-    Source from a network server at no charge.
--   c) Convey individual copies of the object code with a copy of the
-    written offer to provide the Corresponding Source. This
-    alternative is allowed only occasionally and noncommercially, and
-    only if you received the object code with such an offer, in accord
-    with subsection 6b.
--   d) Convey the object code by offering access from a designated
-    place (gratis or for a charge), and offer equivalent access to the
-    Corresponding Source in the same way through the same place at no
-    further charge. You need not require recipients to copy the
-    Corresponding Source along with the object code. If the place to
-    copy the object code is a network server, the Corresponding Source
-    may be on a different server (operated by you or a third party)
-    that supports equivalent copying facilities, provided you maintain
-    clear directions next to the object code saying where to find the
-    Corresponding Source. Regardless of what server hosts the
-    Corresponding Source, you remain obligated to ensure that it is
-    available for as long as needed to satisfy these requirements.
--   e) Convey the object code using peer-to-peer transmission,
-    provided you inform other peers where the object code and
-    Corresponding Source of the work are being offered to the general
-    public at no charge under subsection 6d.
-
-A separable portion of the object code, whose source code is excluded
-from the Corresponding Source as a System Library, need not be
-included in conveying the object code work.
-
-A "User Product" is either (1) a "consumer product", which means any
-tangible personal property which is normally used for personal,
-family, or household purposes, or (2) anything designed or sold for
-incorporation into a dwelling. In determining whether a product is a
-consumer product, doubtful cases shall be resolved in favor of
-coverage. For a particular product received by a particular user,
-"normally used" refers to a typical or common use of that class of
-product, regardless of the status of the particular user or of the way
-in which the particular user actually uses, or expects or is expected
-to use, the product. A product is a consumer product regardless of
-whether the product has substantial commercial, industrial or
-non-consumer uses, unless such uses represent the only significant
-mode of use of the product.
-
-"Installation Information" for a User Product means any methods,
-procedures, authorization keys, or other information required to
-install and execute modified versions of a covered work in that User
-Product from a modified version of its Corresponding Source. The
-information must suffice to ensure that the continued functioning of
-the modified object code is in no case prevented or interfered with
-solely because modification has been made.
-
-If you convey an object code work under this section in, or with, or
-specifically for use in, a User Product, and the conveying occurs as
-part of a transaction in which the right of possession and use of the
-User Product is transferred to the recipient in perpetuity or for a
-fixed term (regardless of how the transaction is characterized), the
-Corresponding Source conveyed under this section must be accompanied
-by the Installation Information. But this requirement does not apply
-if neither you nor any third party retains the ability to install
-modified object code on the User Product (for example, the work has
-been installed in ROM).
-
-The requirement to provide Installation Information does not include a
-requirement to continue to provide support service, warranty, or
-updates for a work that has been modified or installed by the
-recipient, or for the User Product in which it has been modified or
-installed. Access to a network may be denied when the modification
-itself materially and adversely affects the operation of the network
-or violates the rules and protocols for communication across the
-network.
-
-Corresponding Source conveyed, and Installation Information provided,
-in accord with this section must be in a format that is publicly
-documented (and with an implementation available to the public in
-source code form), and must require no special password or key for
-unpacking, reading or copying.
-
-#### 7. Additional Terms.
-
-"Additional permissions" are terms that supplement the terms of this
-License by making exceptions from one or more of its conditions.
-Additional permissions that are applicable to the entire Program shall
-be treated as though they were included in this License, to the extent
-that they are valid under applicable law. If additional permissions
-apply only to part of the Program, that part may be used separately
-under those permissions, but the entire Program remains governed by
-this License without regard to the additional permissions.
-
-When you convey a copy of a covered work, you may at your option
-remove any additional permissions from that copy, or from any part of
-it. (Additional permissions may be written to require their own
-removal in certain cases when you modify the work.) You may place
-additional permissions on material, added by you to a covered work,
-for which you have or can give appropriate copyright permission.
-
-Notwithstanding any other provision of this License, for material you
-add to a covered work, you may (if authorized by the copyright holders
-of that material) supplement the terms of this License with terms:
-
--   a) Disclaiming warranty or limiting liability differently from the
-    terms of sections 15 and 16 of this License; or
--   b) Requiring preservation of specified reasonable legal notices or
-    author attributions in that material or in the Appropriate Legal
-    Notices displayed by works containing it; or
--   c) Prohibiting misrepresentation of the origin of that material,
-    or requiring that modified versions of such material be marked in
-    reasonable ways as different from the original version; or
--   d) Limiting the use for publicity purposes of names of licensors
-    or authors of the material; or
--   e) Declining to grant rights under trademark law for use of some
-    trade names, trademarks, or service marks; or
--   f) Requiring indemnification of licensors and authors of that
-    material by anyone who conveys the material (or modified versions
-    of it) with contractual assumptions of liability to the recipient,
-    for any liability that these contractual assumptions directly
-    impose on those licensors and authors.
-
-All other non-permissive additional terms are considered "further
-restrictions" within the meaning of section 10. If the Program as you
-received it, or any part of it, contains a notice stating that it is
-governed by this License along with a term that is a further
-restriction, you may remove that term. If a license document contains
-a further restriction but permits relicensing or conveying under this
-License, you may add to a covered work material governed by the terms
-of that license document, provided that the further restriction does
-not survive such relicensing or conveying.
-
-If you add terms to a covered work in accord with this section, you
-must place, in the relevant source files, a statement of the
-additional terms that apply to those files, or a notice indicating
-where to find the applicable terms.
-
-Additional terms, permissive or non-permissive, may be stated in the
-form of a separately written license, or stated as exceptions; the
-above requirements apply either way.
-
-#### 8. Termination.
-
-You may not propagate or modify a covered work except as expressly
-provided under this License. Any attempt otherwise to propagate or
-modify it is void, and will automatically terminate your rights under
-this License (including any patent licenses granted under the third
-paragraph of section 11).
-
-However, if you cease all violation of this License, then your license
-from a particular copyright holder is reinstated (a) provisionally,
-unless and until the copyright holder explicitly and finally
-terminates your license, and (b) permanently, if the copyright holder
-fails to notify you of the violation by some reasonable means prior to
-60 days after the cessation.
-
-Moreover, your license from a particular copyright holder is
-reinstated permanently if the copyright holder notifies you of the
-violation by some reasonable means, this is the first time you have
-received notice of violation of this License (for any work) from that
-copyright holder, and you cure the violation prior to 30 days after
-your receipt of the notice.
-
-Termination of your rights under this section does not terminate the
-licenses of parties who have received copies or rights from you under
-this License. If your rights have been terminated and not permanently
-reinstated, you do not qualify to receive new licenses for the same
-material under section 10.
-
-#### 9. Acceptance Not Required for Having Copies.
-
-You are not required to accept this License in order to receive or run
-a copy of the Program. Ancillary propagation of a covered work
-occurring solely as a consequence of using peer-to-peer transmission
-to receive a copy likewise does not require acceptance. However,
-nothing other than this License grants you permission to propagate or
-modify any covered work. These actions infringe copyright if you do
-not accept this License. Therefore, by modifying or propagating a
-covered work, you indicate your acceptance of this License to do so.
-
-#### 10. Automatic Licensing of Downstream Recipients.
-
-Each time you convey a covered work, the recipient automatically
-receives a license from the original licensors, to run, modify and
-propagate that work, subject to this License. You are not responsible
-for enforcing compliance by third parties with this License.
-
-An "entity transaction" is a transaction transferring control of an
-organization, or substantially all assets of one, or subdividing an
-organization, or merging organizations. If propagation of a covered
-work results from an entity transaction, each party to that
-transaction who receives a copy of the work also receives whatever
-licenses to the work the party's predecessor in interest had or could
-give under the previous paragraph, plus a right to possession of the
-Corresponding Source of the work from the predecessor in interest, if
-the predecessor has it or can get it with reasonable efforts.
-
-You may not impose any further restrictions on the exercise of the
-rights granted or affirmed under this License. For example, you may
-not impose a license fee, royalty, or other charge for exercise of
-rights granted under this License, and you may not initiate litigation
-(including a cross-claim or counterclaim in a lawsuit) alleging that
-any patent claim is infringed by making, using, selling, offering for
-sale, or importing the Program or any portion of it.
-
-#### 11. Patents.
-
-A "contributor" is a copyright holder who authorizes use under this
-License of the Program or a work on which the Program is based. The
-work thus licensed is called the contributor's "contributor version".
-
-A contributor's "essential patent claims" are all patent claims owned
-or controlled by the contributor, whether already acquired or
-hereafter acquired, that would be infringed by some manner, permitted
-by this License, of making, using, or selling its contributor version,
-but do not include claims that would be infringed only as a
-consequence of further modification of the contributor version. For
-purposes of this definition, "control" includes the right to grant
-patent sublicenses in a manner consistent with the requirements of
-this License.
-
-Each contributor grants you a non-exclusive, worldwide, royalty-free
-patent license under the contributor's essential patent claims, to
-make, use, sell, offer for sale, import and otherwise run, modify and
-propagate the contents of its contributor version.
-
-In the following three paragraphs, a "patent license" is any express
-agreement or commitment, however denominated, not to enforce a patent
-(such as an express permission to practice a patent or covenant not to
-sue for patent infringement). To "grant" such a patent license to a
-party means to make such an agreement or commitment not to enforce a
-patent against the party.
-
-If you convey a covered work, knowingly relying on a patent license,
-and the Corresponding Source of the work is not available for anyone
-to copy, free of charge and under the terms of this License, through a
-publicly available network server or other readily accessible means,
-then you must either (1) cause the Corresponding Source to be so
-available, or (2) arrange to deprive yourself of the benefit of the
-patent license for this particular work, or (3) arrange, in a manner
-consistent with the requirements of this License, to extend the patent
-license to downstream recipients. "Knowingly relying" means you have
-actual knowledge that, but for the patent license, your conveying the
-covered work in a country, or your recipient's use of the covered work
-in a country, would infringe one or more identifiable patents in that
-country that you have reason to believe are valid.
-
-If, pursuant to or in connection with a single transaction or
-arrangement, you convey, or propagate by procuring conveyance of, a
-covered work, and grant a patent license to some of the parties
-receiving the covered work authorizing them to use, propagate, modify
-or convey a specific copy of the covered work, then the patent license
-you grant is automatically extended to all recipients of the covered
-work and works based on it.
-
-A patent license is "discriminatory" if it does not include within the
-scope of its coverage, prohibits the exercise of, or is conditioned on
-the non-exercise of one or more of the rights that are specifically
-granted under this License. You may not convey a covered work if you
-are a party to an arrangement with a third party that is in the
-business of distributing software, under which you make payment to the
-third party based on the extent of your activity of conveying the
-work, and under which the third party grants, to any of the parties
-who would receive the covered work from you, a discriminatory patent
-license (a) in connection with copies of the covered work conveyed by
-you (or copies made from those copies), or (b) primarily for and in
-connection with specific products or compilations that contain the
-covered work, unless you entered into that arrangement, or that patent
-license was granted, prior to 28 March 2007.
-
-Nothing in this License shall be construed as excluding or limiting
-any implied license or other defenses to infringement that may
-otherwise be available to you under applicable patent law.
-
-#### 12. No Surrender of Others' Freedom.
-
-If conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License. If you cannot convey a
-covered work so as to satisfy simultaneously your obligations under
-this License and any other pertinent obligations, then as a
-consequence you may not convey it at all. For example, if you agree to
-terms that obligate you to collect a royalty for further conveying
-from those to whom you convey the Program, the only way you could
-satisfy both those terms and this License would be to refrain entirely
-from conveying the Program.
-
-#### 13. Use with the GNU Affero General Public License.
-
-Notwithstanding any other provision of this License, you have
-permission to link or combine any covered work with a work licensed
-under version 3 of the GNU Affero General Public License into a single
-combined work, and to convey the resulting work. The terms of this
-License will continue to apply to the part which is the covered work,
-but the special requirements of the GNU Affero General Public License,
-section 13, concerning interaction through a network will apply to the
-combination as such.
-
-#### 14. Revised Versions of this License.
-
-The Free Software Foundation may publish revised and/or new versions
-of the GNU General Public License from time to time. Such new versions
-will be similar in spirit to the present version, but may differ in
-detail to address new problems or concerns.
-
-Each version is given a distinguishing version number. If the Program
-specifies that a certain numbered version of the GNU General Public
-License "or any later version" applies to it, you have the option of
-following the terms and conditions either of that numbered version or
-of any later version published by the Free Software Foundation. If the
-Program does not specify a version number of the GNU General Public
-License, you may choose any version ever published by the Free
-Software Foundation.
-
-If the Program specifies that a proxy can decide which future versions
-of the GNU General Public License can be used, that proxy's public
-statement of acceptance of a version permanently authorizes you to
-choose that version for the Program.
-
-Later license versions may give you additional or different
-permissions. However, no additional obligations are imposed on any
-author or copyright holder as a result of your choosing to follow a
-later version.
-
-#### 15. Disclaimer of Warranty.
-
-THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
-APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
-HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT
-LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND
-PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE
-DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
-CORRECTION.
-
-#### 16. Limitation of Liability.
-
-IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR
-CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES
-ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT
-NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR
-LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM
-TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
-PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
-
-#### 17. Interpretation of Sections 15 and 16.
-
-If the disclaimer of warranty and limitation of liability provided
-above cannot be given local legal effect according to their terms,
-reviewing courts shall apply local law that most closely approximates
-an absolute waiver of all civil liability in connection with the
-Program, unless a warranty or assumption of liability accompanies a
-copy of the Program in return for a fee.
-
-END OF TERMS AND CONDITIONS
-
-### How to Apply These Terms to Your New Programs
-
-If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these
-terms.
-
-To do so, attach the following notices to the program. It is safest to
-attach them to the start of each source file to most effectively state
-the exclusion of warranty; and each file should have at least the
-"copyright" line and a pointer to where the full notice is found.
-
-        <one line to give the program's name and a brief idea of what it does.>
-        Copyright (C) <year>  <name of author>
-
-        This program is free software: you can redistribute it and/or modify
-        it under the terms of the GNU General Public License as published by
-        the Free Software Foundation, either version 3 of the License, or
-        (at your option) any later version.
-
-        This program is distributed in the hope that it will be useful,
-        but WITHOUT ANY WARRANTY; without even the implied warranty of
-        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-        GNU General Public License for more details.
-
-        You should have received a copy of the GNU General Public License
-        along with this program.  If not, see <https://www.gnu.org/licenses/>.
-
-Also add information on how to contact you by electronic and paper
-mail.
-
-If the program does terminal interaction, make it output a short
-notice like this when it starts in an interactive mode:
-
-        <program>  Copyright (C) <year>  <name of author>
-        This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-        This is free software, and you are welcome to redistribute it
-        under certain conditions; type `show c' for details.
-
-The hypothetical commands \`show w' and \`show c' should show the
-appropriate parts of the General Public License. Of course, your
-program's commands might be different; for a GUI interface, you would
-use an "about box".
-
-You should also get your employer (if you work as a programmer) or
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary. For more information on this, and how to apply and follow
-the GNU GPL, see <https://www.gnu.org/licenses/>.
-
-The GNU General Public License does not permit incorporating your
-program into proprietary programs. If your program is a subroutine
-library, you may consider it more useful to permit linking proprietary
-applications with the library. If this is what you want to do, use the
-GNU Lesser General Public License instead of this License. But first,
-please read <https://www.gnu.org/licenses/why-not-lgpl.html>.

Makefile

@@ -0,0 +1,39 @@
+# A Makefile for commands I run frequently:
+
+clean:
+	rm -rf dist
+	rm -rf _static
+	rm -rf jrnl.egg-info
+	rm -rf docs/_build
+	rm -rf _build
+	rm -rf _sources
+	rm -rf _static
+	rm -f *.html
+
+html:
+	curl https://raw.githubusercontent.com/mateuszkocz/3l/master/3L/3L.less > docs/_themes/jrnl/static/less/3L.less ;\
+	lessc --clean-css docs/_themes/jrnl/static/less/jrnl.less docs/_themes/jrnl/static/css/jrnl.css ;\
+	cd docs ;\
+	make html ;\
+	cd .. ;\
+	open docs/_build/html/index.html ;\
+
+# Build GitHub Page from docs
+docs:
+	git checkout gh-pages ; \
+	git checkout master docs ; \
+	git checkout master jrnl ; \
+	curl https://raw.githubusercontent.com/mateuszkocz/3l/master/3L/3L.less > docs/_themes/jrnl/static/less/3L.less ;\
+	lessc --clean-css docs/_themes/jrnl/static/less/jrnl.less docs/_themes/jrnl/static/css/jrnl.css ; \
+	cd docs ; \
+	make html ; \
+	cd .. ; \
+	cp -r docs/_build/html/* . ; \
+	git add -A ; \
+	git commit -m "Updated docs from master" ; \
+	git push -u origin gh-pages ; \
+	git checkout master
+
+# Upload to pipy
+dist:
+	python setup.py publish

README.md

@@ -1,85 +1,41 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-<p align="center">
-<a href="https://jrnl.sh">
-<img align="center" src="https://raw.githubusercontent.com/jrnl-org/jrnl/develop/docs_theme/assets/readme-header.png"/>
-</a>
-</p>
-
-jrnl
- [![Testing](https://github.com/jrnl-org/jrnl/workflows/Testing/badge.svg)](https://github.com/jrnl-org/jrnl/actions?query=workflow%3ATesting)
- [![Downloads](https://pepy.tech/badge/jrnl)](https://pepy.tech/project/jrnl)
- [![Version](http://img.shields.io/pypi/v/jrnl.svg?style=flat)](https://pypi.python.org/pypi/jrnl/)
- [![Homebrew](https://img.shields.io/homebrew/v/jrnl?style=flat-square)](https://formulae.brew.sh/formula/jrnl)
- [![Gitter](https://img.shields.io/gitter/room/jrnl-org/jrnl)](https://gitter.im/jrnl-org/jrnl)
- [![Changelog](https://img.shields.io/badge/changelog-on%20github-green)](https://github.com/jrnl-org/jrnl/blob/develop/CHANGELOG.md)
+jrnl [![Build Status](http://img.shields.io/travis/maebert/jrnl.svg?style=flat)](https://travis-ci.org/maebert/jrnl)  [![Downloads](http://img.shields.io/pypi/dm/jrnl.svg?style=flat)](https://pypi.python.org/pypi/jrnl/) [![Version](http://img.shields.io/pypi/v/jrnl.svg?style=flat)](https://pypi.python.org/pypi/jrnl/)
 ====
 
-_To get help, [submit an issue](https://github.com/jrnl-org/jrnl/issues/new/choose) on
-GitHub._
+_For news on updates or to get help, [read the docs](http://maebert.github.io/jrnl), follow [@maebert](https://twitter.com/maebert) or [submit an issue](https://github.com/maebert/jrnl/issues/new) on Github._
 
-`jrnl` is a simple journal application for the command line.
+*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.
 
-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](http://en.wikipedia.org/wiki/Advanced_Encryption_Standard).
+*jrnl* also plays nice with the fabulous [DayOne](http://dayoneapp.com/) and can read and write directly from and to DayOne Journals.
 
-## In a Nutshell
+Optionally, your journal can be encrypted using the [256-bit AES](http://en.wikipedia.org/wiki/Advanced_Encryption_Standard).
 
-To make a new entry, just enter
+### Why keep a journal?
 
-``` sh
-jrnl yesterday: Called in sick. Used the time to clean the house and write my
-book.
-```
+Journals aren't only for 13-year old girls 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.
 
-`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:
+In a Nutshell
+-------------
 
-    [2012-03-29 09:00] Called in sick.
-    Used the time to clean the house and write my book.
+to make a new entry, just type
 
-If you just call `jrnl`, you will be prompted to compose your entry - but you
-can also configure _jrnl_ to use your external editor.
+    jrnl yesterday: Called in sick. Used the time to clean the house and spent 4h on writing my book.
 
-For more information, please read the
-[documentation](https://jrnl.sh).
+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:
 
-## Contributors
+    2012-03-29 09:00 Called in sick.
+    Used the time to clean the house and spent 4h on writing my book.
 
-### Maintainers
+If you just call `jrnl`, you will be prompted to compose your entry - but you can also configure _jrnl_ to use your external editor.
 
-Our maintainers help keep the lights on for the project:
 
- * Jonathan Wren ([wren](https://github.com/wren))
- * Micah Ellison ([micahellison](https://github.com/micahellison))
+Installation
+------------
 
-Please thank them if you like `jrnl`!
+Install _jrnl_ using pip:
 
-### Code Contributors
+    pip install jrnl
 
-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!
+Or, if you want the option to encrypt your journal,
 
-<a href="https://github.com/jrnl-org/jrnl/graphs/contributors"><img
-src="https://opencollective.com/jrnl/contributors.svg?width=890&button=false"
-/></a>
+    pip install jrnl[encrypted]
 
-If you'd also like to help make `jrnl` better, please see our [contributing
-documentation](docs/contributing.md).
-
-### 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](https://opencollective.com/jrnl/contribute)
-and help us sustain our community.
-
-<a href="https://opencollective.com/jrnl"><img
-src="https://opencollective.com/jrnl/individuals.svg?width=890"></a>

SECURITY.md

@@ -1,7 +0,0 @@
-# Security
-
-If you've discovered a potential security issue in jrnl, please contact the maintainers at [maintainers@jrnl.sh](mailto:maintainers@jrnl.sh).
-
-You can also feel free to [open an issue](https://github.com/jrnl-org/jrnl/issues/new/choose) (but please don't disclose the vulnerability) in case the email goes to spam.
-
-You can find [known privacy and security issues in our documentation](https://jrnl.sh/en/stable/privacy-and-security/).

docs/Makefile

@@ -0,0 +1,177 @@
+# Makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS    =
+SPHINXBUILD   = sphinx-build
+PAPER         =
+BUILDDIR      = _build
+
+# User-friendly check for sphinx-build
+ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
+$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
+endif
+
+# Internal variables.
+PAPEROPT_a4     = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+# the i18n builder cannot share the environment and doctrees with the others
+I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+
+.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest gettext
+
+help:
+	@echo "Please use \`make <target>' where <target> is one of"
+	@echo "  html       to make standalone HTML files"
+	@echo "  dirhtml    to make HTML files named index.html in directories"
+	@echo "  singlehtml to make a single large HTML file"
+	@echo "  pickle     to make pickle files"
+	@echo "  json       to make JSON files"
+	@echo "  htmlhelp   to make HTML files and a HTML help project"
+	@echo "  qthelp     to make HTML files and a qthelp project"
+	@echo "  devhelp    to make HTML files and a Devhelp project"
+	@echo "  epub       to make an epub"
+	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
+	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
+	@echo "  latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
+	@echo "  text       to make text files"
+	@echo "  man        to make manual pages"
+	@echo "  texinfo    to make Texinfo files"
+	@echo "  info       to make Texinfo files and run them through makeinfo"
+	@echo "  gettext    to make PO message catalogs"
+	@echo "  changes    to make an overview of all changed/added/deprecated items"
+	@echo "  xml        to make Docutils-native XML files"
+	@echo "  pseudoxml  to make pseudoxml-XML files for display purposes"
+	@echo "  linkcheck  to check all external links for integrity"
+	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
+
+clean:
+	rm -rf $(BUILDDIR)/*
+
+html:
+	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
+
+dirhtml:
+	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
+
+singlehtml:
+	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
+	@echo
+	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
+
+pickle:
+	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
+	@echo
+	@echo "Build finished; now you can process the pickle files."
+
+json:
+	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
+	@echo
+	@echo "Build finished; now you can process the JSON files."
+
+htmlhelp:
+	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
+	@echo
+	@echo "Build finished; now you can run HTML Help Workshop with the" \
+	      ".hhp project file in $(BUILDDIR)/htmlhelp."
+
+qthelp:
+	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
+	@echo
+	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
+	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/jrnl.qhcp"
+	@echo "To view the help file:"
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/jrnl.qhc"
+
+devhelp:
+	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
+	@echo
+	@echo "Build finished."
+	@echo "To view the help file:"
+	@echo "# mkdir -p $$HOME/.local/share/devhelp/jrnl"
+	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/jrnl"
+	@echo "# devhelp"
+
+epub:
+	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
+	@echo
+	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
+
+latex:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo
+	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
+	@echo "Run \`make' in that directory to run these through (pdf)latex" \
+	      "(use \`make latexpdf' here to do that automatically)."
+
+latexpdf:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo "Running LaTeX files through pdflatex..."
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+latexpdfja:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo "Running LaTeX files through platex and dvipdfmx..."
+	$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+text:
+	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
+	@echo
+	@echo "Build finished. The text files are in $(BUILDDIR)/text."
+
+man:
+	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+	@echo
+	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+texinfo:
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+	@echo
+	@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
+	@echo "Run \`make' in that directory to run these through makeinfo" \
+	      "(use \`make info' here to do that automatically)."
+
+info:
+	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
+	@echo "Running Texinfo files through makeinfo..."
+	make -C $(BUILDDIR)/texinfo info
+	@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
+
+gettext:
+	$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
+	@echo
+	@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
+
+changes:
+	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
+	@echo
+	@echo "The overview file is in $(BUILDDIR)/changes."
+
+linkcheck:
+	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
+	@echo
+	@echo "Link check complete; look for any errors in the above output " \
+	      "or in $(BUILDDIR)/linkcheck/output.txt."
+
+doctest:
+	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
+	@echo "Testing of doctests in the sources finished, look at the " \
+	      "results in $(BUILDDIR)/doctest/output.txt."
+
+xml:
+	$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
+	@echo
+	@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
+
+pseudoxml:
+	$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
+	@echo
+	@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."

docs/_themes/jrnl/index.html

@@ -0,0 +1,93 @@
+<!DOCTYPE html>
+<!--[if lt IE 7]>      <html class="no-js lt-ie9 lt-ie8 lt-ie7"> <![endif]-->
+<!--[if IE 7]>         <html class="no-js lt-ie9 lt-ie8"> <![endif]-->
+<!--[if IE 8]>         <html class="no-js lt-ie9"> <![endif]-->
+<!--[if gt IE 8]><!--> <html class="no-js"> <!--<![endif]-->
+    <head>
+        <meta charset="utf-8">
+        <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
+        <title>jrnl- The Command Line Journal</title>
+        <meta name="description" content="">
+        <meta name="viewport" content="width=device-width">
+
+
+        <link href='http://fonts.googleapis.com/css?family=Open+Sans:300,700' rel='stylesheet' type='text/css'>
+        <link rel="stylesheet" href="{{ pathto('_static/css/jrnl.css', 1) }}">
+        <link rel="apple-touch-icon-precomposed" href="{{ pathto('_static/img/favicon-152.png', 1) }}">
+        <link rel="shortcut icon" href="{{ pathto('_static/img/favicon.ico', 1) }}">
+    </head>
+    <body id="landing" class="landing">
+        <div id="upper">
+            <a id="twitter" href="https://twitter.com/intent/tweet?text=Write+your+memoirs+on+the+command+line.+Like+a+boss.+%23jrnl&url=http%3A%2F%2Fmaebert.github.io%2Fjrnl&via=maebert">Tell your friends</a>
+            <div id="title">
+                <img id="logo" src="{{ pathto('_static/img/logo.png', 1) }}"  width="90px" height="98px" title="jrnl"/>
+                <h1>Collect your thoughts and notes <br />without leaving the command line</h1>
+            </div>
+            <div id="prompt">
+                <div class="pleft" onclick="reset(); prev(); return false;"><i class="icon left"></i></div>
+                <div class="terminal">$ jrnl <span id="args"></span><span id="input">today: Started writing my memoirs. On the command line. Like a boss.</span><div id="output"></div></div>
+                <div class="pright" onclick="reset(); next(); return false;"><i class="icon right"></i></div>
+            </div>
+        </div>
+        <div id="nav">
+            <a href="{{ pathto('overview') }}" title="Documentation">Documentation</a>
+            <a href="http://github.com/maebert/jrnl" title="View on Github">Fork me on GitHub</a>
+            <a id="twitter-nav" href="https://twitter.com/intent/tweet?text=Write+your+memoirs+on+the+command+line.+Like+a+boss.+%23jrnl&url=http%3A%2F%2Fmaebert.github.io%2Fjrnl&via=maebert">Tell your friends on twitter</a>
+            <a href="{{ pathto('installation') }}" title="Quick Start" class="cta">Download &#9654;</a>
+        </div>
+        <div id="lower">
+            <div class="row3">
+                <div class="col">
+                    <i class="icon nli"></i>
+                    <h3>Human friendly.</h3>
+                    <p>jrnl has a natural-language interface so you don't have to remember cryptic shortcuts when you're writing down your thoughts.</p>
+                </div>
+                <div class="col">
+                    <i class="icon future"></i>
+                    <h3>Future-proof.</h3>
+                    <p>your journals are stored in plain-text files that will still be readable in 50 years when all your fancy iPad apps will have gone the way of the Dodo.</p>
+                </div>
+                <div class="col">
+                    <i class="icon secure"></i>
+                    <h3>Secure.</h3>
+                    <p>Encrypt your journals with the military-grade AES encryption. Even the NSA won't be able to read your dirty secrets.</p>
+                </div>
+            </div>
+            <div class="row4">
+                <div class="col">
+                    <i class="icon sync"></i>
+                    <h3>Accessible anywhere.</h3>
+                    <p>Sync your journals with Dropbox and capture your thoughts where ever you are</p>
+                </div>
+                <div class="col">
+                    <i class="icon dayone"></i>
+                    <h3>DayOne compatible.</h3>
+                    <p>Read, write and search your DayOne journal from the command line.</p>
+                </div>
+                <div class="col">
+                    <i class="icon github"></i>
+                    <h3>Free &amp; Open Source.</h3>
+                    <p>jrnl is made by a bunch of really friendly and remarkably attractive people. Maybe even <a href="https://www.github.com/maebert/jrnl" title="Fork jrnl on GitHub">you</a>?</p>
+                </div>
+                <div class="col">
+                    <i class="icon folders"></i>
+                    <h3>For work and play.</h3>
+                    <p>Effortlessly access several journals for all parts of your life.</p>
+                </div>
+            </div>
+
+          <div class="footer">
+            {{ copyright }}
+          </div>
+        </div>
+
+
+        <script src="{{ pathto('_static/js/landing.js', 1) }}"></script>
+        <script>
+            var _gaq=[['_setAccount','UA-XXXXX-X'],['_trackPageview']];
+            (function(d,t){var g=d.createElement(t),s=d.getElementsByTagName(t)[0];
+            g.src='//www.google-analytics.com/ga.js';
+            s.parentNode.insertBefore(g,s)}(document,'script'));
+        </script>
+    </body>
+</html>

docs/_themes/jrnl/layout.html

@@ -0,0 +1,29 @@
+{% if pagename == "index" %}
+  {% include "index.html" %}
+{% else %}
+  {%- extends "basic/layout.html" %}
+
+  {%- block extrahead %}
+    {{ super() }}
+    <meta name="viewport" content="width=device-width, initial-scale=0.9, maximum-scale=0.9">
+    <link rel="apple-touch-icon-precomposed" href="{{ pathto('_static/img/favicon-152.png', 1) }}">
+    <link rel="shortcut icon" href="{{ pathto('_static/img/favicon.ico', 1) }}">
+  {% endblock %}
+  {%- block relbar1 %}{% endblock %}
+  {%- block relbar2 %}{% endblock %}
+
+  {%- block sidebar2 %}
+  <aside>
+    <a href="{{ pathto('index') }}" id="logolink" title="jrnl"><img class="logo" src="{{ pathto('_static/img/logo.png', 1) }}" width="90px" height="98px" title="jrnl"/></a>
+    <h2>Documentation</h2>
+    {{ toctree() }}
+    {%- include "searchbox.html" %}
+  </aside>
+  {% endblock %}
+
+  {%- block footer %}
+      <div class="footer">
+          {{ copyright }}
+      </div>
+  {%- endblock %}
+{% endif %}

docs/_themes/jrnl/relations.html

@@ -0,0 +1,19 @@
+<h3>Related Topics</h3>
+<ul>
+  <li><a href="{{ pathto(master_doc) }}">Documentation overview</a><ul>
+  {%- for parent in parents %}
+  <li><a href="{{ parent.link|e }}">{{ parent.title }}</a><ul>
+  {%- endfor %}
+    {%- if prev %}
+      <li>Previous: <a href="{{ prev.link|e }}" title="{{ _('previous chapter')
+        }}">{{ prev.title }}</a></li>
+    {%- endif %}
+    {%- if next %}
+      <li>Next: <a href="{{ next.link|e }}" title="{{ _('next chapter')
+        }}">{{ next.title }}</a></li>
+    {%- endif %}
+  {%- for parent in parents %}
+  </ul></li>
+  {%- endfor %}
+  </ul></li>
+</ul>

docs/_themes/jrnl/static/js/landing.js

@@ -0,0 +1,109 @@
+var phrases = [
+    ["", "today: Started writing my memoirs. On the command line. Like a boss.", ""],
+    ["", "yesterday 2pm: used jrnl to keep track of accomplished tasks. The done.txt for my todo.txt", ""],
+    ["-from 2009 -until may", "", "(Displays all entries from January 2009 to last may)"],
+    ["", "A day on the beach with @beth and @frank. Taggidy-tag-tag.", ""],
+    ["--tags", "", "@idea    7<br />@beth    5"],
+    ["--export json", "", "(Exports your entire journal to json)"],
+    ["--encrypt", "", "(256 bit AES encryption. Crack this, NSA.)"]
+]
+
+var args = document.getElementById("args");
+var input = document.getElementById("input");
+var output = document.getElementById("output");
+var current = 0
+var timer = null;
+var fadeInTimer = null;
+var fadeOutTimer = null;
+var letterTimer = null;
+var unletterTimer = null;
+
+var next = function() {
+    current = (current + 1) % phrases.length;
+    reveal(current);
+    timer = setTimeout(next, 5000);
+}
+
+var prev = function() {
+    current = (current === 0) ? phrases.length - 1 : current - 1;
+    reveal(current);
+    timer = setTimeout(next, 5000);
+}
+
+var reveal = function(idx) {
+    var args_text      = phrases[idx][0];
+    var input_text     = phrases[idx][1];
+    var output_text    = phrases[idx][2];
+    var old_dix = idx == 0 ? phrases.length - 1 : idx - 1;
+    console.log(idx, old_dix, "++++++++++++")
+    var old_args_text   = args.innerHTML;
+    var old_input_text  = input.innerHTML;
+    var old_output_text = output.innerHTML;
+    console.log(args_text, input_text, output_text)
+    console.log(old_args_text, old_input_text, old_output_text)
+    var s4 = function() {fadeIn(output_text, output);}
+    var s3 = function() {letter(input_text, input, s4);}
+    var s2 = function() {letter(args_text, args, s3);}
+    var s1 = function() {unletter(old_args_text, args, s2);}
+    var s0 = function() {unletter(old_input_text, input, s1);}
+    fadeOut(old_output_text, output, s0, 10);
+}
+
+var fadeIn = function(text, element, next, step) {
+    step = step || 0
+    var nx = function() { fadeIn(text, element, next, ++step); }
+    if (step==0) {
+        element.innerHTML = "";
+        fadeInTimer = setTimeout(nx, 550);
+        return;
+    }
+    if (step==1) {element.innerHTML = text;}
+    if (step>10 || !text) { if (next) {next(); return;} else return;}
+    element.style.opacity = (step-1)/10;
+    element.style.filter = 'alpha(opacity=' + (step-1)*10 + ')';
+    fadeInTimer = setTimeout(nx, 50);
+}
+
+var fadeOut = function(text, element, next, step) {
+    if (step===10) element.innerHTML = text;
+    if (step<0 || !text) {
+        element.innerHTML = "";
+        if (next) {next(); return;}
+        else return;
+    }
+    element.style.opacity = step/10;
+    element.style.filter = 'alpha(opacity=' + step*10 + ')';
+    var nx = function() { fadeOut(text, element, next, --step); }
+    fadeOutTimer = setTimeout(nx, 50);
+}
+
+var unletter = function(text, element, next, timeout, index) {
+    timeout = timeout||10;
+    if (index==null) index = text.length;
+    if (index==-1 || !text.length) { if (next) {next(); return;} else return;}
+    element.innerHTML = text.substring(0, index);
+    var nx = function() { unletter(text, element, next, timeout, --index); }
+    unletterTimer = setTimeout(nx, timeout);
+}
+
+var letter = function(text, element, next, timeout, index) {
+    timeout = timeout||35;
+    index = index||0;
+    if (index > text.length || !text.length) { if (next) {next(); return;} else return;}
+    element.innerHTML = text.substring(0, index);
+    var nx = function() { letter(text, element, next, timeout, ++index); }
+    letterTimer = setTimeout(nx, timeout);
+}
+
+var reset = function() {
+    var timers = [timer, fadeInTimer, fadeOutTimer, letterTimer, unletterTimer];
+    timers.forEach(function (t) {
+      clearTimeout(t);
+    });
+
+    args.innerHTML = "";
+    input.innerHTML = "";
+    output.innerHTML = "";
+}
+
+timer = setTimeout(next, 3000);

docs/_themes/jrnl/static/less/docs.less

@@ -0,0 +1,283 @@
+body
+    {
+    font-family: "Open Sans", "Helvetica Neue", sans-serif;
+    font-weight: 300;
+    color: #333;
+    background: @white;
+    }
+body:not(.landing)
+    {
+    padding:0px 20px;
+    padding-top: 40px;
+    h2
+        {
+        margin-top: 40px;
+        }
+    }
+input
+    {
+    background: transparent;
+    border: 1px solid #999;
+    .border-radius(3px);
+    padding: 2px 5px;
+    color: #666;
+    font-family: "Open Sans";
+    font-weight: 300;
+    outline: none;
+    &:focus
+        {
+        background: white;
+        }
+    }
+div.related
+    {
+    background: rgba(255,200,200,.2);
+    }
+
+* > a.headerlink
+    {
+    display: none;
+    }
+
+h1, h2, h3, h4, h5, h6
+    {
+    font-weight: 300;
+    }
+
+a:link, a:visited
+    {
+    color: @orange;
+    text-decoration: none;
+    }
+a:hover, a:active
+    {
+    text-decoration: underline;
+    color: lighten(@orange, 10);
+    }
+
+.literal
+    {
+    color: @purple;
+    font-size: 1em;
+    background: lighten(@purple-light, 45);
+    padding: 1px 2px;
+    .border-radius(2px);
+    .box-shadow(inset 0px 0px 0px 1px lighten(@purple-light, 30));
+    }
+
+.note
+    {
+    .gradient(lighten(@purple-light, 10), lighten(@purple-light-shade, 10));
+    .border-radius(5px);
+    .box-shadow(0px 2px 3px @purple-shade);
+    padding: 10px 20px 10px 70px;
+    position: relative;
+    color: white;
+    .admonition-title {display: none;}
+    a { color: lighten(@orange, 30);}
+    &:before
+        {
+        content: "";
+        display: block;
+        .icon;
+        .icon.info;
+        position: absolute;
+        margin: auto;
+        top: 0; bottom: 0; left: 20px;
+        }
+    .literal, .highlight-note
+        {
+        color: white;
+        background: darken(@purple-light, 3);
+        padding: 1px 3px;
+        .border-radius(2px);
+        .box-shadow(inset 0px 0px 0px 1px lighten(@purple-light, 10));
+        }
+    .highlight-note
+        {
+        padding: 1px 10px;
+        pre:before
+            {
+            content: "$ ";
+            color: @orange;
+            }
+        }
+    }
+
+.highlight
+    {
+    background:transparent !important;
+    }
+.highlight-output, .highlight-javascript, .highlight-sh
+    {
+    .pre-block;
+    background: desaturate(lighten(@terminal,10), 10);
+    pre {color: white;}
+    }
+.highlight-python
+    {
+    .terminal;
+    pre
+        {
+        margin: 0 0 10px 0;
+        &:before
+            {
+            content: "$ ";
+            color: @orange;
+            }
+        }
+    }
+
+*:hover > a.headerlink
+    {
+    display: inline;
+    color: lighten(@purple-light, 30);
+    margin-left: 10px;
+    text-decoration: none;
+    &:hover { color: @purple-light; }
+    }
+
+tt
+    {
+    color: @purple;
+    font-size: 1.2em;
+    }
+ul li {
+    margin-bottom: 10px;
+}
+
+div.document
+    {
+    max-width: 900px;
+    margin: 20px auto;
+    position: relative;
+    }
+div.documentwrapper
+    {
+    margin-left: 240px;
+    padding: 0;
+    }
+aside
+    {
+    position: absolute;
+    width: 220px;
+    top: 0px;
+    .logo
+        {
+        margin: 0 auto 20px auto;
+        display: block;
+        width: 90px;
+        height: 98px;
+        }
+    color: #999;
+    h2, h3, h3 a:link, h3 a:visited
+        {
+        color: #777;
+        }
+
+    a:link, a:visited
+        {
+        color: #999;
+        }
+    a:hover, a:active
+        {
+        color: @orange;
+        }
+    input[type=submit]
+        {
+        display: none;
+        }
+    &>ul
+        {
+        margin: 0 4px;
+        padding: 0;
+        list-style: none;
+        &>li
+            {
+            margin-bottom: 10px;
+            font-size: 18px;
+            color: #777;
+            a:link, a:visited {color: #777;}
+            ul
+                {
+                margin: 10px 0 0 0;
+                padding-left: 20px;
+                font-size: 16px;
+                color: #999;
+                a:link, a:visited {color: #999;}
+                }
+            }
+        }
+    }
+
+div.footer
+    {
+    font-size: .8em;
+    text-align: center;
+    margin: 40px 0;
+    color: #999;
+    a:link, a:visited {color: #555;}
+    }
+
+@media screen and (max-width: 820px)
+    {
+        body:not(.landing){
+            padding-top: 130px;
+            .highlight-output,.highlight-python, .highlight-javascript
+                {
+                width: auto;
+                max-width: 500px;
+                }
+            .highlight-python
+                {
+                pre { margin: -10px 0 10px 0;}
+                &:before
+                    {
+                    height: 24px !important;
+                    line-height: 24px;
+                    font-size: .7em;
+                    }
+                &:after
+                    {
+                    background: none;
+                    }
+                }
+            aside
+                {
+                position: static;
+                }
+            div.documentwrapper
+                {
+                margin: 0px;
+                }
+            h1, .section
+                {
+                margin: 0px !important;
+                }
+            aside
+                {
+                background-color: #f0f0f0;
+                width: 100%;
+                margin: 5px -20px;
+                padding: 5px 20px 10px 20px;
+                }
+            #logolink
+                {
+                position: absolute;
+                top: -120px;
+                left: 50%;
+                margin-left: -49px;
+                }
+        }
+
+    }
+@media (-webkit-min-device-pixel-ratio: 1.5), (min--moz-device-pixel-ratio: 1.5), (-o-min-device-pixel-ratio: 3/2), (min-resolution: 1.5dppx)
+    {
+    aside .logo, body#landing #upper #logo
+        {
+        width: 90px;
+        height: 98px;
+        content: url(../img/logo@2x.png);
+        }
+
+    }

docs/_themes/jrnl/static/less/jrnl.less

@@ -0,0 +1,317 @@
+@import "retina";
+@import "3L";
+
+@white: #f7f8f9;
+@blue: #5e7dc5;
+@blue-light: #7c95ca;
+@terminal: #2f1e34;
+@purple: #47375d;
+@purple-shade: #413155;
+@purple-light: #725794;
+@purple-light-shade: #564371;
+@orange: #deaa09;
+
+.normalize();
+@import "docs.less";
+
+.icon,
+    {
+    .sprite("../img/icons.png", 32px, 5, 3, 8px);
+    &.secure {.sprite(0, 0)};
+    &.future {.sprite(1, 0)};
+    &.search {.sprite(2, 0)};
+    &.nli    {.sprite(3, 0)};
+    &.share  {.sprite(0, 1)};
+    &.sync   {.sprite(0, 1)};
+    &.dayone {.sprite(1, 1)};
+    &.github {.sprite(2, 1)};
+    &.folders{.sprite(3, 1)};
+    &.cal    {.sprite(4, 1)};
+    &.left   {.sprite(0, 2)};
+    &.right  {.sprite(1, 2)};
+    &.info   {.sprite(2, 2)};
+    }
+
+.pre-block
+    {
+    background: @terminal;
+    .border-radius(6px);
+    padding: 1px 20px;
+    margin: 40px auto;
+    width: 500px;
+    .box-shadow(0px 1px 8px darken(@white, 30));
+    position: relative;
+    color: @white;
+    font-family: "Monaco", "Courier New";
+    font-size: 12pt;
+    #args {color: #f6f7b9}
+    #output {color: #9278b5}
+    }
+
+.terminal
+    {
+    .pre-block;
+    @p: 20px;
+    padding: @p + 30px @p (@p - 10px) @p;
+    &:before
+        {
+        content: "Terminal";
+        display: block;
+        width: 100%;
+        position: absolute;
+        left: 0;
+        .box-shadow(inset 0px 1px 0px #f4f4f4, inset 0px -1px 0px #888);
+        margin-top: -50px;
+        // margin: -@p -@p 0px -@p;
+        text-align: center;
+        height: 30px;
+        line-height: 30px;
+        color: #777;
+        text-shadow: 0px 1px 0px #ddd;
+        .border-radius(5px 5px 0px 0px);
+        .gradient(#eaeaea, #bababa);
+        }
+    &:after
+        {
+        content: "";
+        width: 48px;
+        height: 30px;
+        position: absolute;
+        top: 0px;
+        left: 10px;
+        background: url(../img/terminal.png) no-repeat center center;
+        }
+    }
+
+body#landing
+    {
+    background-color: @purple;
+    font-family: "Open Sans", "Helvetica Neue", sans-serif;
+    font-weight: 300;
+    #twitter
+        {
+        display: block;
+        position: absolute;
+        top: 20px;
+        right: 20px;
+        border: 1px solid @purple;
+        padding: 5px 10px 5px 30px;
+        color: @purple;
+        .border-radius(3px);
+        .opacity(.7);
+        background: url(../img/twitter.png) 8px center no-repeat transparent;
+        &:hover, &:active
+            {
+            .opacity(1);
+            text-decoration: none;
+            }
+        }
+    #title, .row3, .row4, #prompt
+        {
+        width: 900px;
+        margin: 0px auto;
+        }
+    #upper
+        {
+        .clearfix;
+        background: @white;
+        .box-shadow(inset 0px -6px 6px -3px darken(@white, 10));
+        #title
+            {
+            width: 650px;
+            margin: 150px auto 75px auto;
+            }
+        img
+            {
+            float: left;
+            margin-right: 30px;
+            }
+        h1
+            {
+            color: @purple-light-shade;
+            font-weight: 300;
+            }
+        #prompt
+            {
+            width: 640px;
+            margin: 0 auto;
+            .clearfix;
+            }
+        .terminal
+            {
+            .border-radius(6px 6px 0px 0px);
+            float: left;
+            margin: 0px;
+            width: 500px;
+            min-height: 134px;
+            .border-box-sizing;
+            }
+        .pleft, .pright
+            {
+            text-align: center;
+            .border-box-sizing;
+            float: left;
+            padding-top: 50px;
+            width: 70px;
+            i {.opacity(60);}
+            i:hover {.opacity(1000); cursor: pointer;}
+            }
+        }
+    #nav
+        {
+        .gradient(@blue-light, @blue);
+        height: 60px;
+        .box-shadow(0px 6px 6px -3px @purple-shade);
+        text-align: center;
+        a#twitter-nav {display: none;}
+        a
+            {
+            color: @white;
+            text-shadow: 0px -1px 0px darken(@blue, 30);
+            text-decoration: none;
+            font-size: 14pt;
+            line-height: 60px;
+             margin: 0 40px;
+             &:hover
+                {
+                color: lighten(@orange, 20);
+                text-shadow: 0px -1px 0px darken(@orange, 15);
+                }
+            }
+        a.cta
+            {
+            .gradient(@purple-light, @purple-light-shade);
+            .box-shadow(0px 1px 0px @purple-shade);
+            .border-radius(5px);
+            padding: 6px 10px 5px 10px;
+            white-space: nowrap;
+            &:hover
+                {
+                .gradient(lighten(@orange, 10), darken(@orange, 5));
+                .box-shadow(0px 1px 0px darken(@orange, 15));
+                text-shadow: 0px -1px 0px darken(@orange, 15);
+                color: @white;
+
+                }
+            }
+        }
+    #lower
+        {
+        color: @white;
+        padding-top: 40px;
+        a
+            {
+            color: @orange;
+            text-decoration: none;
+            &:hover
+                {
+                color: lighten(@orange, 20);
+                text-decoration: underline;
+                }
+            }
+        .row3, .row4 {
+            .clearfix;
+            margin-bottom: 20px;
+            .col
+                {
+                position: relative;
+                padding-left: 40px;
+                i
+                    {
+                    position: absolute;
+                    left: 0;
+                    top: 16px;
+                    }
+                h3 {font-size: 12pt; margin-bottom: .5em;}
+                p {font-size: 10pt; margin: 0;}
+                float: left;
+                width: 25%;
+                padding-right: 2%;
+                .border-box-sizing;
+                &:last-child {padding-right: 0;}
+                }
+        }
+        .row3 .col { width: 33.3333%; }
+        .row4 .col { color: mix(@white, @purple, 80); i {.opacity(80);}}
+        }
+    }
+
+@media screen and (max-width: 680px)
+    {
+    body#landing
+        {
+        #nav
+            {
+            height: auto;
+            padding-bottom: 10px;
+            a, a#twitter-nav
+                {
+                display: block;
+                }
+            a.cta
+                {
+                margin: 10px;
+                padding: 1px;
+                }
+            }
+        #upper
+            {
+            #twitter { display: none;}
+            #title
+                {
+                    margin: 30px 0 10px 0;
+                }
+            #logo
+                {
+                backgound: red;
+                display: block;
+                float: none;
+                margin: 0px auto;
+                }
+            #title br {display: none;}
+            .pleft, .pright {display: none;}
+            #prompt, #title
+                {
+                width: 100%;
+                .border-box-sizing;
+                padding: 0px 20px;
+                }
+            .terminal
+                {
+                width: 100%;
+                }
+            }
+        }
+    }
+
+@media screen and (max-width: 900px)
+    {
+    body#landing
+        {
+        #lower
+            {
+            padding: 40px 20px;
+            .row3, .row4
+                {
+                margin: 0px;
+                width: auto;
+                }
+            .row3 .col, .row4 .col
+                {
+                float: none;
+                width: 100%;
+                text-align: center;
+                padding: 0px;
+                margin: 0 0 40px 0;
+                h3 {font-size: 1.5em;}
+                p {font-size: 1em;}
+
+                i
+                    {
+                    position: static;
+                    margin-bottom: -20px;
+                    }
+                }
+            }
+        }
+    }

docs/_themes/jrnl/static/less/retina.less

@@ -0,0 +1,35 @@
+// A helper mixin for applying high-resolution background images (http://www.retinajs.com)
+
+@highdpi: ~"(-webkit-min-device-pixel-ratio: 1.5), (min--moz-device-pixel-ratio: 1.5), (-o-min-device-pixel-ratio: 3/2), (min-resolution: 1.5dppx)";
+
+.at2x(@path, @w: auto, @h: auto) {
+  background-image: url(@path);
+  @at2x_path: ~`@{path}.replace(/\.\w+$/, function(match) { return "@2x" + match; })`;
+  background-size: @w @h;
+
+  @media @highdpi {
+    background-image: url("@{at2x_path}");
+  }
+}
+
+// Sprite mixin, see https://coderwall.com/p/oztebw
+
+.sprite (@path, @size, @w, @h, @pad: 0) when (isstring(@path))
+    {
+    background-image: url(@path);
+    width: @size;
+    height: @size;
+    display: inline-block;
+    @at2x_path: ~`@{path}.replace(/\.[\w\?=]+$/, function(match) { return "@2x" + match; })`;
+    font-size: @size + @pad;
+    background-size: (@size + @pad) * @w   (@size + @pad) * @h;
+    @media @highdpi
+        {
+        background-image: url("@{at2x_path}");
+        }
+    }
+
+.sprite(@x, @y)
+    {
+    background-position: -@x * 1em -@y * 1em;
+    }

docs/_themes/jrnl/static/sprites.svg

@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Generator: IcoMoon.io  -->
+
+<svg
+   xmlns:dc="http://purl.org/dc/elements/1.1/"
+   xmlns:cc="http://creativecommons.org/ns#"
+   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+   xmlns:svg="http://www.w3.org/2000/svg"
+   xmlns="http://www.w3.org/2000/svg"
+   xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+   xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+   width="1008"
+   height="48"
+   viewBox="0 0 1008 48"
+   data-tags="bookmark"
+   style="margin-left: -8px; margin-top: -8px;"
+   fill="#333333"
+   id="svg2"
+   version="1.1"
+   inkscape:version="0.48.2 r9819"
+   sodipodi:docname="sprites.svg">
+  <metadata
+     id="metadata30">
+    <rdf:RDF>
+      <cc:Work
+         rdf:about="">
+        <dc:format>image/svg+xml</dc:format>
+        <dc:type
+           rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+      </cc:Work>
+    </rdf:RDF>
+  </metadata>
+  <defs
+     id="defs28" />
+  <sodipodi:namedview
+     pagecolor="#ffffff"
+     bordercolor="#666666"
+     borderopacity="1"
+     objecttolerance="10"
+     gridtolerance="10"
+     guidetolerance="10"
+     inkscape:pageopacity="0"
+     inkscape:pageshadow="2"
+     inkscape:window-width="1562"
+     inkscape:window-height="1153"
+     id="namedview26"
+     showgrid="true"
+     inkscape:zoom="2.7460317"
+     inkscape:cx="651.02496"
+     inkscape:cy="38.446605"
+     inkscape:window-x="0"
+     inkscape:window-y="0"
+     inkscape:window-maximized="0"
+     inkscape:current-layer="svg2">
+    <inkscape:grid
+       type="xygrid"
+       id="grid3007" />
+  </sodipodi:namedview>
+  <path
+     d="M 141.818,22.909l-15.273-6.545l 6.105-4.361C 129.469,8.651, 124.985,6.545, 120,6.545  C 111.545,6.545, 104.5,12.556, 102.892,20.535L 98.819,18.849C 101.136,9.29, 109.728,2.182, 120,2.182c 6.452,0, 12.227,2.819, 16.224,7.27L 141.818,5.455L 141.818,22.909 z   M 107.35,35.998C 110.529,39.349, 115.015,41.455, 120,41.455c 8.487,0, 15.552-6.057, 17.123-14.084l 4.069,1.741C 138.888,38.69, 130.287,45.818, 120,45.818  c-6.452,0-12.229-2.819-16.224-7.27L 98.182,42.545l0-17.455 l 15.273,6.545L 107.35,35.998z"
+     id="path6" />
+  <path
+     d="M 224.71875 2.09375 L 224.71875 10.8125 C 224.71875 10.8125 201.34725 10.877 200.78125 36.125 C 201.12625 32.307 203.78675 17.375 224.71875 17.375 L 224.71875 23.90625 L 240 13 L 224.71875 2.09375 z M 198 7 C 194.676 7 192 9.676 192 13 L 192 40 C 192 43.324 194.676 46 198 46 L 229 46 C 232.324 46 235 43.324 235 40 L 235 23 L 232 25 L 232 40 C 232 41.662 230.662 43 229 43 L 198 43 C 196.338 43 195 41.662 195 40 L 195 13 C 195 11.338 196.338 10 198 10 L 210 10 L 217 7 L 198 7 z "
+     id="path8" />
+  <path
+     d="M 318,0.007c-9.941,0-18,8.059-18,18c0,3.039, 0.76,5.899, 2.093,8.412l-12.516,12.513l 0.011,0.009   C 288.609,39.903, 288,41.235, 288,42.715c0,2.924, 2.37,5.293, 5.293,5.293c 1.478,0, 2.811-0.609, 3.772-1.588l-0.003-0.003l 12.511-12.51   c 2.514,1.337, 5.379,2.1, 8.425,2.1c 9.941,0, 18-8.059, 18-18C 336,8.067, 327.941,0.007, 318,0.007z M 295.192,44.545   c-0.483,0.501-1.152,0.815-1.899,0.815c-1.462,0-2.647-1.183-2.647-2.646c0-0.747, 0.315-1.414, 0.815-1.899l-0.013-0.012l 12.099-12.099   c 1.057,1.426, 2.317,2.686, 3.741,3.747L 295.192,44.545z M 318,33.009c-8.283,0-15-6.719-15-15c0-8.283, 6.717-15, 15-15   c 8.281,0, 15,6.717, 15,15C 333,26.291, 326.282,33.009, 318,33.009zM 318,7.508 C 318.412,7.508 318.75,7.844 318.75,8.258 C 318.75,8.671 318.412,9.008 318,9.008 C 313.029,9.008 309,13.038 309,18.008 C 309,18.422 308.664,18.758 308.25,18.758 C 307.836,18.758 307.5,18.422 307.5,18.008 C 307.5,12.208 312.2,7.508 318,7.508 Z"
+     id="path10" />
+  <path
+     d="M 421.5,19.5L 421.5,13.5 c0-7.457-6.043-13.5-13.5-13.5c-7.457,0-13.5,6.043-13.5,13.5l0,6 c-2.486,0-4.5,2.014-4.5,4.5l0,4.5 l0,1.5 l0,3 l0,1.5 c0,7.457, 6.043,13.5, 13.5,13.5l 9,0    c 7.457,0, 13.5-6.043, 13.5-13.5l0-1.5 l0-3 l0-1.5 l0-4.5 C 426,21.513, 423.984,19.5, 421.5,19.5z M 397.5,13.5c0-5.799, 4.701-10.5, 10.5-10.5c 5.799,0, 10.5,4.701, 10.5,10.5l0,6 l-3,0 L 415.5,13.503    c0-4.143-3.357-7.5-7.5-7.5c-4.143,0-7.5,3.357-7.5,7.5L 400.5,19.5 L 397.5,19.5 L 397.5,13.5 z M 414,13.5l0,0.005 L 414,19.5 l-12,0 L 402,13.503 L 402,13.5 c0-3.314, 2.686-6, 6-6C 411.313,7.5, 414,10.187, 414,13.5z M 423,28.5   l0,1.5 l0,3 l0,1.5 c0,5.788-4.712,10.5-10.5,10.5l-9,0 c-5.788,0-10.5-4.712-10.5-10.5l0-1.5 l0-3 l0-1.5 l0-4.5 c0-0.828, 0.672-1.5, 1.5-1.5c 1.001,0, 1.999,0, 3,0l 21,0 c 0.999,0, 1.998,0, 3,0   c 0.827,0, 1.5,0.672, 1.5,1.5L 423,28.5 zM 408,28.5 C 409.656,28.5 411,29.843 411,31.5 C 411,32.413 410.508,34.152 410.001,35.523 C 409.591,36.63 409.173,37.497 408,37.497 C 406.922,37.497 406.409,36.621 406,35.508 C 405.5,34.14 405,32.41 405,31.5 C 405,29.843 406.344,28.5 408,28.5 Z"
+     id="path12" />
+  <path
+     d="M 524.093,3.87C 521.625,1.405, 518.376,0, 515.174,0c-2.701,0-5.189,1.002-7.005,2.816l-7.3,7.356  c-0.022,0.021-0.048,0.035-0.071,0.057c-0.012,0.012-0.019,0.028-0.032,0.039l 0.003,0.003L 485.276,25.884  c-0.714,0.71-1.232,1.593-1.519,2.558l-3.524,12.762C 480.229,41.238, 480,42.24, 480,42.75C 480,45.648, 482.353,48, 485.256,48  c 0.578,0, 1.695-0.276, 1.736-0.282l 12.717-3.344c 0.966-0.286, 1.844-0.808, 2.558-1.524l 22.895-23.075  C 529.325,15.609, 528.855,8.625, 524.093,3.87z M 504.021,35.693c-0.123-1.353-0.506-2.68-1.079-3.94l 14.183-14.181  c 0.867,2.739, 0.422,5.604-1.479,7.506c-0.012,0.012-0.027,0.019-0.038,0.032l 0.021,0.019l-11.592,11.685  C 504.037,36.439, 504.055,36.073, 504.021,35.693z M 502.189,30.384c-0.559-0.919-1.196-1.808-1.983-2.594  c-0.916-0.916-1.968-1.635-3.066-2.238l 14.298-14.298c 1.122,0.498, 2.198,1.208, 3.147,2.157c 0.812,0.808, 1.438,1.715, 1.921,2.656  L 502.189,30.384z M 495.729,24.843c-1.389-0.559-2.844-0.879-4.302-0.898l 11.555-11.643c 1.768-1.725, 4.344-2.222, 6.88-1.593  L 495.729,24.843z M 486.25,44.809C 486.087,44.847, 485.579,44.976, 485.233,45C 484,44.985, 483,43.983, 483,42.75  c 0.018-0.252, 0.118-0.685, 0.153-0.843l 1.579-5.721c 1.715-0.046, 3.56,0.621, 5.010,2.075c 1.473,1.47, 2.166,3.351, 2.091,5.087  L 486.25,44.809z M 493.311,42.956c-0.036-2.013-0.855-4.107-2.508-5.757C 489.24,35.634, 487.194,34.731, 485.154,34.65l 1.494-5.411  c 0.108-0.36, 0.323-0.716, 0.587-1.026c 3.009-2.154, 7.636-1.518, 10.851,1.7c 3.401,3.399, 3.925,8.379, 1.306,11.352  c-0.174,0.091-0.35,0.178-0.538,0.234L 493.311,42.956z M 523.036,17.658l-2.526,2.546c0-0.339, 0.041-0.664, 0.009-1.011  c-0.264-2.902-1.617-5.709-3.815-7.904c-2.444-2.445-5.684-3.848-8.892-3.857l 2.484-2.505C 511.541,3.687, 513.276,3, 515.174,3  c 2.413,0, 4.893,1.092, 6.8,2.993c 1.79,1.787, 2.856,4.006, 3.009,6.252C 525.123,14.34, 524.431,16.261, 523.036,17.658z"
+     id="path14" />
+  <path
+     d="M 600,10.5 C 600.414,10.5 600.75,10.836 600.75,11.25 C 600.75,11.664 600.412,12 600,12 C 592.009,12 585,16.206 585,21 C 585,21.414 584.664,21.75 584.25,21.75 C 583.836,21.75 583.5,21.414 583.5,21 C 583.5,15.309 591.056,10.5 600,10.5 ZM 600,3C 586.745,3, 576,11.059, 576,21c0,6.191, 4.168,11.649, 10.512,14.889   C 586.512,35.929, 586.5,35.956, 586.5,36c0,2.689-2.008,5.585-2.892,7.104c 0.002,0, 0.003,0, 0.003,0C 583.54,43.269, 583.5,43.45, 583.5,43.641   C 583.5,44.391, 584.107,45, 584.859,45C 585,45, 585.248,44.963, 585.241,44.979c 4.688-0.768, 9.104-5.075, 10.13-6.322C 596.87,38.877, 598.415,39, 600,39   c 13.253,0, 24-8.059, 24-18C 624,11.059, 613.254,3, 600,3z M 600,36c-1.376,0-2.787-0.105-4.194-0.31c-0.146-0.024-0.291-0.032-0.435-0.032   c-0.891,0-1.744,0.396-2.319,1.095c-0.642,0.782-2.469,2.526-4.627,3.809c 0.585-1.343, 1.042-2.847, 1.074-4.398   c 0.009-0.096, 0.013-0.194, 0.013-0.276c0-1.128-0.631-2.159-1.635-2.671C 582.318,30.378, 579,25.811, 579,21C 579,12.729, 588.42,6, 600,6   c 11.577,0, 21,6.729, 21,15C 621,29.271, 611.579,36, 600,36z"
+     id="path16" />
+  <path
+     d="M 774 0 L 771 26.84375 L 773.96875 27.15625 L 776.65625 3 L 807.34375 3 L 810.03125 27.15625 L 813 26.84375 L 810 0 L 774 0 z M 780 6 L 780 9 L 804 9 L 804 6 L 780 6 z M 780 12 L 780 15 L 804 15 L 804 12 L 780 12 z M 780 18 L 780 21 L 804 21 L 804 18 L 780 18 z M 780 24 L 780 27 L 804 27 L 804 24 L 780 24 z M 769.5 30 C 768.675 30 768.20775 30.6545 768.46875 31.4375 L 773.53125 46.5625 C 773.79225 47.3455 774.675 48 775.5 48 L 808.5 48 C 809.325 48 810.20775 47.3455 810.46875 46.5625 L 815.53125 31.4375 C 815.79325 30.6545 815.325 30 814.5 30 L 769.5 30 z M 786 33 L 798 33 L 798 36 L 786 36 L 786 33 z "
+     id="path20" />
+  <path
+     d="M 888 0 C 874.745 0 864 10.745 864 24 C 864 37.255 874.745 48 888 48 C 901.255 48 912 37.255 912 24 C 912 10.745 901.255 0 888 0 z M 888 3 C 899.59798 3 909 12.402018 909 24 C 909 33.513233 902.67471 41.543499 894 44.125 L 894 43.25 L 894 41.53125 L 894 39.65625 C 894 37.76525 893.32825 36.35975 892.03125 35.46875 C 892.84425 35.39075 893.60225 35.29625 894.28125 35.15625 C 894.96025 35.01625 895.6795 34.8275 896.4375 34.5625 C 897.1955 34.2975 897.86675 33.96075 898.46875 33.59375 C 899.07075 33.22675 899.66475 32.74225 900.21875 32.15625 C 900.77275 31.57025 901.21875 30.9295 901.59375 30.1875 C 901.96875 29.4455 902.281 28.539 902.5 27.5 C 902.719 26.461 902.8125 25.3125 902.8125 24.0625 C 902.8125 21.6405 902.04675 19.579 900.46875 17.875 C 901.18775 16 901.09375 13.953 900.21875 11.75 L 899.625 11.6875 C 899.219 11.6405 898.4915 11.82775 897.4375 12.21875 C 896.3835 12.60975 895.21925 13.234 893.90625 14.125 C 892.04725 13.609 890.09375 13.375 888.09375 13.375 C 886.07775 13.375 884.17175 13.61 882.34375 14.125 C 881.51575 13.562 880.742 13.118 880 12.75 C 879.258 12.383 878.66375 12.133 878.21875 12 C 877.77375 11.867 877.35175 11.781 876.96875 11.75 C 876.58575 11.719 876.32775 11.70275 876.21875 11.71875 C 876.10975 11.73475 876.046 11.76525 876 11.78125 C 875.125 14.00025 875.031 16.016 875.75 17.875 C 874.172 19.578 873.375 21.6405 873.375 24.0625 C 873.375 25.3125 873.49975 26.461 873.71875 27.5 C 873.93775 28.539 874.21875 29.4455 874.59375 30.1875 C 874.96875 30.9295 875.445 31.57025 876 32.15625 C 876.555 32.74225 877.149 33.22575 877.75 33.59375 C 878.351 33.96175 879.02325 34.2975 879.78125 34.5625 C 880.53925 34.8275 881.0085 35.01625 881.6875 35.15625 C 882.3665 35.29625 883.1255 35.422 883.9375 35.5 C 882.6565 36.375 882 37.75025 882 39.65625 L 882 41.34375 L 882 43.3125 L 882 44.125 C 873.3253 41.543499 867 33.513233 867 24 C 867 12.402018 876.40203 3 888 3 z "
+     id="path22" />
+  <path
+     d="M 978.072,25.441c-0.267,0.386-0.593,1.352-0.978,1.588c-0.386,0.235-0.821,0.401-1.304,0.492  c-0.485,0.093-0.986,0.134-1.503,0.118l0,2.29 l 3.7,0 L 977.988,39 l 2.987,0 l0-14.994 l-2.376,0 C 978.514,24.578, 978.339,25.056, 978.072,25.441z M 994.5,12l 3,0   c 0.83,0, 1.5-0.672, 1.5-1.5L 999,1.5 c0-0.828-0.67-1.5-1.5-1.5l-3,0 c-0.83,0-1.5,0.672-1.5,1.5l0,9 C 993,11.328, 993.67,12, 994.5,12z M 970.5,12l 3,0 c 0.828,0, 1.5-0.672, 1.5-1.5L 975,1.5   c0-0.828-0.672-1.5-1.5-1.5L 970.5,0 C 969.672,0, 969,0.672, 969,1.5l0,9 C 969,11.328, 969.672,12, 970.5,12z M 1005,6l-3,0 l0,7.5 c0,0.828-0.67,1.5-1.5,1.5l-9,0 c-0.83,0-1.5-0.672-1.5-1.5L 990,6 l-12,0 l0,7.5   c0,0.828-0.672,1.5-1.5,1.5L 967.5,15 c-0.828,0-1.5-0.672-1.5-1.5L 966,6 L 963,6 C 961.344,6, 960,7.344, 960,9l0,36 c0,1.656, 1.344,3, 3,3l 42,0 c 1.656,0, 3-1.344, 3-3L 1008,9   C 1008,7.344, 1006.656,6, 1005,6z M 1005,43.5c0,0.83-0.67,1.5-1.5,1.5L 964.5,45 c-0.828,0-1.5-0.67-1.5-1.5L 963,19.5 c0-0.828, 0.672-1.5, 1.5-1.5l 39,0 c 0.83,0, 1.5,0.672, 1.5,1.5L 1005,43.5 z   M 983.977,26.973l 7.452,0 c-1.404,1.728-2.534,3.488-3.397,5.558c-0.862,2.071-0.957,4.227-1.123,6.468l 3.196,0   c 0.013-0.999-0.292-2.078-0.076-3.234c 0.219-1.157, 0.528-2.298, 0.925-3.428c 0.401-1.128, 0.897-2.192, 1.494-3.19  c 0.594-1.001, 1.28-1.844, 2.050-2.529l0-2.613 l-10.522,0 L 983.976,26.973 z"
+     id="path24" />
+  <path
+     style="fill:#333333;fill-opacity:1;stroke:none"
+     d="M 9.46875,0 C 6.437316,0 4,2.4373158 4,5.46875 l 0,37.0625 C 4,45.562684 6.437316,48 9.46875,48 l 29.0625,0 C 41.562684,48 44,45.562684 44,42.53125 L 44,5.46875 C 44,2.4373158 41.562684,0 38.53125,0 z M 11,3 l 2,0 0,42 -2,0 C 8.784,45 7,43.216 7,41 L 7,7 C 7,4.784 8.784,3 11,3 z m 5,0 11,0 0,13 4,-3 4,3 0,-13 2,0 c 2.216,0 4,1.784 4,4 l 0,34 c 0,2.216 -1.784,4 -4,4 l -21,0 z"
+     id="rect3009"
+     inkscape:connector-curvature="0"
+     sodipodi:nodetypes="ssssssssssccssssccccccsssscc" />
+  <path
+     style="font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-indent:0;text-align:start;text-decoration:none;line-height:normal;letter-spacing:normal;word-spacing:normal;text-transform:none;direction:ltr;block-progression:tb;writing-mode:lr-tb;text-anchor:start;baseline-shift:baseline;color:#000000;fill:#333333;fill-opacity:1;stroke:none;stroke-width:3;marker:none;visibility:visible;display:inline;overflow:visible;enable-background:accumulate;font-family:Sans;-inkscape-font-specification:Sans"
+     d="M 697 -1 C 696.25371 -1 695.55642 -0.73689699 695 -0.28125 C 694.44358 0.17439699 694 0.87583597 694 1.71875 L 694 3 L 693 3 L 693 4 L 687.5 4 C 687.448 3.99729 687.39579 3.99729 687.34375 4 C 686.61183 4.0767148 685.99606 4.7640806 686 5.5 L 686 6 L 684.5 6 C 683.71462 6.0000785 683.00008 6.7146233 683 7.5 L 683 8.09375 C 682.42224 8.2980557 682.0033 8.8871877 682 9.5 L 682 12.5 C 682.00008 13.285377 682.71462 13.999921 683.5 14 L 686 14 L 686 39 L 684.75 40.1875 C 684.29266 40.451552 683.9953 40.971929 684 41.5 L 684 44.5 C 684.00008 45.285377 684.71462 45.999921 685.5 46 L 693.40625 46 L 700.5 46 L 700.65625 46 L 708.5 46 C 709.28538 45.999921 709.99992 45.285377 710 44.5 L 710 41.5 C 710.005 40.971929 709.70734 40.451552 709.25 40.1875 L 708 39 L 708 14 L 710.5 14 C 711.28538 13.999921 711.99992 13.285377 712 12.5 L 712 9.5 C 711.997 8.8871877 711.57776 8.2980557 711 8.09375 L 711 7.5 C 710.99992 6.7146233 710.28538 6.0000785 709.5 6 L 708 6 L 708 5.5 C 707.99992 4.7146233 707.28538 4.0000785 706.5 4 L 701 4 L 701 3 L 700 3 L 700 1.71875 C 700 0.87583597 699.55642 0.17439702 699 -0.28125 C 698.44358 -0.73689702 697.74629 -1 697 -1 z M 697 1 C 697.20585 1 697.5132 1.1129297 697.71875 1.28125 C 697.9243 1.4495703 698 1.6095221 698 1.71875 L 698 3 L 696 3 L 696 1.71875 C 696 1.6095221 696.0757 1.4495702 696.28125 1.28125 C 696.4868 1.1129298 696.79415 1 697 1 z M 688 7 L 706 7 L 706 8 L 708 8 C 707.9472 8.7370898 708.11489 9.2632977 709 9.0625 L 709 12 L 705 12 L 689 12 L 685 12 L 685 9.15625 C 685.81891 9.2047089 685.94068 8.6267293 686 8 L 688 8 L 688 7 z M 689 14 L 705 14 L 705 41 L 707 42.375 L 707 43 L 687 43 L 687 42.375 L 689 41 L 689 14 z M 691 16 L 691 20 L 693 20 L 693 16 L 691 16 z M 694 16 L 694 20 L 696 20 L 696 16 L 694 16 z M 698 16 L 698 20 L 700 20 L 700 16 L 698 16 z M 701 16 L 701 20 L 703 20 L 703 16 L 701 16 z M 691 21 L 691 25 L 693 25 L 693 21 L 691 21 z M 694 21 L 694 25 L 696 25 L 696 21 L 694 21 z M 698 21 L 698 25 L 700 25 L 700 21 L 698 21 z M 701 21 L 701 25 L 703 25 L 703 21 L 701 21 z M 699.375 29.625 C 698.61451 29.625 698 30.239511 698 31 C 698 31.760489 698.61451 32.375 699.375 32.375 C 700.13549 32.375 700.75 31.760489 700.75 31 C 700.75 30.239511 700.13549 29.625 699.375 29.625 z "
+     id="path3858" />
+</svg>

docs/_themes/jrnl/theme.conf

@@ -0,0 +1,7 @@
+[theme]
+inherit = basic
+stylesheet = css/jrnl.css
+pygments_style = flask_theme_support.FlaskyStyle
+
+[options]
+touch_icon =

docs/advanced.md

@@ -1,117 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Advanced Usage
-
-## Configuration File
-
-`jrnl` has a wide variety of options that can be customized through the config file,
-including templates, formats, multiple journals, and more. See
-the [configuration file reference](./reference-config-file.md) for details
-or read on for some common use cases.
-
-### Multiple journal files
-
-You can configure `jrnl`to use with multiple journals (eg.
-`private` and `work`) by defining more journals in your [config file](./reference-config-file.md),
-for example:
-
-``` yaml
-journals:
-  default: ~/journal.txt
-  work: ~/work.txt
-```
-
-The `default` journal gets created the first time you start `jrnl`
-Now you can access the `work` journal by using `jrnl work` instead of
-`jrnl`, eg.
-
-``` sh
-jrnl work at 10am: Meeting with @Steve
-jrnl work -n 3
-```
-
-will both use `~/work.txt`, while `jrnl -n 3` will display the last
-three entries from `~/journal.txt` (and so does `jrnl default -n 3`).
-
-You can also override the default options for each individual journal.
-If your `jrnl.yaml` looks like this:
-
-``` yaml
-encrypt: false
-journals:
-  default: ~/journal.txt
-  work:
-    journal: ~/work.txt
-    encrypt: true
-  food: ~/my_recipes.txt
-```
-
-Your `default` and your `food` journals won't be encrypted, however your
-`work` journal will!
-
-You can override all options that are present at
-the top level of `jrnl.yaml`, just make sure that at the very least
-you specify a `journal: ...` key that points to the journal file of
-that journal.
-
-Consider the following example configuration
-
-``` yaml
-editor: vi -c startinsert 
-journals: 
-  default: ~/journal.txt 
-  work: 
-    journal: ~/work.txt 
-    encrypt: true 
-    display_format: json 
-    editor: code -rw 
-  food:
-    display_format: markdown 
-    journal: ~/recipes.txt 
-```
-
-The `work` journal is encrypted, prints to `json` by default, and is edited using an existing window of VSCode. Similarly, the `food` journal prints to markdown by default, but uses all the other defaults.
-
-### Modifying Configurations from the Command line 
-
-You can override a configuration field for the current instance of `jrnl` using `--config-override CONFIG_KEY CONFIG_VALUE` where `CONFIG_KEY` is a valid configuration field, specified in dot notation and `CONFIG_VALUE` is the (valid) desired override value. The dot notation can be used to change config keys within other keys, such as `colors.title` for the `title` key within the `colors` key.
-
-You can specify multiple overrides as multiple calls to `--config-override`.
-
-!!! note
-    These overrides allow you to modify ***any*** field of your jrnl configuration. We trust that you know what you are doing. 
-
-#### Examples: 
-
-``` sh
-# Create an entry using the `stdin` prompt, for rapid logging
-jrnl --config-override editor ""
-
-# Populate a project's log
-jrnl --config-override journals.todo "$(git rev-parse --show-toplevel)/todo.txt" todo find my towel 
-
-# Pass multiple overrides 
-jrnl --config-override display_format fancy --config-override linewrap 20 \
---config-override colors.title green
-```
-
-### Using an alternate config
-
-You can specify an alternate configuration file for the current instance of `jrnl` using `--config-file CONFIG_FILE_PATH` where
-`CONFIG_FILE_PATH` is a path to an alternate `jrnl` configuration file. 
-
-#### Examples:
-
-``` sh
-# Use personalised configuration file for personal journal entries
-jrnl --config-file ~/foo/jrnl/personal-config.yaml
-
-# Use alternate configuration file for work-related entries
-jrnl --config-file ~/foo/jrnl/work-config.yaml
-
-# Use default configuration file (created on first run)
-jrnl
-```

docs/advanced.rst

@@ -0,0 +1,123 @@
+.. _advanced:
+
+Advanced Usage
+==============
+
+Configuration File
+-------------------
+
+You can configure the way jrnl behaves in a configuration file. By default, this is ``~/.jrnl_config``. If you have the ``XDG_CONFIG_HOME`` variable set, the configuration file will be saved under ``$XDG_CONFIG_HOME/jrnl``.
+
+.. note::
+
+    On Windows, The configuration file is typically found at ``C:\Users\[Your Username]\.jrnl_config``.
+
+
+The configuration file is a simple JSON file with the following options and can be edited with any plain text editor.
+
+- ``journals``
+      paths to your journal files
+- ``editor``
+    if set, executes this command to launch an external editor for writing your entries, e.g. ``vim``. Some editors require special options to work properly, see :doc:`FAQ <recipes>` for details.
+- ``encrypt``
+    if ``true``, encrypts your journal using AES.
+- ``tagsymbols``
+    Symbols to be interpreted as tags. (See note below)
+- ``default_hour`` and ``default_minute``
+    if you supply a date, such as ``last thursday``, but no specific time, the entry will be created at this time
+- ``timeformat``
+    how to format the timestamps in your journal, see the `python docs <http://docs.python.org/library/time.html#time.strftime>`_ for reference
+- ``highlight``
+    if ``true``, tags will be highlighted in cyan.
+- ``linewrap``
+    controls the width of the output. Set to ``false`` if you don't want to wrap long lines.
+
+.. note::
+
+      Although it seems intuitive to use the `#` character for tags, there's a drawback: on most shells, this is interpreted as a meta-character starting a comment. This means that if you type
+
+      .. code-block:: note
+
+          jrnl Implemented endless scrolling on the #frontend of our website.
+
+      your bash will chop off everything after the ``#`` before passing it to _jrnl_). To avoid this, wrap your input into quotation marks like this:
+
+      .. code-block:: note
+
+          jrnl "Implemented endless scrolling on the #frontend of our website."
+
+      Or use the built-in prompt or an external editor to compose your entries.
+
+DayOne Integration
+------------------
+
+Using your DayOne journal instead of a flat text file is dead simple -- instead of pointing to a text file, change your ``.jrnl_config`` to point to your DayOne journal. This is a folder named something like ``Journal_dayone`` or ``Journal.dayone``, and it's located at
+
+* ``~/Library/Application Support/Day One/`` by default
+* ``~/Dropbox/Apps/Day One/`` if you're syncing with Dropbox and
+* ``~/Library/Mobile Documents/5U8NS4GX82~com~dayoneapp~dayone/Documents/`` if you're syncing with iCloud.
+
+Instead of all entries being in a single file, each entry will live in a separate `plist` file. So your ``.jrnl_config`` should look like this:
+
+.. code-block:: javascript
+
+    {
+      ...
+      "journals": {
+        "default": "~/journal.txt",
+        "dayone": "~/Library/Mobile Documents/5U8NS4GX82~com~dayoneapp~dayone/Documents/Journal_dayone"
+    }
+
+
+Multiple journal files
+----------------------
+
+You can configure _jrnl_ to use with multiple journals (eg. ``private`` and ``work``) by defining more journals in your ``.jrnl_config``, for example:
+
+.. code-block:: javascript
+
+    {
+    ...
+      "journals": {
+        "default": "~/journal.txt",
+        "work":    "~/work.txt"
+      }
+    }
+
+The ``default`` journal gets created the first time you start _jrnl_. Now you can access the ``work`` journal by using ``jrnl work`` instead of ``jrnl``, eg. ::
+
+    jrnl work at 10am: Meeting with @Steve
+
+::
+
+    jrnl work -n 3
+
+will both use ``~/work.txt``, while ``jrnl -n 3`` will display the last three entries from ``~/journal.txt`` (and so does ``jrnl default -n 3``).
+
+You can also override the default options for each individual journal. If you ``.jrnl_config`` looks like this:
+
+.. code-block:: javascript
+
+    {
+      ...
+      "encrypt": false
+      "journals": {
+        "default": "~/journal.txt",
+        "work": {
+          "journal": "~/work.txt",
+          "encrypt": true
+        },
+        "food": "~/my_recipes.txt",
+    }
+
+Your ``default`` and your ``food`` journals won't be encrypted, however your ``work`` journal will! You can override all options that are present at the top level of ``.jrnl_config``, just make sure that at the very least you specify a ``"journal": ...`` key that points to the journal file of that journal.
+
+.. note::
+
+    Changing ``encrypt`` to a different value will not encrypt or decrypt your journal file, it merely says whether or not your journal `is` encrypted. Hence manually changing this option will most likely result in your journal file being impossible to load.
+
+Known Issues
+~~~~~~~~~~~~
+
+- The Windows shell prior to Windows 7 has issues with unicode encoding. If you want to use non-ascii characters, change the codepage with ``chcp 1252`` before using `jrnl` (Thanks to Yves Pouplard for solving this!)
+- _jrnl_ relies on the `PyCrypto` package to encrypt journals, which has some known problems with installing on Windows and within virtual environments.

docs/conf.py

@@ -0,0 +1,257 @@
+# -*- coding: utf-8 -*-
+#
+# jrnl documentation build configuration file, created by
+# sphinx-quickstart on Wed Aug  7 13:22:51 2013.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+sys.path.insert(0, os.path.abspath('..'))
+import jrnl
+from jrnl import __version__
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.insert(0, os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = ['sphinx.ext.autodoc']
+
+# Add any paths that contain templates here, relative to this directory.
+templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General information about the project.
+project = u'jrnl'
+copyright = u'jrnl is made with love by <a href="http://www.1450.me">Manuel Ebert</a> and <a href="https://github.com/maebert/jrnl/graphs/contributors" title="Contributors">other fabulous people</a>. If you need help, tweet to <a href="https://twitter.com/maebert" title="Follow @maebert on twitter">@maebert</a> or <a href="https://github.com/maebert/jrnl/issues/new" title="Open a new issue on Github">submit an issue</a> on Github.'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = __version__
+# The full version, including alpha/beta/rc tags.
+release = version
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#language = None
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'native'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+# If true, keep warnings as "system message" paragraphs in the built documents.
+#keep_warnings = False
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes.
+html_theme = 'jrnl'
+
+# On read the docs, use their standard theme.
+RTD_NEW_THEME = True
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+#html_theme_path = []
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+#html_title = None
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = None
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+#html_logo = None
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+#html_favicon = None
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+#html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+html_show_sourcelink = False
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+html_show_sphinx = False
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+#html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# This is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = None
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'jrnldoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+latex_elements = {
+# The paper size ('letterpaper' or 'a4paper').
+#'papersize': 'letterpaper',
+
+# The font size ('10pt', '11pt' or '12pt').
+#'pointsize': '10pt',
+
+# Additional stuff for the LaTeX preamble.
+#'preamble': '',
+}
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index', 'jrnl.tex', u'jrnl Documentation',
+   u'Manuel Ebert', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+    ('index', 'jrnl', u'jrnl Documentation',
+     [u'Manuel Ebert'], 1)
+]
+
+# If true, show URL addresses after external links.
+#man_show_urls = False
+
+
+# -- Options for Texinfo output ------------------------------------------------
+
+# Grouping the document tree into Texinfo files. List of tuples
+# (source start file, target name, title, author,
+#  dir menu entry, description, category)
+texinfo_documents = [
+  ('index', 'jrnl', u'jrnl Documentation',
+   u'Manuel Ebert', 'jrnl', 'One line description of project.',
+   'Miscellaneous'),
+]
+
+# Documents to append as an appendix to all manuals.
+#texinfo_appendices = []
+
+# If false, no module index is generated.
+#texinfo_domain_indices = True
+
+# How to display URL addresses: 'footnote', 'no', or 'inline'.
+#texinfo_show_urls = 'footnote'
+
+# If true, do not generate a @detailmenu in the "Top" node's menu.
+#texinfo_no_detailmenu = False
+sys.path.append(os.path.abspath('_themes'))
+html_theme_path = ['_themes']
+html_theme = 'jrnl'

docs/contributing.md

@@ -1,132 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Contributing to jrnl
-
-We welcome contributions to jrnl, whether it's through reporting bugs, improving the documentation, testing releases, engaging in discussion on features and bugs, or writing code.
-
-## Table of Contents
- * [Code of Conduct](#code-of-conduct)
- * [Reporting Bugs](#reporting-bugs)
- * [Editing Documentation](#editing-documentation)
- * [Testing](#testing)
- * [Submitting feature requests and ideas](#submitting-feature-requests-and-ideas)
- * [Developing jrnl](#developing)
-
-## Code of Conduct
-
-Before starting, please read the [Code of Conduct](https://github.com/jrnl-org/jrnl/blob/develop/CODE_OF_CONDUCT.md).
-
-## Reporting Bugs
-
-Please report bugs by [opening a new issue](https://github.com/jrnl-org/jrnl/issues/new/choose) and describing it as well as possible. Many bugs are specific to a particular operating system and Python version, so please include that information!
-
-## Editing Documentation
-
-If you find a typo or a mistake in the docs, please fix it right away and send a pull request. If you're unsure what to change but still see a problem, you can [open a new issue](https://github.com/jrnl-org/jrnl/issues/new/choose) with the "Documentation change" type.
-
-To edit the documentation, edit the `docs/*.md` files on the **develop** branch. You can see the result by running `poe docs-run` inside the project's root directory, then navigating your browser to [localhost:8000](http://localhost:8000).
-
-### External editors and tips and tricks
-
-If you'd like to share a jrnl command line trick that you find useful, you may find it worthwhile to add it to the ["Tips and Tricks" section](tips-and-tricks.md). For advice on how to integrate a particular external editor, you can add to the ["External Editors" section](external-editors.md).
-
-## Testing
-
-Much of the work of maintaining jrnl involves testing rather than coding.
-
-The nature of jrnl means we deal with extremely sensitive data, and can't risk data loss. While jrnl does have a comprehensive automated testing suite, user testing is crucial to mitigating this risk.
-
-### Prereleases
-
-[Prereleases are deployed through PyPi much like normal releases](https://pypi.org/project/jrnl/#history). You can use [pipx](https://pypi.org/project/pipx/) to fetch them and test them. See the [changelog](https://github.com/jrnl-org/jrnl/blob/develop/CHANGELOG.md) for information on what has changed with each release.
-
-### Pull requests
-
-If you are comfortable enough with git, feel free to fetch particular [pull requests](https://github.com/jrnl-org/jrnl/pulls), test them yourself, and report back your findings. Bonus points if you can add a screencast of how the new feature works.
-
-### Confirm bug reports
-
-There are always [open bugs among our GitHub issues](https://github.com/jrnl-org/jrnl/issues?q=is%3Aissue+is%3Aopen+label%3Abug) and many are specific to a particular OS, Python version, or jrnl version. A simple comment like "Confirmed on jrnl v2.2, MacOS 10.15, Python 3.8.1" would be extremely helpful in tracking down bugs.
-
-### Automate tests
-
-See the develop section below for information on how to contribute new automated tests.
-
-## Submitting feature requests and ideas
-
-If you have a feature request or idea for jrnl, please [open a new issue](https://github.com/jrnl-org/jrnl/issues/new/choose) and describe the goal of the feature, and any relevant use cases. We'll discuss the issue with you, and decide if it's a good fit for the project.
-
-When discussing new features, please keep in mind our design goals. jrnl strives to
-[do one thing well](https://en.wikipedia.org/wiki/Unix_philosophy). To us, that means:
-
-* being _nimble_
-* having a simple interface
-* avoiding duplicating functionality
-
-## Developing
-
-### Getting your environment set up
-
-You will need to install [poetry](https://python-poetry.org/) to develop jrnl. It will take care of all of the project's other dependencies.
-
-### Understanding the branches
-
-jrnl uses two primary branches:
-
- * `develop` - for ongoing development
- * `release` - for releases
-
-In general, pull requests should be made on the `develop` branch.
-
-### Common development commands
-
-You can find an inventory of commands in the `pyproject.toml`. Users can run the commands by typing `poe` followed by the name of the command ([Poe the Poet](https://github.com/nat-n/poethepoet) can be installed on its own, or as part of `poetry install`).
-
-A typical development workflow includes:
-
- * Installing dependencies:
-    * `poetry install`
- * Activate virtual environment:
-    * `poetry shell`
- * Running the source in a virtual environment:
-    * `jrnl` (with or without arguments as necessary)
- * Running tests:
-     * `poe test`
- * Formatting the code to standardize its style:
-     * `poe format`
-
-### Updating automated tests
-
-When resolving bugs or adding new functionality, please add tests to prevent that functionality from breaking in the future. If you notice any functionality that isn't covered in the tests, feel free to submit a test-only pull request as well.
-
-For testing, jrnl uses [pytest](https://docs.pytest.org) for unit tests, and [pytest-bdd](https://pytest-bdd.readthedocs.io/) for integration testing. All tests are in the `tests` folder.
-
-Many tests can be created by only editing `*.feature` files with the same format as other tests. For more complicated functionality, you may need to implement steps in `tests/lib/` which are then executed by your tests in the `feature` files.
-
-### Submitting pull requests
-
-When you're ready, feel free to submit a pull request (PR). The jrnl maintainers generally review the pull requests every two weeks, but the continuous integration pipeline will run on automated tests on it within a matter of minutes and will report back any issues it has found with your code across a variety of environments.
-
-The pull request template contains a checklist full of housekeeping items. Please fill them out as necessary when you submit.
-
-If a pull request contains failing tests, it probably will not be reviewed, and it definitely will not be approved. However, if you need help resolving a failing test, please mention that in your PR.
-
-### Finding things to work on
-
-You can search the [jrnl GitHub issues](https://github.com/jrnl-org/jrnl/issues) by [label](https://github.com/jrnl-org/jrnl/labels) for things to work on. Here are some labels worth searching:
-
-* [critical](https://github.com/jrnl-org/jrnl/labels/critical)
-* [help wanted](https://github.com/jrnl-org/jrnl/labels/help%20wanted)
-* [bug](https://github.com/jrnl-org/jrnl/labels/bug)
-* [enhancement](https://github.com/jrnl-org/jrnl/labels/enhancement)
-
-You can also get a feel for the project's priorities by reviewing the [milestones](https://github.com/jrnl-org/jrnl/milestones).
-
-### A note for new programmers and programmers new to python
-
-Although jrnl has grown quite a bit since its inception, the overall complexity (for an end-user program) is fairly low, and we hope you'll find the code easy enough to understand.
-
-If you have a question, please don't hesitate to ask! Python is known for its welcoming community and openness to novice programmers, so feel free to fork the code and play around with it! If you create something you want to share with us, please create a pull request. We never expect pull requests to be perfect, idiomatic, instantly mergeable code. We can work through it together!

docs/encryption.md

@@ -1,160 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Encryption
-
-## A Note on Security
-
-While `jrnl` follows best practices, total security is never possible in the
-real world. There are a number of ways that people can at least partially
-compromise your `jrnl` data. See the [Privacy and Security](./privacy-and-security.md) page
-for more information.
-
-## Encrypting and Decrypting
-
-Existing plain text journal files can be encrypted using the `--encrypt`
-command:
-
-``` sh
-jrnl --encrypt [FILENAME]
-```
-
-You can then enter a new password, and the unencrypted file will replaced with
-the new encrypted file.
-
-This command also works to change the password for a journal file that is
-already encrypted. `jrnl` will prompt you for the current password and then new
-password.
-
-Conversely,
-
-``` sh
-jrnl --decrypt [FILENAME]
-```
-
-replaces the encrypted journal file with a plain text file. You can also specify
-a filename, e.g., `jrnl --decrypt plain_text_copy.txt`, to leave the original
-encrypted file untouched and create a new plain text file next to it.
-
-!!! note
-    Changing `encrypt` in your [config file](./reference-config-file.md) to
-    a different value will not encrypt or decrypt your
-    journal file. It merely says whether or not your journal
-    is encrypted. Hence manually changing
-    this option will most likely result in your journal file being
-    impossible to load. This is why the above commands are necessary.
-
-## Storing Passwords in Your Keychain
-
-Nobody can recover or reset your `jrnl` password. If you lose it,
-your data will be inaccessible forever.
-
-For this reason, when encrypting a journal, `jrnl` asks whether you would like
-to store the password in your system's keychain. An added benefit is that you
-will not need to enter the password when interacting with the journal file.
-
-If you don't initially store the password in your keychain but decide to do so
-later---or if you want to store it in one computer's keychain but not in another
-computer's---you can run `jrnl --encrypt` on an encrypted journal and use the
-same password again. This will trigger the keychain storage prompt.
-
-## Manual Decryption
-
-The easiest way to decrypt your journal is with `jrnl --decrypt`, but you could
-also decrypt your journal manually if needed. To do this, you can use any
-program that supports the AES algorithm (specifically AES-CBC), and you'll need
-the following relevant information for decryption:
-
-- **Key:** The key used for encryption is the
-    [SHA-256](https://en.wikipedia.org/wiki/SHA-2) hash of your password.
-- **Initialization vector (IV):** The IV is stored in the first 16 bytes of
-    your encrypted journal file.
-- **The actual text of the journal** (everything after the first 16 bytes in
-    the encrypted journal file) is encoded in
-    [UTF-8](https://en.wikipedia.org/wiki/UTF-8) and padded according to
-    [PKCS\#7](https://en.wikipedia.org/wiki/PKCS_7) before being encrypted.
-
-If you'd like an example of what this might look like in script form, please
-see below for some examples of Python scripts that you could use to manually
-decrypt your journal.
-
-
-
-!!! note
-    These are only examples, and are only here to illustrate that your journal files
-    will still be recoverable even if `jrnl` isn't around anymore. Please use 
-    `jrnl --decrypt` if available.
-
-**Example for jrnl v2 files**:
-``` python
-#!/usr/bin/env python3
-"""
-Decrypt a jrnl v2 encrypted journal.
-
-Note: the `cryptography` module must be installed (you can do this with
-something like `pip3 install crytography`)
-"""
-
-import base64
-import getpass
-from pathlib import Path
-
-from cryptography.fernet import Fernet
-from cryptography.hazmat.backends import default_backend
-from cryptography.hazmat.primitives import hashes
-from cryptography.hazmat.primitives.kdf.pbkdf2 import PBKDF2HMAC
-
-filepath = input("journal file path: ")
-password = getpass.getpass("Password: ")
-
-with open(Path(filepath), "rb") as f:
-    ciphertext = f.read()
-
-password = password.encode("utf-8")
-kdf = PBKDF2HMAC(
-    algorithm=hashes.SHA256(),
-    length=32,
-    salt=b"\xf2\xd5q\x0e\xc1\x8d.\xde\xdc\x8e6t\x89\x04\xce\xf8",
-    iterations=100_000,
-    backend=default_backend(),
-)
-
-key = base64.urlsafe_b64encode(kdf.derive(password))
-
-print(Fernet(key).decrypt(ciphertext).decode("utf-8"))
-```
-
-**Example for jrnl v1 files**:
-``` python
-#!/usr/bin/env python3
-"""
-Decrypt a jrnl v1 encrypted journal.
-
-Note: the `pycrypto` module must be installed (you can do this with something
-like `pip3 install pycrypto`)
-"""
-
-import argparse
-import getpass
-import hashlib
-
-from Crypto.Cipher import AES
-
-parser = argparse.ArgumentParser()
-parser.add_argument("filepath", help="journal file to decrypt")
-args = parser.parse_args()
-
-pwd = getpass.getpass()
-key = hashlib.sha256(pwd.encode("utf-8")).digest()
-
-with open(args.filepath, "rb") as f:
-    ciphertext = f.read()
-
-crypto = AES.new(key, AES.MODE_CBC, ciphertext[:16])
-plain = crypto.decrypt(ciphertext[16:])
-plain = plain.strip(plain[-1:])
-plain = plain.decode("utf-8")
-print(plain)
-```

docs/encryption.rst

@@ -0,0 +1,47 @@
+.. _encryption:
+
+Encryption
+==========
+
+Encrypting and decrypting
+-------------------------
+
+
+If you don't choose to encrypt your file when you run `jrnl` for the first time, you can encrypt your existing journal file or change its password using ::
+
+    jrnl --encrypt
+
+If it is already encrypted, you will first be asked for the current password. You can then enter a new password and your plain journal will replaced by the encrypted file. Conversely, ::
+
+    jrnl --decrypt
+
+will replace your encrypted journal file by a Journal in plain text. You can also specify a filename, ie. ``jrnl --decrypt plain_text_copy.txt``, to leave your original file untouched.
+
+
+Storing passwords in your keychain
+----------------------------------
+
+Whenever you encrypt your journal, you are asked whether you want to store the encryption password in your keychain. If you do this, you won't have to enter your password every time you want to write or read your journal.
+
+If you don't initially store the password in the keychain but decide to do so at a later point -- or maybe want to store it on one computer but not on another -- you can simply run ``jrnl --encrypt`` on an encrypted journal and use the same password again.
+
+A note on security
+------------------
+
+While jrnl follows best practises, true security is an illusion. Specifically, jrnl will leave traces in your memory and your shell history -- it's meant to keep journals secure in transit, for example when storing it on an `untrusted <http://techcrunch.com/2014/04/09/condoleezza-rice-joins-dropboxs-board/>`_ services such as Dropbox. If you're concerned about security, disable history logging for journal in your ``.bashrc`` ::
+
+    HISTINGNORE="jrnl *"
+
+Manual decryption
+-----------------
+
+Should you ever want to decrypt your journal manually, you can do so with any program that supports the AES algorithm in CBC. The key used for encryption is the SHA-256-hash of your password, the IV (initialisation vector) is stored in the first 16 bytes of the encrypted file. The plain text is encoded in UTF-8 and padded according to PKCS#7 before being encrypted. So, to decrypt a journal file in python, run::
+
+    import hashlib, Crypto.Cipher
+    key = hashlib.sha256(my_password).digest()
+    with open("my_journal.txt") as f:
+        cipher = f.read()
+        crypto = AES.new(key, AES.MODE_CBC, iv = cipher[:16])
+        plain = crypto.decrypt(cipher[16:])
+        plain = plain.strip(plain[-1])
+        plain = plain.decode("utf-8")

docs/export.rst

@@ -0,0 +1,69 @@
+.. _export:
+
+Import and Export
+=================
+
+Tag export
+----------
+
+With::
+
+    jrnl --tags
+
+you'll get a list of all tags you used in your journal, sorted by most frequent. Tags occurring several times in the same entry are only counted as one.
+
+List of all entries
+-------------------
+
+::
+
+    jrnl --short
+
+Will only display the date and title of each entry.
+
+JSON export
+-----------
+
+Can do::
+
+    jrnl --export json
+
+Why not create a `beautiful timeline <http://timeline.verite.co/>`_ of your journal?
+
+Markdown export
+---------------
+
+Use::
+
+    jrnl --export markdown
+
+Markdown is a simple markup language that is human readable and can be used to be rendered to other formats (html, pdf). This README for example is formatted in markdown and github makes it look nice.
+
+Text export
+-----------
+
+::
+
+    jrnl --export text
+
+Pretty-prints your entire journal.
+
+Export to files
+---------------
+
+You can specify the output file of your exported journal using the `-o` argument::
+
+    jrnl --export md -o journal.md
+
+The above command will generate a file named `journal.md`. If the `-o` argument is a directory, jrnl will export each entry into an individual file::
+
+    jrnl --export json -o my_entries/
+
+The contents of `my_entries/` will then look like this:
+
+.. code-block:: output
+
+    my_entries/
+    |- 2013_06_03_a-beautiful-day.json
+    |- 2013_06_07_dinner-with-gabriel.json
+    |- ...

docs/external-editors.md

@@ -1,137 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# External editors
-
-Configure your preferred external editor by updating the `editor` option
-in your [configuration file](./reference-config-file.md#editor). If your editor is not 
-in your operating system's `PATH` environment variable, then you will have to 
-enter the full path of your editor.
-
-Once it's configured, you can create an entry as a new document in your editor using the `jrnl` 
-command by itself:
-
-``` text
-jrnl
-```
-
-You can specify the time and title of the entry as usual on the first line of the document. 
-
-If you want, you can skip the editor by including a quick entry with the `jrnl` command:
-
-``` text
-jrnl yesterday: All my troubles seemed so far away.
-```
-
-If you want to start the entry on the command line and continue writing in your chosen editor, 
-use the `--edit` flag. For example:
-
-``` text
-jrnl yesterday: All my troubles seemed so far away. --edit
-```
-
-!!! note
-    To save and log any entry edits, save and close the file.
-
-All editors must be [blocking processes](https://en.wikipedia.org/wiki/Blocking_(computing)) to work with jrnl. Some editors, such as [micro](https://micro-editor.github.io/), are blocking by default, though others can be made to block with additional arguments, such as many of those documented below. If jrnl opens your editor but finishes running immediately, then your editor is not a blocking process, and you may be able to correct that with one of the suggestions below.
-
-Please see [this section](./privacy-and-security.md#editor-history) about how
-your editor might leak sensitive information and how to mitigate that risk.
-
-## Sublime Text
-
-To use [Sublime Text](https://www.sublimetext.com/), install the command line
-tools for Sublime Text and configure your `jrnl.yaml` like this:
-
-```yaml
-editor: "subl -w"
-```
-
-Note the `-w` flag to make sure `jrnl` waits for Sublime Text to close the
-file before writing into the journal.
-
-## Visual Studio Code
-
-[Visual Studio Code](https://code.visualstudio.com) also requires a flag
-that tells the process to wait until the file is closed before exiting:
-
-```yaml
-editor: "code --wait"
-```
-
-On Windows, `code` is not added to the path by default, so you'll need to
-enter the full path to your `code.exe` file, or add it to the `PATH` variable.
-
-## MacVim
-
-Also similar to Sublime Text, MacVim must be started with a flag that tells
-the the process to wait until the file is closed before passing control
-back to journal. In the case of MacVim, this is `-f`:
-
-```yaml
-editor: "mvim -f"
-```
-
-## Vim/Neovim
-
-To use any of the Vim derivatives as editor in Linux, simply set the `editor`
-to the executable:
-
-```yaml
-editor: "vim"
-# or
-editor: "nvim"
-```
-
-## iA Writer
-
-On OS X, you can use the fabulous [iA
-Writer](http://www.iawriter.com/mac) to write entries. Configure your
-`jrnl.yaml` like this:
-
-```yaml
-editor: "open -b pro.writer.mac -Wn"
-```
-
-What does this do? `open -b ...` opens a file using the application
-identified by the bundle identifier (a unique string for every app out
-there). `-Wn` tells the application to wait until it's closed before
-passing back control, and to use a new instance of the application.
-
-If the `pro.writer.mac` bundle identifier is not found on your system,
-you can find the right string to use by inspecting iA Writer's
-`Info.plist` file in your shell:
-
-```sh
-grep -A 1 CFBundleIdentifier /Applications/iA\ Writer.app/Contents/Info.plist
-```
-
-## Notepad++ on Windows
-
-To set [Notepad++](http://notepad-plus-plus.org/) as your editor, edit
-the `jrnl` config file (`jrnl.yaml`) like this:
-
-```yaml
-editor: "C:\\Program Files (x86)\\Notepad++\\notepad++.exe -multiInst -nosession"
-```
-
-The double backslashes are needed so `jrnl` can read the file path
-correctly. The `-multiInst -nosession` options will cause `jrnl` to open
-its own Notepad++ window.
-
-
-## emacs
-
-To use `emacs` as your editor, edit the `jrnl` config file (`jrnl.yaml`) like this:
-
-```yaml
-editor: emacsclient -a "" -c
-```
-
-When you're done editing the message, save and `C-x #` to close the buffer and stop the emacsclient process.
-
-## Other editors
-
-If you're using another editor and would like to share, feel free to [contribute documentation](./contributing.md#editing-documentation) on it.

docs/formats.md

@@ -1,354 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Formats
-
-`jrnl` supports a variety of alternate formats. These can be used to display your
-journal in a different manner than the `jrnl` default, and can even be used to pipe data
-from your journal for use in another program to create reports, or do whatever you want
-with your `jrnl` data.
-
-Any of these formats can be used with a search (e.g. `jrnl -contains "lorem ipsum"
---format json`) to display the results of that search in the given format, or can be
-used alone (e.g. `jrnl --format json`) to display all entries from the selected journal.
-
-This page shows examples of all the built-in formats, but since `jrnl` supports adding
-more formats through plugins, you may have more available on your system. Please see
-`jrnl --help` for a list of which formats are available on your system.
-
-Any of these formats can be used interchangeably, and are only grouped into "display",
-"data", and "report" formats below for convenience.
-
-## Display Formats
-These formats are mainly intended for displaying your journal in the terminal. Even so,
-they can still be used in the same way as any other format (like written to a file, if
-you choose).
-
-### Pretty
-``` sh
-jrnl --format pretty
-# or
-jrnl -1 # any search
-```
-
-This is the default format in `jrnl`. If no `--format` is given, `pretty` will be used.
-
-It displays the timestamp of each entry formatted to by the user config followed by the
-title on the same line. Then the body of the entry is shown below.
-
-This format is configurable through these values from your config file (see
-[Advanced Usage](./advanced.md) for more details):
-
-- `colors`
-    - `body`
-    - `date`
-    - `tags`
-    - `title`
-- `indent_character`
-- `linewrap`
-- `timeformat`
-
-**Example output**:
-``` sh
-2020-06-28 18:22 This is the first sample entry
-| This is the sample body text of the first sample entry.
-
-2020-07-01 20:00 This is the second sample entry
-| This is the sample body text of the second sample entry, but
-| this one has a @tag.
-
-2020-07-02 09:00 This is the third sample entry
-| This is the sample body text of the third sample entry.
-```
-
-### Short
-
-``` sh
-jrnl --format short
-# or
-jrnl --short
-```
-
-This will shorten entries to display only the date and title. It is essentially the
-`pretty` format but without the body of each entry. This can be useful if you have long
-journal entries and only want to see a list of entries that match your search.
-
-**Example output**:
-``` sh
-2020-06-28 18:22 This is the first sample entry
-2020-07-01 20:00 This is the second sample entry
-2020-07-02 09:00 This is the third sample entry
-```
-
-### Fancy (or Boxed)
-``` sh
-jrnl --format fancy
-# or
-jrnl --format boxed
-```
-
-This format outlines each entry with a border. This makes it much easier to tell where
-each entry starts and ends. It's an example of how free-form the formats can be, and also
-just looks kinda ~*~fancy~*~, if you're into that kind of thing.
-
-**Example output**:
-``` sh
-┎──────────────────────────────────────────────────────────────────────╮2020-06-28 18:22
-┃ This is the first sample entry                                       ╘═══════════════╕
-┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
-┃ This is the sample body text of the first sample entry.                              │
-┖──────────────────────────────────────────────────────────────────────────────────────┘
-┎──────────────────────────────────────────────────────────────────────╮2020-07-01 20:00
-┃ This is the second sample entry                                      ╘═══════════════╕
-┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
-┃ This is the sample body text of the second sample entry, but this one has a @tag.    │
-┖──────────────────────────────────────────────────────────────────────────────────────┘
-┎──────────────────────────────────────────────────────────────────────╮2020-07-02 09:00
-┃ This is the third sample entry                                       ╘═══════════════╕
-┠╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌┤
-┃ This is the sample body text of the third sample entry.                              │
-┖──────────────────────────────────────────────────────────────────────────────────────┘
-```
-
-## Data Formats
-These formats are mainly intended for piping or exporting your journal to other
-programs. Even so, they can still be used in the same way as any other format (like
-written to a file, or displayed in your terminal, if you want).
-
-!!! note
-You may see boxed messages like "2 entries found" when using these formats, but
-those messages are written to `stderr` instead of `stdout`, and won't be piped when
-using the `|` operator.
-
-### JSON
-
-``` sh
-jrnl --format json
-```
-
-JSON is a very handy format used by many programs and has support in nearly every
-programming language. There are many things you could do with JSON data. Maybe you could
-use `jq` ([project page](https://github.com/stedolan/jq)) to filter through the fields in your journal.
-Like this:
-
-``` sh
-$ j -3 --format json | jq '.entries[].date'                                                                                                                            jrnl-GFqVlfgP-py3.8 
-"2020-06-28"
-"2020-07-01"
-"2020-07-02"
-```
-
-Or why not create a [beautiful timeline](http://timeline.knightlab.com/) of your journal?
-
-**Example output**:
-``` json
-{
-  "tags": {
-    "@tag": 1
-  },
-  "entries": [
-    {
-      "title": "This is the first sample entry",
-      "body": "This is the sample body text of the first sample entry.",
-      "date": "2020-06-28",
-      "time": "18:22",
-      "tags": [],
-      "starred": false
-    },
-    {
-      "title": "This is the second sample entry",
-      "body": "This is the sample body text of the second sample entry, but this one has a @tag.",
-      "date": "2020-07-01",
-      "time": "20:00",
-      "tags": [
-        "@tag"
-      ],
-      "starred": false
-    },
-    {
-      "title": "This is the third sample entry",
-      "body": "This is the sample body text of the third sample entry.",
-      "date": "2020-07-02",
-      "time": "09:00",
-      "tags": [],
-      "starred": false
-    }
-  ]
-}
-```
-
-### Markdown
-
-``` sh
-jrnl --format markdown
-# or
-jrnl --format md
-```
-
-Markdown is a simple markup language that is human readable and can be used to be
-rendered to other formats (html, pdf). `jrnl`'s
-[README](https://github.com/jrnl-org/jrnl/blob/develop/README.md) for example is
-formatted in markdown, then Github adds some formatting to make it look nice.
-
-The markdown format groups entries by date (first by year, then by month), and adds
-header markings as needed (e.g. `#`, `##`, etc). If you already have markdown header
-markings in your journal, they will be incremented as necessary to make them fit under
-these new headers (i.e. `#` will become `##`).
-
-This format can be very useful, for example, to export a journal to a program that
-converts markdown to html to make a website or a blog from your journal.
-
-**Example output**:
-``` markdown
-# 2020
-
-## June
-
-### 2020-06-28 18:22 This is the first sample entry
-
-This is the sample body text of the first sample entry.
-
-## July
-
-### 2020-07-01 20:00 This is the second sample entry
-
-This is the sample body text of the second sample entry, but this one has a @tag.
-
-### 2020-07-02 09:00 This is the third sample entry
-
-This is the sample body text of the third sample entry.
-```
-
-### Plain Text
-
-``` sh
-jrnl --format text
-# or
-jrnl --format txt
-```
-
-This outputs your journal in the same plain-text format that `jrnl` uses to store your
-journal on disk. This format is particularly useful for importing and exporting journals
-within `jrnl`.
-
-You can use it, for example, to move entries from one journal to another, or to create a
-new journal with search results from another journal.
-
-**Example output**:
-``` sh
-[2020-06-28 18:22] This is the first sample entry
-This is the sample body text of the first sample entry.
-
-[2020-07-01 20:00] This is the second sample entry
-This is the sample body text of the second sample entry, but this one has a @tag.
-
-[2020-07-02 09:00] This is the third sample entry
-This is the sample body text of the third sample entry.
-```
-
-### XML
-``` sh
-jrnl --format xml
-```
-
-This outputs your journal into XML format. XML is a commonly used data format and is
-supported by many programs and programming languages.
-
-**Example output**:
-``` xml
-<?xml version="1.0" ?>
-<journal>
-        <entries>
-                <entry date="2020-06-28T18:22:00" starred="">This is the first sample entry This is the sample body text of the first sample entry.</entry>
-                <entry date="2020-07-01T20:00:00" starred="">
-                        <tag name="@tag"/>
-                        This is the second sample entry This is the sample body text of the second sample entry, but this one has a @tag.
-                </entry>
-                <entry date="2020-07-02T09:00:00" starred="">*This is the third sample entry, and is starred This is the sample body text of the third sample entry.</entry>
-        </entries>
-        <tags>
-                <tag name="@tag">1</tag>
-        </tags>
-</journal>
-```
-
-### YAML
-``` sh
-jrnl --format yaml --file 'my_directory/'
-```
-
-This outputs your journal into YAML format. YAML is a commonly used data format and is
-supported by many programs and programming languages. [Exporting to directories](#exporting-to-directories) is the
-only supported YAML export option and each entry will be written to a separate file.
-
-**Example file**:
-``` yaml
-title: This is the second sample entry
-date: 2020-07-01 20:00
-starred: False
-tags: tag
-
-This is the sample body text of the second sample entry, but this one has a @tag.
-```
-
-## Report formats
-Since formats use your journal data and display it in different ways, they can also be
-used to create reports.
-
-### Tags
-
-``` sh
-jrnl --format tags
-# or
-jrnl --tags
-```
-
-This format is a simple example of how formats can be used to create reports. It
-displays each tag, and a count of how many entries in which tag appears in your journal
-(or in the search results), sorted by most frequent.
-
-Example output:
-``` sh
-@one                 : 32
-@two                 : 17
-@three               : 4
-```
-
-## Options
-
-### Exporting with `--file`
-
-Example: `jrnl --format json --file /some/path/to/a/file.txt`
-
-By default, `jrnl` will output entries to your terminal. But if you provide `--file`
-along with a filename, the same output that would have been to your terminal will be
-written to the file instead. This is the same as piping the output to a file.
-
-So, in bash for example, the following two statements are equivalent:
-
-``` sh
-jrnl --format json --file myjournal.json
-```
-
-``` sh
-jrnl --format json > myjournal.json
-```
-
-#### Exporting to directories
-
-If the `--file` argument is a directory, jrnl will export each entry into an individual file:
-
-``` sh
-jrnl --format yaml --file my_entries/
-```
-
-The contents of `my_entries/` will then look like this:
-
-``` output
-my_entries/
-|- 2013_06_03_a-beautiful-day.yaml
-|- 2013_06_07_dinner-with-gabriel.yaml
-|- ...
-```

docs/index.rst

@@ -0,0 +1,20 @@
+.. jrnl documentation master file, created by
+   sphinx-quickstart on Wed Aug  7 13:22:51 2013.
+
+jrnl: The command-line journal
+==============================
+
+Release v\ |version|.
+
+Contents:
+
+.. toctree::
+   :maxdepth: 3
+
+   overview
+   installation
+   usage
+   encryption
+   export
+   advanced
+   recipes

docs/installation.md

@@ -1,43 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Getting started
-
-## Installation
-
-The easiest way to install `jrnl` is using
-[pipx](https://pipx.pypa.io/stable/installation/)
-with [Python](https://www.python.org/) 3.10+:
-
-``` sh
-pipx install jrnl
-```
-
-!!! tip
-     Do not use `sudo` while installing `jrnl`. This may lead to path issues.
-
-The first time you run `jrnl` you will be asked where your journal file
-should be created and whether you wish to encrypt it.
-
-## Quickstart
-
-To make a new entry, just type
-
-``` text
-jrnl yesterday: Called in sick. Used the time to clean, and spent 4h on writing my book.
-```
-
-and hit return. `yesterday:` will be interpreted as a time stamp.
-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:
-
-``` output
-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](advanced.md) *jrnl* to use your external editor.

docs/installation.rst

@@ -0,0 +1,41 @@
+.. _download:
+
+Getting started
+===============
+
+Installation
+------------
+
+Install *jrnl* using pip ::
+
+    pip install jrnl
+
+Or, if you want the option to encrypt your journal, ::
+
+    pip install jrnl[encrypted]
+
+to install the dependencies for encrypting journals as well.
+
+.. note::
+
+   Installing the encryption library, `pycrypto`, requires a `gcc` compiler. For this reason, jrnl will not install `pycrypto` unless explicitly told so like this. You can `install PyCrypto manually <https://www.dlitz.net/software/pycrypto/>`_ first or install it with ``pip install pycrypto`` if you have a `gcc` compiler.
+
+The first time you run ``jrnl`` you will be asked where your journal file should be created and whether you wish to encrypt it.
+
+
+Quickstart
+----------
+
+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 time stamp. 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:
+
+.. code-block:: output
+
+   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.
+

docs/journal-types.md

@@ -1,65 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Journal Types
-`jrnl` can store your journal in a few different ways:
-
- - a single text file (encrypted or otherwise)
- - a folder structure organized by date containing unencrypted text files
- - the DayOne Classic format
-
-There is no need to specify what type of journal you'd like to use. Instead,
-`jrnl` will automatically detect the journal type based on whether you're
-referencing a file or a folder in your [config file](advanced.md),
-and if it's a folder, whether or not DayOne Classic content exists in it.
-
-## Single File
-The single file format is the most flexible, as it can be [encrypted](encryption.md).
-To use it, enter any path that is a file or does not already exist. You can
-use any extension. `jrnl` will automatically create the file when you save
-your first entry.
-
-## Folder
-The folder journal format organizes your entries into subfolders for the year
-and month and `.txt` files for each day. If there are multiple entries in a day,
-they all appear in the same `.txt` file.
-
-The directory tree structure is in this format: `YYYY/MM/DD.txt`. For instance, if
-you have an entry on May 5th, 2021 in a folder journal at `~/folderjournal`, it will
-be located in: `~/folderjournal/2021/05/05.txt`
-
-!!! note
-Creating a new folder journal can be done in two ways:
-
-* Create a folder with the name of the journal before running `jrnl`. Otherwise, when you run `jrnl` for the first time, it will assume that you are creating a single file journal instead, and it will create a file at that path.
-* Create a new journal in your [config_file](advanced.md) and end the path with a ``/`` (on a POSIX system like Linux or MacOSX) or a ``\`` (on a Windows system). The folder will be created automatically if it doesn't exist.
-
-!!! note
-Folder journals can't be encrypted.
-
-## Day One Classic
-`jrnl` supports the original data format used by DayOne. It's similar to the folder
-journal format, except it's identified by either of these characteristics:
-
-* the folder has a `.dayone` extension
-* the folder has a subfolder named `entries`
-
-This is not to be confused with the DayOne 2.0 format, [which is very different](https://help.dayoneapp.com/en/articles/1187337-day-one-classic-is-retired).
-
-!!! note
-DayOne Classic journals can't be encrypted.
-
-## Changing your journal type
-You can't simply modify a journal's configuration to change its type. Instead,
-define a new journal as the type you'd like, and use
-[piping](https://en.wikipedia.org/wiki/Redirection_(computing)#Piping)
-to export your old journal as `txt` to an import command on your new journal.
-
-For instance, if you have a `projects` journal you would like to import into
-a `new` journal, you would run the following after setting up the configuration
-for your `new` journal:
-```
-jrnl projects --format txt | jrnl new --import
-```

docs/overview.md

@@ -1,64 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Overview
-
-`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](http://en.wikipedia.org/wiki/Advanced_Encryption_Standard).
-
-`jrnl` has most of the features you need, and few of the ones you don't.
-
-## Plain Text
-
-`jrnl` stores each journal in plain text. You can store `jrnl` files anywhere,
-including in shared folders to keep them synchronized between devices. Journal
-files are compact (thousands of entries take up less than 1 MiB) and can be read
-by almost any electronic device, now and for the foreseeable future.
-
-## Tags
-
-To make it easier to find entries later, `jrnl` includes support for inline tags
-(the default tag symbol is `@`). You can find and filter entries by using tags
-along with other search criteria.
-
-## Support for Multiple Journals
-  
-`jrnl` includes support for the creation of multiple journals, each of which
-can be stored as a single file or as a set of files. Entries are automatically
-timestamped in a human-readable format that makes it easy to view multiple
-entries at a time. `jrnl` can easily find the entries you want so that you can
-read them or edit them.
-
-## Support for External Editors
-
-`jrnl` plays nicely with your favorite text editor. You may prefer to write
-journal entries in an editor. Or you may want to make changes that require a
-more comprehensive application. `jrnl` can filter specific entries and pass them
-to the [external editor](./external-editors.md) of your choice.
-
-## Encryption
-  
-`jrnl` includes support for [AES
-encryption](http://en.wikipedia.org/wiki/Advanced_Encryption_Standard). See the
-[encryption page](./encryption.md) for more information.
-
-## Import and Export
-
-`jrnl` makes it easy to import entries from other sources. Existing entries can
-be exported in a variety of [formats](./formats.md).
-
-## Multi-Platform Support
-
-`jrnl` is compatible with most operating systems. You can [download](./installation.md) it using one
-of a variety of package managers, or you can build from source.
-
-## Open-Source
-
-`jrnl` is written in [Python](https://www.python.org) and maintained by a
-[friendly community](https://github.com/jrnl-org/jrnl) of open-source software
-enthusiasts.

docs/overview.rst

@@ -0,0 +1,23 @@
+.. _overview:
+
+Overview
+===============
+
+What is jrnl?
+-------------
+
+`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.
+
+`jrnl` also plays nice with the fabulous `DayOne <http://dayoneapp.com>`_ and can read and write directly from and to DayOne Journals.
+
+Optionally, your journal can be encrypted using the `256-bit AES <http://en.wikipedia.org/wiki/Advanced_Encryption_Standard>`_.
+
+Why keep a journal?
+-------------------
+
+Journals aren't only for 13-year old girls 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. Or use it as a quick way to keep a change log. Or use it to keep a lab book.
+

docs/privacy-and-security.md

@@ -1,232 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Privacy and Security
-
-`jrnl` is designed with privacy and security in mind, but like any other
-program there are some limitations to be aware of.
-
-## Password strength
-
-`jrnl` doesn't enforce password strength requirements. Short or commonly-used
-passwords can be easily circumvented by someone with basic security skills
-to access to your encrypted `jrnl` file.
-
-## Plausible deniability
-
-You may be able to hide the contents of your journal behind a layer of encryption,
-but if someone has access to your configuration file, then they can figure out that
-you have a journal, where that journal file is, and when you last edited it.
-With a sufficient power imbalance, someone may be able to force you to unencrypt
-it through non-technical means.
-
-## Spying
-
-While `jrnl` can protect against unauthorized access to your journal entries while
-it isn't open, it cannot protect you against an unsafe computer/location.
-For example:
-
-- Someone installs a keylogger, tracking what you type into your journal.
-- Someone watches your screen while you write your entry.
-- Someone installs a backdoor into `jrnl` or poisons your journal into revealing your entries.
-
-## Saved Passwords
-
-When creating an encrypted journal, you'll be prompted as to whether or not you
-want to "store the password in your keychain." This keychain is accessed using
-the [Python keyring library](https://pypi.org/project/keyring/), which has different
-behavior depending on your operating system.
-
-In Windows, the keychain is the Windows Credential Manager (WCM), which can't be locked
-and can be accessed by any other application running under your username. If this is
-a concern for you, you may not want to store your password.
-
-## Shell history
-
-Since you can enter entries from the command line, any tool that logs command
-line actions is a potential security risk. See below for how to deal with this
-problem in various shells.
-
-### bash
-
-You can disable history logging for jrnl by adding this line into your
-`~/.bashrc` file:
-
-``` sh
-HISTIGNORE="$HISTIGNORE:jrnl *"
-```
-
-To delete existing `jrnl` commands from `bash` history, simply delete them from
-your bash history file. The default location of this file is `~/.bash_history`,
-but you can run `echo "$HISTFILE"` to find it if needed.  Also, you can run
-`history -c` to delete all commands from your history.
-
-### zsh
-
-You can disable history logging for jrnl by adding this to your `~/.zshrc`
-file:
-
-``` sh
-setopt HIST_IGNORE_SPACE
-alias jrnl=" jrnl"
-```
-
-To delete existing `jrnl` commands from `zsh` history, simply remove them from
-your zsh history file. The default location of this file is `~/.zsh_history`,
-but you can run `echo "$HISTFILE"` to find it if needed. Also, you can run
-`history -c` to delete all commands from your history.
-
-### fish
-
-By default `fish` will not log any command that starts with a space. If you
-want to always run jrnl with a space before it, then you can add this to your
-`~/.config/fish/config.fish` file:
-
-``` sh
-abbr --add jrnl " jrnl"
-```
-
-To delete existing jrnl commands from `fish` history, run `history delete --prefix 'jrnl '`.
-
-### Windows Command Prompt
-
-Windows doesn't log history to disk, but it does keep it in your command prompt
-session. Close the command prompt or press `Alt`+`F7` to clear your history
-after journaling.
-
-## Files in transit from editor to jrnl
-
-When creating or editing an entry, `jrnl` uses a unencrypted temporary file on
-disk in order to give your editor access to your journal. After you close your
-editor, `jrnl` then deletes this temporary file.
-
-So, if you have saved a journal entry but haven't closed your editor yet, the
-unencrypted temporary remains on your disk. If your computer were to shut off
-during this time, or the `jrnl` process were killed unexpectedly, then the
-unencrypted temporary file will remain on your disk. You can mitigate this
-issue by only saving with your editor right before closing it. You can also
-manually delete these files from your temporary folder. By default, they
-are named `jrnl*.jrnl`, but if you use a
-[template](reference-config-file.md#template), they will have the same
-extension as the template.
-
-## Editor history
-
-Some editors keep usage history stored on disk for future use. This can be a
-security risk in the sense that sensitive information can leak via recent
-search patterns or editor commands.
-
-### Visual Studio Code
-
-Visual Studio Code stores the contents of saved files to allow you to restore or
-review the contents later. You can disable this feature for all files by unchecking
-the `workbench.localHistory.enabled` setting in the
-[Settings editor](https://code.visualstudio.com/docs/getstarted/settings#_settings-editor).
-
-Alternatively, you can disable this feature for specific files by configuring a
-[pattern](https://code.visualstudio.com/docs/editor/codebasics#_advanced-search-options)
-in the `workbench.localHistory.exclude` setting. To exclude unencrypted temporary files generated
-by `jrnl`, you can set the `**/jrnl*.jrnl` (unless you are using a
-[template](reference-config-file.md#template)) pattern for the `workbench.localHistory.exclude` setting
-in the [Settings editor](https://code.visualstudio.com/docs/getstarted/settings#_settings-editor).
-
-!!! note
-    On Windows, the history location is typically found at
-    `%APPDATA%\Code\User\History`.
-
-Visual Studio Code also creates a copy of all unsaved files that are open.
-It stores these copies in a backup location that's automatically cleaned when
-you save the file. However, if your computer shuts off before you save the file,
-or the Visual Studio Code process stops unexpectedly, then an unencrypted
-temporary file may remain on your disk. You can manually delete these files
-from the backup location.
-
-!!! note
-    On Windows, the backup location is typically found at
-    `%APPDATA%\Code\Backups`.
-
-### Vim
-
-Vim stores progress data in a so called Viminfo file located at `~/.viminfo`
-which contains all sorts of user data including command line history, search
-string history, search/substitute patterns, contents of register etc. Also to
-be able to recover opened files after an unexpected application close Vim uses
-swap files.
-
-These options as well as other leaky features can be disabled by setting the
-`editor` key in the Jrnl settings like this:
-
-``` yaml
-editor: "vim -c 'set viminfo= noswapfile noundofile nobackup nowritebackup noshelltemp history=0 nomodeline secure'"
-```
-
-To disable all plugins and custom configurations and start Vim with the default
-configuration `-u NONE` can be passed on the command line as well. This will
-ensure that any rogue plugins or other difficult to catch information leaks are
-eliminated. The downside to this is that the editor experience will decrease
-quite a bit.
-
-To instead let Vim automatically detect when a Jrnl file is being edited an
-autocommand can be used. Place this in your `~/.vimrc`:
-
-``` vim
-autocmd BufNewFile,BufReadPre *.jrnl setlocal viminfo= noswapfile noundofile nobackup nowritebackup noshelltemp history=0 nomodeline secure
-```
-
-!!! note
-    If you're using a [template](reference-config-file.md#template), you will
-    have to use the template's file extension instead of `.jrnl`.
-
-See `:h <option>` in Vim for more information about the options mentioned.
-
-### Neovim
-
-Neovim strives to be mostly compatible with Vim and has therefore similar
-functionality as Vim. One difference in Neovim is that the Viminfo file is
-instead called the ShaDa ("shared data") file which resides in
-`~/.local/state/nvim` (`~/.local/share/nvim` pre Neovim v0.8.0). The ShaDa file
-can be disabled in the same way as for Vim.
-
-``` yaml
-editor: "nvim -c 'set shada= noswapfile noundofile nobackup nowritebackup noshelltemp history=0 nomodeline secure'"
-```
-
-`-u NONE` can be passed here as well to start a session with the default configs.
-
-As for Vim above we can create an autocommand in Vimscript:
-
-``` vim
-autocmd BufNewFile,BufReadPre *.jrnl setlocal shada= noswapfile noundofile nobackup nowritebackup noshelltemp history=0 nomodeline secure
-```
-
-or the same but in Lua:
-
-``` lua
-vim.api.nvim_create_autocmd( {"BufNewFile","BufReadPre" }, {
-  group = vim.api.nvim_create_augroup("PrivateJrnl", {}),
-  pattern = "*.jrnl",
-  callback = function()
-    vim.o.shada = ""
-    vim.o.swapfile = false
-    vim.o.undofile = false
-    vim.o.backup = false
-    vim.o.writebackup = false
-    vim.o.shelltemp = false
-    vim.o.history = 0
-    vim.o.modeline = false
-    vim.o.secure = true
-  end,
-})
-```
-
-!!! note
-    If you're using a [template](reference-config-file.md#template), you will
-    have to use the template's file extension instead of `.jrnl`.
-
-Please see `:h <option>` in Neovim for more information about the options mentioned.
-
-## Notice any other risks?
-
-Please let the maintainers know by [filing an issue on GitHub](https://github.com/jrnl-org/jrnl/issues).

docs/recipes.rst

@@ -0,0 +1,125 @@
+.. _recipes:
+
+FAQ
+===
+
+Recipes
+-------
+
+Co-occurrence of tags
+~~~~~~~~~~~~~~~~~~~~~
+
+If I want to find out how often I mentioned my flatmates Alberto and Melo in the same entry, I run ::
+
+    jrnl @alberto --tags | grep @melo
+
+And will get something like ``@melo: 9``, meaning there are 9 entries where both ``@alberto`` and ``@melo`` are tagged. How does this work? First, ``jrnl @alberto`` will filter the journal to only entries containing the tag ``@alberto``, and then the ``--tags`` option will print out how often each tag occurred in this `filtered` journal. Finally, we pipe this to ``grep`` which will only display the line containing ``@melo``.
+
+Combining filters
+~~~~~~~~~~~~~~~~~
+
+You can do things like ::
+
+    jrnl @fixed -starred -n 10 -until "jan 2013" --short
+
+To get a short summary of the 10 most recent, favourited entries before January 1, 2013 that are tagged with ``@fixed``.
+
+Statistics
+~~~~~~~~~~
+
+How much did I write last year? ::
+
+    jrnl -from "jan 1 2013" -until "dec 31 2013" | wc -w
+
+Will give you the number of words you wrote in 2013. How long is my average entry? ::
+
+    expr $(jrnl --export text | wc -w) / $(jrnl --short | wc -l)
+
+This will first get the total number of words in the journal and divide it by the number of entries (this works because ``jrnl --short`` will print exactly one line per entry).
+
+Importing older files
+~~~~~~~~~~~~~~~~~~~~~
+
+If you want to import a file as an entry to jrnl, you can just do ``jrnl < entry.ext``. But what if you want the modification date of the file to be the date of the entry in jrnl? Try this ::
+
+    echo `stat -f %Sm -t '%d %b %Y at %H:%M: ' entry.txt` `cat entry.txt` | jrnl
+
+The first part will format the modification date of ``entry.txt``, and then combine it with the contents of the file before piping it to jrnl. If you do that often, consider creating a function in your ``.bashrc`` or ``.bash_profile``
+
+.. code-block:: sh
+
+    jrnlimport () {
+        echo `stat -f %Sm -t '%d %b %Y at %H:%M: ' $1` `cat $1` | jrnl
+    }
+
+
+Using templates
+~~~~~~~~~~~~~~~
+
+Say you always want to use the same template for creating new entries. If you have an :doc:`external editor <advanced>` set up, you can use this ::
+
+    jrnl < my_template.txt
+    $ jrnl -1 --edit
+
+Another nice solution that allows you to define individual prompts comes from `Jacobo de Vera <https://github.com/maebert/jrnl/issues/194#issuecomment-47402869>`_:
+
+.. code-block:: sh
+
+    function log_question()
+    {
+       echo $1
+       read
+       jrnl today: ${1}. $REPLY
+    }
+    log_question 'What did I achieve today?'
+    log_question 'What did I make progress with?'
+
+
+External editors
+----------------
+
+To use external editors for writing and editing journal entries,  set them up in your ``.jrnl_config`` (see :doc:`advanced usage <advanced>` for details). Generally, after writing an entry, you will have to save and close the file to save the changes to jrnl.
+
+Sublime Text
+~~~~~~~~~~~~
+
+To use Sublime Text, install the command line tools for Sublime Text and configure your ``.jrnl_config`` like this:
+
+.. code-block:: javascript
+
+    "editor": "subl -w"
+
+Note the ``-w`` flag to make sure jrnl waits for Sublime Text to close the file before writing into the journal.
+
+
+MacVim
+~~~~~~
+
+Similar to Sublime Text, MacVim must be started with a flag that tells the the process to wait until the file is closed before passing control back to journal. In the case of MacVim, this is ``-f``:
+
+.. code-block:: javascript
+
+    "editor": "mvim -f"
+
+iA Writer
+~~~~~~~~~
+
+On OS X, you can use the fabulous `iA Writer <http://www.iawriter.com/mac>`_ to write entries. Configure your ``.jrnl_config`` like this:
+
+.. code-block:: javascript
+
+    "editor": "open -b jp.informationarchitects.WriterForMacOSX -Wn"
+
+What does this do? ``open -b ...`` opens a file using the application identified by the bundle identifier (a unique string for every app out there). ``-Wn`` tells the application to wait until it's closed before passing back control, and to use a new instance of the application.
+
+
+Notepad++ on Windows
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To set `Notepad++ <http://notepad-plus-plus.org/>`_ as your editor, edit the jrnl config file (``.jrnl_config``) like this:
+
+.. code-block:: javascript
+
+      "editor": "C:\\Program Files (x86)\\Notepad++\\notepad++.exe -multiInst -nosession",
+
+The double backslashes are needed so jrnl can read the file path correctly. The ``-multiInst -nosession`` options will cause jrnl to open its own Notepad++ window.

docs/reference-command-line.md

@@ -1,141 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Command Line Reference
-
-## Synopsis
-```
-usage: jrnl [--debug] [--help] [--version] [--list] [--encrypt] [--decrypt]
-            [--import] [-on DATE] [-today-in-history] [-month DATE]
-            [-day DATE] [-year DATE] [-from DATE] [-to DATE] [-contains TEXT]
-            [-and] [-starred] [-n [NUMBER]] [-not [TAG]] [--edit] [--delete]
-            [--format TYPE] [--tags] [--short]
-            [--config-override CONFIG_KEY CONFIG_VALUE]
-            [--config-file CONFIG_FILE_PATH]
-            [[...]]
-```
-
-## Standalone Commands
-
-These commands will exit after they complete. You may only run one at a time.
-
-### --help
-Show a help message.
-
-### --version
-Print version and license information.
-
-### --list
-List the config file location, all configured journals, and their locations.
-
-### ---encrypt
-Encrypt a journal. See [encryption](encryption.md) for more information.
-
-### --decrypt
-Decrypt a journal. See [encryption](encryption.md) for more information.
-
-
-### --import
-Import entries from another journal. If any entries have the exact same content
-and timestamp, they will be deduplicated.
-
-Optional parameters:
-```sh
---file FILENAME
-```
-Specify a file to import. If not provided, `jrnl` will use STDIN as the data source.
-
-```sh
---format TYPE
-```
-Specify the format of the file that is being imported. Defaults to the same data
-storage method that jrnl uses. See [formats](formats.md) for more information.
-
-## Writing new entries
-See [Basic Usage](usage.md).
-
-## Searching
-
-To find entries from your journal, use any combination of the below filters.
-Only entries that match all the filters will be displayed.
-
-When specifying dates, you can use the same kinds of dates you use for new
-entries, such as `yesterday`, `today`, `Tuesday`, or `2021-08-01`.
-
-| Search Argument | Description |
-| --- | --- |
-| -on DATE | Show entries on this date |
-| -today-in-history | Show entries of today over the years |
-| -month DATE | Show entries on this month of any year |
-| -day DATE | Show entries on this day of any month |
-| -year DATE | Show entries of a specific year |
-| -from DATE | Show entries after, or on, this date |
-| -to DATE | Show entries before, or on, this date (alias: -until) |
-| -contains TEXT | Show entries containing specific text (put quotes around text with spaces) |
-| -and | Show only entries that match all conditions, like saying "x AND y" (default: OR) |
-| -starred | Show only starred entries (marked with *) |
-| -tagged | Show only tagged entries (marked with the [configured tagsymbols](reference-config-file.md#tagsymbols)) |
-| -n [NUMBER] | Show a maximum of NUMBER entries (note: '-n 3' and '-3' have the same effect) |
-| -not [TAG] | Exclude entries with this tag |
-| -not -starred | Exclude entries that are starred |
-| -not -tagged | Exclude entries that are tagged |
-
-## Searching Options
-These help you do various tasks with the selected entries from your search.
-If used on their own (with no search), they will act on your entire journal.
-
-### --edit
-Opens the selected entries in your configured editor. It will fail if the
-`editor` key is not set in your config file.
-
-Once you begin editing, you can add multiple entries and delete entries
-by modifying the text in your editor. When your editor closes, jrnl reads
-the temporary file you were editing and makes the changes to your journal.
-
-### --delete
-Interactively deletes selected entries. You'll be asked to confirm deletion of
-each entry.
-
-### --change-time DATE
-Interactively changes the time of the selected entries to the date specified,
-or to right now if no date is specified. You'll be asked to confirm each entry,
-unless you are using this with `--edit` on a single entry.
-
-### --format TYPE
-Display selected entries in an alternate format. See [formats](formats.md).
-
-#### Optional parameters
-```sh
---file FILENAME
-```
-Write output to file instead of STDOUT. In most shells, the
-same effect can be achieved using `>`.
-
-### --tags
-
-Alias for '--format tags'. Returns a list of all tags and the number of times
-they occur within the searched entries. If there are no tags found, `jrnl` will output a message saying so.
-
-### --short
-Only shows the date and titles of the searched entries.
-
-## Configuration arguments
-
-### --config-override CONFIG_KEY CONFIG_VALUE
-
-Override configured key-value pair with CONFIG_KV_PAIR for this command invocation only. To access config keys that aren't at the top level, separate the keys with a dot, such as `colors.title` to access the `title` key within the `colors` key. Read [advanced usage](./advanced.md) for examples.
-
-### --config-file CONFIG_FILE_PATH
-
-Use the config file at CONFIG_FILE_PATH for this command invocation only.
-Read [advanced usage](./advanced.md) for examples.
-
-## Other Arguments
-
-### --debug
-Prints information useful for troubleshooting while `jrnl` executes.
-
-### --diagnostic
-Prints diagnostic information useful for [reporting issues](https://github.com/jrnl-org/jrnl/issues).

docs/reference-config-file.md

@@ -1,123 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Configuration File Reference
-
-`jrnl` stores its information in a YAML configuration file.
-
-!!! note
-    Backup your journal and config file before editing. Changes to the config file
-    can have destructive effects on your journal!
-
-## Config location
-You can find your configuration file location by running:
-`jrnl --list`
-
-By default, the configuration file is `~/.config/jrnl/jrnl.yaml`.
-If you have the `XDG_CONFIG_HOME` variable set, the configuration
-file will be saved as `$XDG_CONFIG_HOME/jrnl/jrnl.yaml`.
-
-!!! note
-    On Windows, the configuration file is typically found at
-    `%USERPROFILE%\.config\jrnl\jrnl.yaml`.
-
-
-## Config format
-The configuration file is a [YAML](https://yaml.org/) file and can be edited with
-a text editor.
-
-## Config keys
-
-### journals
-
-Describes each journal used by `jrnl`. Each indented key after this key is
-the name of a journal.
-
-If a journal key has a value, that value will be interpreted as the path
-to the journal. Otherwise, the journal needs the additional indented key
-`journal` to specify its path.
-
-All keys below can be specified for each journal at the same level as the
-`journal` key. If a key conflicts with a top-level key, the journal-specific
-key will be used instead.
-
-### editor
-If set, executes this command to launch an external editor for
-writing and editing your entries. The path to a temporary file
-is passed after it, and `jrnl` processes the file once
-the editor returns control to `jrnl`.
-
-Some editors require special options to work properly, since they must be
-blocking processes to work with `jrnl`. See [External Editors](external-editors.md)
-for details.
-
-### encrypt
-If `true`, encrypts your journal using AES. Do not change this
-value for journals that already have data in them.
-
-### template
-The path to a text file to use as a template for new entries. Only works when you
-have the `editor` field configured. If you use a template, the editor's
-[temporary files](privacy-and-security.md#files-in-transit-from-editor-to-jrnl)
-will have the same extension as the template.
-
-### tagsymbols
-Symbols to be interpreted as tags.
-
-!!! note
-    Although it seems intuitive to use the `#`
-    character for tags, there's a drawback: on most shells, this is
-    interpreted as a meta-character starting a comment. This means that if
-    you type
-
-    > `jrnl Implemented endless scrolling on the #frontend of our website.`
-
-    your bash will chop off everything after the `#` before passing it to
-      `jrnl`. To avoid this, wrap your input into quotation marks like
-      this:
-
-    > `jrnl "Implemented endless scrolling on the #frontend of our website."`
-
-  Or use the built-in prompt or an external editor to compose your
-  entries.
-
-### default_hour and default_minute
-Entries will be created at this time if you supply a date but no specific time (for example, `last thursday`).
-
-### timeformat
-Defines how to format the timestamps as they are stored in your journal.
-See the [python docs](http://docs.python.org/library/time.html#time.strftime) for reference.
-
-Do not change this for an existing journal, since that might lead
-to data loss.
-
-!!! note
-    `jrnl` doesn't support the `%z` or `%Z` time zone identifiers.
-
-### highlight
-If `true`, tags will be highlighted in cyan.
-
-### linewrap
-Controls the width of the output. Set to `false` if you don't want to
-wrap long lines. Set to `auto` to let `jrnl` automatically determine
-the terminal width.
-
-### colors
-A dictionary that controls the colors used to display journal entries.
-It has four subkeys, which are: `body`, `date`, `tags`, and `title`.
-
-Current valid values are: `BLACK`, `RED`, `GREEN`, `YELLOW`, `BLUE`,
-`MAGENTA`, `CYAN`, `WHITE`, and `NONE`.
-
-`colorama.Fore` is used for colorization, and you can find the [docs here](https://github.com/tartley/colorama#colored-output).
-
-To disable colored output, set the value to `NONE`.
-
-### display_format
-Specifies formatter to use by default. See [formats](formats.md).
-
-### version
-`jrnl` automatically updates this field to the version that it is running.
-There is no need to change this field manually.

docs/tips-and-tricks.md

@@ -1,224 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Tips and Tricks
-
-This page contains tips and tricks for using `jrnl`, often in conjunction
-with other tools, including external editors.
-
-## Co-occurrence of tags
-
-If I want to find out how often I mentioned my flatmates Alberto and
-Melo in the same entry, I run
-
-```sh
-jrnl @alberto --tags | grep @melo
-```
-
-And will get something like `@melo: 9`, meaning there are 9 entries
-where both `@alberto` and `@melo` are tagged. How does this work? First,
-`jrnl @alberto` will filter the journal to only entries containing the
-tag `@alberto`, and then the `--tags` option will print out how often
-each tag occurred in this filtered journal. Finally, we pipe this to
-`grep` which will only display the line containing `@melo`.
-
-## Combining filters
-
-You can do things like
-
-```sh
-jrnl @fixed -starred -n 10 -to "jan 2013" --short
-```
-
-To get a short summary of the 10 most recent, favourite entries before
-January 1, 2013 that are tagged with `@fixed`.
-
-## Statistics
-
-How much did I write last year?
-
-```sh
-jrnl -from "jan 1 2013" -to "dec 31 2013" | wc -w
-```
-
-Will give you the number of words you wrote in 2013. How long is my
-average entry?
-
-```sh
-expr $(jrnl --export text | wc -w) / $(jrnl --short | wc -l)
-```
-
-This will first get the total number of words in the journal and divide
-it by the number of entries (this works because `jrnl --short` will
-print exactly one line per entry).
-
-## Importing older files
-
-If you want to import a file as an entry to `jrnl`, you can just do `jrnl < entry.ext`. But what if you want the modification date of the file to
-be the date of the entry in `jrnl`? Try this
-
-```sh
-echo `stat -f %Sm -t '%d %b %Y at %H:%M: ' entry.txt` `cat entry.txt` | jrnl
-```
-
-The first part will format the modification date of `entry.txt`, and
-then combine it with the contents of the file before piping it to jrnl.
-If you do that often, consider creating a function in your `.bashrc` or
-`.bash_profile`
-
-```sh
-jrnlimport () {
-  echo `stat -f %Sm -t '%d %b %Y at %H:%M: ' $1` `cat $1` | jrnl
-}
-```
-
-## Using Templates
-
-!!! note
-    Templates require an [external editor](./advanced.md) be configured.
-
-Templates are text files that are used for creating structured journals.
-There are three ways you can use templates:
-
-### 1. Use the `--template` command line argument and the default $XDG_DATA_HOME/jrnl/templates directory
-
-`$XDG_DATA_HOME/jrnl/templates` is created by default to store your templates! Create a template (like `default.md`) in this directory and pass `--template FILE_IN_DIR`.
-
-```sh
-jrnl --template default.md
-```
-
-### 2. Use the `--template` command line argument with a local / absolute path
-
-You can create a template file with any text. Here is an example:
-
-```sh
-# /tmp/template.txt
-My Personal Journal
-Title:
-
-Body:
-```
-
-Then, pass the absolute or relative path to the template file as an argument, and your external
-editor will open and have your template pre-populated.
-
-```sh
-jrnl --template /tmp/template.md
-```
-
-### 3. Set a default template file in `jrnl.yaml`
-
-If you want a template by default, change the value of `template` in the [config file](./reference-config-file.md)
-from `false` to the template file's path, wrapped in double quotes:
-
-```sh
-...
-template: "/path/to/template.txt"
-...
-```
-
-!!! tip
-    To read your journal entry or to verify the entry saved, you can use this
-    command: `jrnl -n 1` (Check out [Formats](./formats.md) for more options).
-
-```sh
-jrnl -n 1
-```
-
-## Prompts on shell reload
-
-If you'd like to be prompted each time you refresh your shell, you can include
-this in your `.bash_profile`:
-
-```sh
-function log_question()
-{
-   echo $1
-   read
-   jrnl today: ${1}. $REPLY
-}
-log_question 'What did I achieve today?'
-log_question 'What did I make progress with?'
-```
-
-Whenever your shell is reloaded, you will be prompted to answer each of the
-questions in the example above. Each answer will be logged as a separate
-journal entry at the `default_hour` and `default_minute` listed in your
-`jrnl.yaml` [config file](../advanced/#configuration-file).
-
-## Display random entry
-
-You can use this to select one title at random and then display the whole
-entry. The invocation of `cut` needs to match the format of the timestamp.
-For timestamps that have a space between data and time components, select
-fields 1 and 2 as shown. For timestamps that have no whitespace, select
-only field 1.
-
-```sh
-jrnl -on "$(jrnl --short | shuf -n 1 | cut -d' ' -f1,2)"
-```
-
-
-## Launch a terminal for rapid logging
-You can use this to launch a terminal that is the `jrnl` stdin prompt so you can start typing away immediately.
-
-```bash
-jrnl --config-override editor ""
-```
-
-Bind this to a keyboard shortcut.
-
-Map `Super+Alt+J` to launch the terminal with `jrnl` prompt
-
-- **xbindkeys**
-In your `.xbindkeysrc`
-
-```ini
-Mod4+Mod1+j
- alacritty -t floating-jrnl -e jrnl --config-override editor "",
-```
-
-- **I3 WM** Launch a floating terminal with the `jrnl` prompt
-
-```ini
-bindsym Mod4+Mod1+j exec --no-startup-id alacritty -t floating-jrnl -e jrnl --config-override editor ""
-for_window[title="floating *"] floating enable
-```
-## Visualize Formatted Markdown in the CLI
-
-Out of the box, `jrnl` can output journal entries in Markdown. To visualize it, you can pipe to [mdless](https://github.com/ttscoff/mdless), which is a [less](https://en.wikipedia.org/wiki/Less_(Unix))-like tool that allows you to visualize your Markdown text with formatting and syntax highlighting from the CLI. You can use this in any shell that supports piping.
-
-The simplest way to visualize your Markdown output with `mdless` is as follows:
-```sh
-jrnl --export md | mdless
-```
-
-This will render your Markdown output in the whole screen.
-
-Fortunately, `mdless` has an option that allows you to adjust the screen width by using the `-w` option as follows:
-
-```sh
-jrnl --export md | mdless -w 70
-```
-
-If you want Markdown to be your default display format, you can define this in your config file as follows:
-
-```yaml
-display_format: md
-# or
-display_format: markdown
-```
-
-For more information on how `jrnl` outputs your entries in Markdown, please visit the [Formats](./formats.md) section.
-
-
-## Jump to end of buffer (with vi)
-
-To cause vi to jump to the end of the last line of the entry you edit, in your config file set:
-
-```yaml
-editor: vi + -c "call cursor('.',strwidth(getline('.')))"
-```

docs/usage.md

@@ -1,256 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-# Basic Usage #
-
-`jrnl` has two modes: **composing** and **viewing**. Whenever you don't enter
-any arguments that start with a dash (`-`) or double-dash (`--`), you're in
-composing mode, meaning that you can write your entry on the command line.
-
-We intentionally break a convention on command line arguments: all arguments
-starting with a _single dash_ (`-`) will _filter_ your journal before viewing
-it. Filter arguments can be combined arbitrarily. Arguments with a _double dash_
-(`--`) will _control_ how your journal is displayed or exported. Control
-arguments are mutually exclusive (i.e., you can only specify one way to display
-or export your journal at a time).
-
-For a list of commands, enter `jrnl --help`.
-
-## Composing Entries ##
-
-Composing mode is entered by either starting `jrnl` without any arguments --
-which will launch an external editor -- or by just writing an entry on the
-command line:
-
-```text
-jrnl today at 3am: I just met Steve Buscemi in a bar! What a nice guy.
-```
-
-!!! note
-    Most shells contain a certain number of reserved characters, such as `#` and
-    `*`. These characters, as well as unbalanced single or double quotation
-    marks, parentheses, and others, likely will cause problems. Although
-    reserved characters can be escaped using `\`, this is not ideal for
-    long-form writing. The solution: first enter `jrnl` and hit `return`. You
-    can then enter the text of your journal entry. Alternatively, you can [use
-    an external editor](./advanced.md).
-
-You can also import an entry directly from a file:
-
-```sh
-jrnl < my_entry.txt
-```
-
-### Specifying Date and Time ###
-
-If you don't specify a date and time (e.g., `jrnl finished writing letter to brother`), `jrnl` will create an entry using the current date and time. For retrospective entries, you can use a timestamp to tell `jrnl` where to put the entry. Timestamps can be entered using a variety of formats. Here are some that work:
-
-- at 6am
-- yesterday
-- last monday
-- sunday at noon
-- 2 march 2012
-- 7 apr
-- 5/20/1998 at 23:42
-- 2020-05-22T15:55-04:00
-
-If you don't use a timestamp, `jrnl` will create an entry using the current
-time. If you use a date only (no time), `jrnl` will use the default time
-specified in your [configuration file](./reference-config-file.md#default_hour-and-default_minute).
-Behind the scenes, `jrnl` reorganizes entries in chronological order.
-
-### Using Tags ###
-
-`jrnl` supports tags. The default tag symbol is `@` (largely because `#` is a
-reserved character). You can specify your own tag symbol in the
-[configuration file](./reference-config-file.md#tagsymbols). To use tags, preface the
-desired tag with the symbol:
-
-```sh
-jrnl Had a wonderful day at the @beach with @Tom and @Anna.
-```
-
-Although you can use capitals while tagging an entry, searches by tag are
-case-insensitive.
-
-There is no limit to how many tags you can use in an entry.
-
-### Starring Entries ###
-
-To mark an entry as a favorite, simply "star" it using an asterisk (`*`):
-
-```sh
-jrnl last sunday *: Best day of my life.
-```
-
-If you don't want to add a date (i.e., you want the date to be entered as
-_now_), the following options are equivalent:
-
-- `jrnl *: Best day of my life.`
-- `jrnl *Best day of my life.`
-- `jrnl Best day of my life.*`
-
-!!! note
-    Make sure that the asterisk (`*`) is **not** surrounded by whitespaces.
-    `jrnl Best day of my life! *` will not work because the `*` character has a
-    special meaning in most shells.
-
-## Viewing and Searching Entries ##
-
-`jrnl` can display entries in a variety of ways.
-
-To view all entries, enter:
-```sh
-jrnl -to today
-```
-
-`jrnl` provides several filtering commands, prefaced by a single dash (`-`), that
-allow you to find a more specific range of entries. For example,
-
-```sh
-jrnl -n 10
-```
-
-lists the ten most recent entries. `jrnl -10` is even more concise and works the
-same way. If you want to see all of the entries you wrote from the beginning of
-last year until the end of this past March, you would enter
-
-```sh
-jrnl -from "last year" -to march
-```
-
-Filter criteria that use more than one word require surrounding quotes (`""`).
-
-To see entries on a particular date, use `-on`:
-```sh
-jrnl -on yesterday
-```
-
-### Text Search ###
-
-The `-contains` command displays all entries containing the text you enter after it.
-This may be helpful when you're searching for entries and you can't remember if you
-tagged any words when you wrote them.
-
-You may realize that you use a word a lot and want to turn it into a tag in all
-of your previous entries.
-
-```sh
-jrnl -contains "dogs" --edit
-```
-
-opens your external editor so that you can add a tag symbol (`@` by default) to
-all instances of the word "dogs."
-
-### Filtering by Tag ###
-
-You can filter your journal entries by tag. For example,
-
-```sh
-jrnl @pinkie @WorldDomination
-```
-
-displays all entries in which either `@pinkie` or `@WorldDomination`
-occurred. Tag filters can be combined with other filters:
-
-```sh
-jrnl -n 5 @pinkie -and @WorldDomination
-```
-
-displays the last five entries containing _both_ `@pinkie` _and_
-`@worldDomination`. You can change which symbols you'd like to use for tagging
-in the [configuration file](./reference-config-file.md#tagsymbols).
-
-!!! note
-    Entering `jrnl @pinkie @WorldDomination` will display entries in which both
-    tags are present because, although no command line arguments are given, all
-    of the input strings look like tags. `jrnl` will assume you want to filter
-    by tag, rather than create a new entry that consists only of tags.
-
-To view a list of all tags in the journal, enter:
-
-```sh
-jrnl --tags
-```
-
-### Viewing Starred Entries ###
-
-To display only your favorite (starred) entries, enter
-
-```sh
-jrnl -starred
-```
-
-## Editing Entries ##
-
-You can edit entries after writing them. This is particularly useful when your
-journal file is encrypted. To use this feature, you need to have an external
-editor configured in your [configuration file](./reference-config-file.md#editor). You
-can also edit only the entries that match specific search criteria. For example,
-
-```sh
-jrnl -to 1950 @texas -and @history --edit
-```
-
-opens your external editor displaying all entries tagged with `@texas` and
-`@history` that were written before 1950. After making changes, save and close
-the file, and only those entries will be modified (and encrypted, if
-applicable).
-
-If you are using multiple journals, it's easy to edit specific entries from
-specific journals. Simply prefix the filter string with the name of the journal.
-For example,
-
-```sh
-jrnl work -n 1 --edit
-```
-
-opens the most recent entry in the 'work' journal in your external editor.
-
-## Deleting Entries ##
-
-The `--delete` command opens an interactive interface for deleting entries. The
-date and title of each entry in the journal are presented one at a time, and you
-can choose whether to keep or delete each entry.
-
-If no filters are specified, `jrnl` will ask you to keep or delete each entry in
-the entire journal, one by one. If there are a lot of entries in the journal, it
-may be more efficient to filter entries before passing the `--delete` command.
-
-Here's an example. Say you have a journal into which you've imported the last 12
-years of blog posts. You use the `@book` tag a lot, and for some reason you want
-to delete some, but not all, of the entries in which you used that tag, but only
-the ones you wrote at some point in 2004 or earlier. You're not sure which
-entries you want to keep, and you want to look through them before deciding.
-This is what you might enter:
-
-```sh
-jrnl -to 2004 @book --delete
-```
-
-`jrnl` will show you only the relevant entries, and you can choose the ones you
-want to delete.
-
-You may want to delete _all_ of the entries containing `@book` that you wrote in
-2004 or earlier. If there are dozens or hundreds, the easiest way would be to
-use an external editor. Open an editor with the entries you want to delete...
-
-```sh
-jrnl -to 2004 @book --edit
-```
-
-...select everything, delete it, save and close, and all of those entries are
-removed from the journal.
-
-## Listing Journals ##
-
-To list all of your journals:
-
-```sh
-jrnl --list
-```
-
-The journals displayed correspond to those specified in the `jrnl`
-[configuration file](./reference-config-file.md#journals).

docs/usage.rst

@@ -0,0 +1,134 @@
+.. _usage:
+
+Basic Usage
+===========
+
+*jrnl* has two modes: **composing** and **viewing**. Basically, whenever you `don't` supply any arguments that start with a dash or double-dash, you're in composing mode, meaning you can write your entry on the command line or an editor of your choice.
+
+We intentionally break a convention on command line arguments: all arguments starting with a `single dash` will `filter` your journal before viewing it, and can be combined arbitrarily. Arguments with a `double dash` will control how your journal is displayed or exported and are mutually exclusive (ie. you can only specify one way to display or export your journal at a time).
+
+Listing Journals
+----------------
+
+You can list the journals accessible by jrnl::
+
+    jrnl -ls
+
+The journals displayed correspond to those specified in the jrnl configuration file.
+
+Composing Entries
+-----------------
+
+Composing mode is entered by either starting ``jrnl`` without any arguments -- which will prompt you to write an entry or launch your editor -- or by just writing an entry on the prompt, such as::
+
+    jrnl today at 3am: I just met Steve Buscemi in a bar! He looked funny.
+
+
+.. note::
+
+    Most shell contains a certain number of reserved characters, such as ``#`` and ``*``. Unbalanced quotes, parenthesis, and so on will also get into the way of your editing. For writing longer entries, just enter ``jrnl`` and hit ``return``. Only then enter the text of your journal entry. Alternatively, :doc:`use an external editor <advanced>`).
+
+You can also import an entry directly from a file::
+
+    jrnl < my_entry.txt
+
+Smart timestamps
+~~~~~~~~~~~~~~~~
+
+Timestamps that work:
+
+* at 6am
+* yesterday
+* last monday
+* sunday at noon
+* 2 march 2012
+* 7 apr
+* 5/20/1998 at 23:42
+
+Starring entries
+~~~~~~~~~~~~~~~~
+
+To mark an entry as a favourite, simply "star" it::
+
+    jrnl last sunday *: Best day of my life.
+
+If you don't want to add a date (ie. your entry will be dated as now), The following options are equivalent:
+
+* ``jrnl *: Best day of my life.``
+* ``jrnl *Best day of my life.``
+* ``jrnl Best day of my life.*``
+
+.. note::
+
+  Just make sure that the asterisk sign is **not** surrounded by whitespaces, e.g. ``jrnl Best day of my life! *`` will **not** work (the reason being that the ``*`` sign has a special meaning on most shells).
+
+Viewing
+-------
+
+::
+
+    jrnl -n 10
+
+will list you the ten latest entries (if you're lazy, ``jrnl -10`` will do the same), ::
+
+    jrnl -from "last year" -until march
+
+everything that happened from the start of last year to the start of last march. To only see your favourite entries, use ::
+
+    jrnl -starred
+
+Using Tags
+----------
+
+Keep track of people, projects or locations, by tagging them with an ``@`` in your entries ::
+
+    jrnl Had a wonderful day on the @beach with @Tom and @Anna.
+
+You can filter your journal entries just like this: ::
+
+    jrnl @pinkie @WorldDomination
+
+Will print all entries in which either ``@pinkie`` or ``@WorldDomination`` occurred. ::
+
+    jrnl -n 5 -and @pineapple @lubricant
+
+the last five entries containing both ``@pineapple`` **and** ``@lubricant``. You can change which symbols you'd like to use for tagging in the configuration.
+
+.. note::
+
+  ``jrnl @pinkie @WorldDomination`` will switch to viewing mode because although **no** command line arguments are given, all the input strings look like tags - *jrnl* will assume you want to filter by tag.
+
+Editing older entries
+---------------------
+
+You can edit selected entries after you wrote them. This is particularly useful when your journal file is encrypted or if you're using a DayOne journal. To use this feature, you need to have an editor configured in your journal configuration file (see :doc:`advanced usage <advanced>`)::
+
+    jrnl -until 1950 @texas -and @history --edit
+
+Will open your editor with all entries tagged with ``@texas`` and ``@history`` before 1950. You can make any changes to them you want; after you save the file and close the editor, your journal will be updated.
+
+Of course, if you are using multiple journals, you can also edit e.g. the latest entry of your work journal with ``jrnl work -n 1 --edit``. In any case, this will bring up your editor and save (and, if applicable, encrypt) your edited journal after you save and exit the editor.
+
+You can also use this feature for deleting entries from your journal::
+
+    jrnl @girlfriend -until 'june 2012' --edit
+
+Just select all text, press delete, and everything is gone...
+
+Editing DayOne Journals
+~~~~~~~~~~~~~~~~~~~~~~~
+
+DayOne journals can be edited exactly the same way, however the output looks a little bit different because of the way DayOne stores its entries:
+
+.. code-block:: output
+
+    # af8dbd0d43fb55458f11aad586ea2abf
+    2013-05-02 15:30 I told everyone I built my @robot wife for sex.
+    But late at night when we're alone we mostly play Battleship.
+
+    # 2391048fe24111e1983ed49a20be6f9e
+    2013-08-10 03:22 I had all kinds of plans in case of a @zombie attack.
+    I just figured I'd be on the other side.
+
+The long strings starting with hash symbol are the so-called UUIDs, unique identifiers for each entry. Don't touch them. If you do, then the old entry would get deleted and a new one written, which means that you could lose DayOne data that jrnl can't handle (such as as the entry's geolocation).
+

docs_theme/assets/colors.css

@@ -1,34 +0,0 @@
-/*
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
-*/
-
-:root {
-  /* For dark bg */
-  --white: #fcfcfc;
-  --off-white: #f4f0ff;
-  --purple: #7e57c2;
-  --light-purple: #cf93e6;
-  --blue: #61aeee;
-  --green: #a6e22e;
-  --orange: #fd971f;
-  --red: #eb5567;
-  --pink: #d57699;
-  --yellow: #e2b93d;
-
-  /* For light bg */
-  --black: #404040;
-  --teal: #2a8068;
-  --dark-blue: #356eb7;
-  --mid-purple: #846392;
-  --bright-purple: #af27ad;
-  --dark-purple: #604385;
-  --darkest-purple: #251A32;
-  --grey: #3b3b4a;
-
-  --black-shadow: #0000001A;
-  --blacker-shadow: #00000059;
-
-  /* Special cases */
-  --terminal: #1b1c2e;
-}

docs_theme/assets/highlight.css

@@ -1,147 +0,0 @@
-/*
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
-
-Atom One Dark With support for ReasonML by Gidi Morris, based off work by
-Daniel Gamage
-
-Original One Dark Syntax theme from https://github.com/atom/one-dark-syntax
-*/
-
-.hljs {
-  display: block;
-  overflow-x: auto;
-  padding: 0.5em;
-  line-height: 1.3em;
-  color: var(--off-white);
-  background: #383e49;
-  border-radius: 5px;
-  font-size: 0.9rem;
-  line-height: 1.3rem;
-}
-.hljs-keyword,
-.hljs-operator {
-  color: var(--pink);
-}
-.hljs-pattern-match {
-  color: var(--pink);
-}
-.hljs-pattern-match .hljs-constructor {
-  color: var(--blue);
-}
-.hljs-function {
-  color: var(--blue);
-}
-.hljs-function .hljs-params {
-  color: var(--green);
-}
-.hljs-function .hljs-params .hljs-typing {
-  color: var(--orange);
-}
-.hljs-module-access .hljs-module {
-  color: var(--purple);
-}
-.hljs-constructor {
-  color: var(--yellow);
-}
-.hljs-constructor .hljs-string {
-  color: var(--green);
-}
-.hljs-comment,
-.hljs-quote {
-  color: var(--light-purple);
-  font-style: italic;
-}
-.hljs-doctag,
-.hljs-formula {
-  color: var(--purple);
-}
-.hljs-section,
-.hljs-name,
-.hljs-selector-tag,
-.hljs-deletion,
-.hljs-subst {
-  color: var(--yellow);
-}
-.hljs-literal {
-  color: var(--blue);
-}
-.hljs-string,
-.hljs-regexp,
-.hljs-addition,
-.hljs-attribute,
-.hljs-meta-string {
-  color: var(--green);
-}
-.hljs-built_in,
-.hljs-class .hljs-title {
-  color: var(--orange);
-}
-.hljs-attr,
-.hljs-variable,
-.hljs-template-variable,
-.hljs-type,
-.hljs-selector-class,
-.hljs-selector-attr,
-.hljs-selector-pseudo,
-.hljs-number {
-  color: var(--orange);
-}
-
-.rst-content a tt,
-.rst-content a tt,
-.rst-content a code {
-  color: var(--blue);
-}
-
-.hljs-number,
-.hljs-literal,
-.hljs-variable,
-.hljs-template-variable,
-.hljs-tag .hljs-attr {
-  color: var(--blue);
-}
-
-.hljs-tag {
-  color: var(--pink)
-}
-
-.hljs-symbol,
-.hljs-bullet,
-.hljs-link,
-.hljs-meta,
-.hljs-selector-id,
-.hljs-title {
-  color: var(--blue);
-}
-.hljs-emphasis {
-  font-style: italic;
-}
-.hljs-strong {
-  font-weight: bold;
-}
-.hljs-link {
-  text-decoration: underline;
-}
-
-.rst-content .note .admonition-title {
-  background: var(--dark-blue);
-}
-
-.rst-content .note.admonition {
-  background: var(--light-blue);
-}
-
-.rst-content .tip .admonition-title {
-  background: var(--teal);
-}
-
-.rst-content .tip .admonition {
-  background: var(--light-blue);
-}
-
-/* hack to bypass a11y issue with conflicting highlight.css files */
-code.language-xml span.hljs-meta span.hljs-string {
-  color: var(--green) !important;
-}
-

docs_theme/assets/index.css

@@ -1,325 +0,0 @@
-/*
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
-*/
-
-/* reset */article,aside,details,figcaption,figure,footer,header,hgroup,main,nav,section,summary{display:block}audio,canvas,video{display:inline-block}audio:not([controls]){display:none;height:0}[hidden]{display:none}html{font-family:sans-serif;-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%}body{margin:0}a:focus{outline:thin dotted}a:active,a:hover{outline:0}h1{font-size:2em;margin:.67em 0}abbr[title]{border-bottom:1px dotted}b,strong{font-weight:bold}dfn{font-style:italic}hr{-moz-box-sizing:content-box;box-sizing:content-box;height:0}mark{background:#ff0;color:#000}code,kbd,pre,samp{font-family:monospace,serif;font-size:1em}pre{white-space:pre-wrap}q{quotes:"\201C" "\201D" "\2018" "\2019"}small{font-size:80%}sub,sup{font-size:75%;line-height:0;position:relative;vertical-align:baseline}sup{top:-0.5em}sub{bottom:-0.25em}img{border:0}svg:not(:root){overflow:hidden}figure{margin:0}fieldset{border:1px solid silver;margin:0 2px;padding:.35em .625em .75em}legend{border:0;padding:0}button,input,select,textarea{font-family:inherit;font-size:100%;margin:0}button,input{line-height:normal}button,select{text-transform:none}button,html input[type="button"],input[type="reset"],input[type="submit"]{-webkit-appearance:button;cursor:pointer}button[disabled],html input[disabled]{cursor:default}input[type="checkbox"],input[type="radio"]{box-sizing:border-box;padding:0}input[type="search"]{-webkit-appearance:textfield;-moz-box-sizing:content-box;-webkit-box-sizing:content-box;box-sizing:content-box}input[type="search"]::-webkit-search-cancel-button,input[type="search"]::-webkit-search-decoration{-webkit-appearance:none}button::-moz-focus-inner,input::-moz-focus-inner{border:0;padding:0}textarea{overflow:auto;vertical-align:top}table{border-collapse:collapse;border-spacing:0}
-
-body {
-  background-color: var(--white);
-  font-family: "Open Sans", "Helvetica Neue", sans-serif;
-  font-weight: 300;
-}
-
-.icon {
-  background-image: url("../img/sprites.svg");
-  width: 32px;
-  height: 32px;
-  display: inline-block;
-  font-size: 40px;
-  background-size: 200px 80px;
-}
-
-h3 {
-  font-weight: 400;
-}
-
-.icon.secure {
-  background-position: 0em 0em;
-}
-
-.icon.future {
-  background-position: -1em 0em;
-}
-
-.icon.search {
-  background-position: -2em 0em;
-}
-
-.icon.nli {
-  background-position: -3em 0em;
-}
-
-.icon.share {
-  background-position: 0em -1em;
-}
-
-.icon.sync {
-  background-position: 0 -1em;
-}
-
-.icon.dayone {
-  background-position: -1em -1em;
-}
-
-.icon.github {
-  background-position: -2em -1em;
-}
-
-.icon.search {
-  background-position: -2em 0;
-}
-
-.icon.folders {
-  background-position: -3em -1em;
-}
-
-.icon.twitter {
-  background-position: -4em -1em;
-}
-
-header {
-  background-color: var(--mid-purple);
-  background-image: linear-gradient(211deg, var(--mid-purple) 0%, var(--dark-purple) 100%);
-  color: var(--white);
-  border: 0px solid transparent;
-  display: relative;
-  padding-top: 150px;
-  overflow: visible;
-}
-
-#terminal {
-  background: var(--terminal);
-  max-width: 520px;
-  box-shadow: 0 -2px 16px 0 var(--black-shadow);
-  border-radius: 6px;
-  min-height: 120px;
-  margin: 0px auto;
-  position: relative;
-  transform: translateY(75px);
-  color: var(--off-white);
-  font-family: "Monaco", "Courier New";
-  font-size: 18px;
-  padding: 45px 20px 0px 20px;
-  line-height: 165%;
-}
-
-#terminal b {
-  font-weight: normal;
-  color: var(--off-white);
-}
-
-#terminal i {
-  font-style: normal;
-  color: var(--light-purple);
-}
-
-#terminal:before {
-  content: "";
-  position: absolute;
-  top: 15px;
-  left: 15px;
-  display: inline-block;
-  width: 15px;
-  height: 15px;
-  border-radius: 50%;
-  background: var(--grey);
-  box-shadow: 25px 0 0 var(--grey), 50px 0 0 var(--grey);
-}
-
-#typed:before {
-  content: "$ ";
-  color: var(--mid-purple);
-}
-
-#twitter {
-  display: block;
-  position: absolute;
-  text-decoration: none;
-  top: 20px;
-  right: 20px;
-  border: 1px solid var(--white);
-  padding: 5px 10px;
-  color: var(--white);
-  border-radius: 3px;
-}
-
-#twitter .icon {
-  transform: scale(0.5);
-  vertical-align: -18%;
-  margin: 0;
-  padding: 0;
-}
-
-#twitter:hover,
-#twitter:active {
-  text-decoration: none;
-  box-shadow: 0 2px 25px 0 var(--blacker-shadow);
-  transition: all .5s ease;
-}
-
-#title {
-  max-width: 630px;
-  margin: 0 auto;
-  padding: 0px 20px;
-}
-
-#prompt {
-  max-width: 700px;
-  margin: 25px auto 100px auto;
-  padding: 0px 20px;
-}
-
-header img {
-  float: left;
-  margin-right: 30px;
-}
-
-h1 {
-  color: var(--white);
-  font-weight: 300;
-}
-
-a,
-a:visited {
-  color: var(--dark-purple);
-}
-
-a:hover {
-  color: var(--bright-purple);
-}
-
-nav {
-  text-align: center;
-}
-
-nav a#twitter-nav {
-  display: none;
-}
-
-nav a, nav a:visited {
-  color: var(--dark-purple);
-  font-size: 20px;
-  line-height: 2.5em;
-  margin: 0 40px;
-  font-weight: 400;
-  text-decoration: none;
-}
-
-nav a:hover,
-nav a:visited:hover {
-  color: var(--bright-purple);
-  text-decoration: underline;
-}
-
-
-nav a.cta {
-  display: inline-block;
-  color: var(--white);
-  background-color: var(--mid-purple);
-  background-image: linear-gradient(259deg, var(--mid-purple) 0%, var(--dark-purple) 100%);
-  box-shadow: 0 2px 8px 0 var(--blacker-shadow);
-  border-radius: 50px;
-  padding: 0 2em;
-  white-space: nowrap;
-  transition: all 0.1s ease;
-  text-decoration: none;
-}
-
-nav a.cta:hover {
-  text-decoration: none;
-  background-color: var(--mid-purple);
-  background-image: linear-gradient(259deg, var(--bright-purple) 0%, var(--dark-purple) 100%);
-  box-shadow: 0 4px 16px 0 var(--black-shadow);
-  color: var(--off-white);
-}
-
-main {
-  padding: 60px 0 0 0;
-}
-
-.flex {
-  display: flex;
-  margin: 0 auto;
-  max-width: 920px;
-  flex-wrap: wrap;
-  padding: 20px 20px;
-  padding-top: 30px;
-  justify-content: space-between;
-}
-
-.flex section {
-  /*margin: 20px;*/
-  margin-top: 40px;
-  width: 32%;
-}
-
-.flex section:first-child {
-  margin-left: 0px;
-}
-.flex section:last-child {
-  margin-right: 0px;
-}
-
-.flex section i {
-  float: left;
-  left: 0;
-  display: block;
-  margin: 0px auto 10px auto;
-}
-
-.flex section h3 {
-  margin-top: 0;
-  font-size: 18px;
-  color: var(--dark-purple);
-  margin-bottom: 0.5em;
-  font-weight: 300;
-  margin-left: 40px;
-}
-
-.flex section p {
-  padding-left: 40px;
-  color: var(--grey);
-  font-size: 16px;
-  margin: 0;
-}
-
-footer {
-  color: var(--grey);
-  max-width: 700px;
-  margin: 70px auto 20px;
-  padding: 0 20px 20px 20px;
-  font-size: 16px;
-  text-align: center;
-}
-
-@media screen and (max-width: 680px) {
-  .flex {
-    display: block;
-    padding: 0;
-  }
-  .flex section {
-    width: 100%;
-  }
-
-  main {
-    padding: 20px;
-    margin: 0;
-    width: calc(100% - 40px);
-  }
-
-  nav a,
-  nav a#twitter-nav {
-    display: inline-block;
-    margin: 0px 10px;
-  }
-
-  nav a.cta {
-    display: block;
-    margin: 20px;
-  }
-
-  header #twitter {
-    display: none;
-  }
-
-  header #logo {
-    display: block;
-    float: none;
-    margin: 0px auto;
-  }
-
-  header #title br {
-    display: none;
-  }
-}

docs_theme/assets/theme.css

@@ -1,378 +0,0 @@
-/*
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
-*/
-
-/* ------------------------------------------------------------ */
-/* Overrides for jrnl theme                                     */
-/* ------------------------------------------------------------ */
-
-body.wy-body-for-nav,
-section.wy-nav-content-wrap {
-  background-color: var(--white);
-  color: var(--black);
-}
-
-.rst-content pre {
-  background-color: transparent;
-  border: none;
-  margin: 1em -1em;
-}
-
-.rst-content code {
-  color: var(--darkest-purple);
-  background-color: var(--off-white);
-  font-size: 15px;
-}
-
-.rst-content pre code {
-  color: var(--off-white);
-  background: var(--darkest-purple);
-  padding: 1em 1.5em;
-  border-radius: 15px;
-  border: none;
-  font-size: 16px;
-  line-height: 1.5em;
-  font-weight: 200 !important;
-}
-
-h1,
-h2,
-h3,
-h4,
-h5,
-h6 {
-  font-family: "Open Sans", "Helvetica Neue", Helvetica, sans-serif;
-  font-weight: 600;
-  margin-top: 2rem;
-  margin-bottom: 0.2rem;
-}
-
-h2 {
-  font-size: 1.2em;
-  margin-top: 40px;
-}
-
-h3 {
-  font-size:  1.1em;
-}
-
-h4 {
-  font-size:  1em;
-}
-
-p,
-td,
-tr,
-div,
-li {
-  font-family: "Open Sans", "Helvetica Neue", Helvetica, sans-serif;
-  font-weight: 00;
-  font-size: 18px;
-  line-height: 1.5em;
-}
-
-p {
-  margin: 1em 0em;
-}
-
-/* No-one likes lines that are 400 characters long. */
-div.rst-content {
-  max-width: 54em;
-}
-
-
-.wy-side-nav-search,
-.wy-menu-vertical li.current,
-.wy-menu-vertical li.toctree-l1.current > a,
-.wy-menu-vertical li.toctree-l2.current > a,
-.wy-menu-vertical li.toctree-l3.current > a {
-  background-color: transparent;
-  border: none;
-}
-
-.wy-menu-vertical li.toctree-l2.current li.toctree-l3,
-.wy-menu-vertical li.toctree-l2.current li.toctree-l3 > a {
-  background: transparent;
-}
-
-.wy-menu-vertical li.toctree-l4,
-.wy-menu-vertical li.toctree-l5,
-.wy-menu-vertical li.toctree-l6,
-.wy-menu-vertical li.toctree-l7 {
-  display: none;
-}
-
-.wy-nav-top {
-  background-color: var(--mid-purple);
-  background-image: linear-gradient(-211deg, var(--mid-purple) 0%, var(--dark-purple) 100%);
-}
-
-.wy-nav-top .fa-bars {
-  line-height: 50px;
-}
-
-.wy-side-nav-search a.icon-home {
-  width: 100%;
-  max-width: 250px;
-  background-size: 100%;
-}
-
-.wy-side-nav-search a.icon-home:before {
-  display: block;
-  width: 84px;
-  height: 70px;
-  content: "";
-  background: url(../img/logo_white.svg) center center no-repeat;
-  margin: 10px auto;
-}
-
-.wy-menu-vertical a,
-.wy-menu-vertical li ul li a {
-  font-size: 16px;
-  color: var(--white);
-  line-height: 2em;
-}
-
-.wy-menu-vertical a:hover,
-.wy-menu-vertical li.toctree-l2.current li.toctree-l3 > a:hover,
-.wy-menu-vertical li.current a:hover {
-  background-color: var(--black-shadow);
-  color: var(--white);
-}
-
-.wy-menu-vertical li.on a {
-  transition: all .25s ease;
-  background: var(--dark-purple);
-  color: var(--white);
-  position: relative;
-}
-
-.wy-menu-vertical li.toctree-l1.current > a {
-  background: var(--darkest-purple);
-  border: none !important;
-  pointer-events: none;
-}
-
-.wy-menu-vertical li.on a,
-.wy-menu-vertical li.current a {
-  border-right: none;
-}
-
-.wy-menu-vertical li.on a,
-.wy-menu-vertical li > a.current:after {
-  position: absolute;
-  right: 0em;
-  z-index: 999;
-  content: "";
-  width: 0;
-  height: 0;
-  border-top: 1em solid transparent;
-  border-bottom: 1em solid transparent;
-  border-right: 1em solid var(--white);
-}
-
-.toctree-expand:before {
-  display: none !important;
-}
-
-.rst-versions,
-.rst-versions .rst-current-version {
-  display: none;
-}
-
-.wy-menu-vertical p.caption {
-  margin-top: 2em;
-}
-
-.wy-menu-vertical span {
-  color: var(--white);
-  font-size: 1.2em;
-  font-weight: 600;
-}
-
-.wy-menu-vertical li a {
-  color: var(--white) !important;
-  font-weight: 300;
-}
-
-
-.wy-nav-side {
-  background-color: var(--mid-purple);
-  font-weight: 300;
-  height: 100%;
-}
-
-
-footer {
-  display: none;
-}
-
-.wy-side-nav-search input[type=text],
-.mkdocs-search input[type=text],
-form .search-query {
-  background-color: var(--off-white);
-  border: none;
-  margin-bottom: 1em;
-  color: var(--black);
-  font-weight: 500;
-  box-shadow: none;
-}
-
-.wy-side-nav-search input[type=text]::placeholder,
-.mkdocs-search input[type=text]::placeholder,
-form .search-query::placeholder {
-  color: var(--dark-purple);
-}
-
-.wy-side-nav-search > a:hover {
-  background: transparent;
-}
-
-.wy-menu-vertical li.current ul {
-  background-color: var(--mid-purple);
-}
-
-
-/* ------------------------------------------------------------ */
-/* Logo: ;                                                      */
-/* ------------------------------------------------------------ */
-
-.logo {
-  width: 128px;
-  height: 128px;
-  vertical-align: middle;
-  margin-right: 1em;
-}
-
-/* ------------------------------------------------------------ */
-/* Code blocks in callouts                                      */
-/* ------------------------------------------------------------ */
-
-div.admonition {
-  border-radius: 5px;
-  margin: 1em -1em;
-}
-
-div.admonition p.admonition-title {
-  border-top-left-radius: 5px;
-  border-top-right-radius: 5px;
-}
-
-div.admonition>p {
-  padding: 0em .5em;
-}
-
-
-div.admonition div.highlight {
-  background: none !important;
-}
-
-/* ------------------------------------------------------------ */
-/* Fancy ordered lists.                                         */
-/* ------------------------------------------------------------ */
-
-ol {
-  counter-reset: li;
-  margin-left: 0px;
-  padding: 0;
-}
-
-ol li {
-  list-style: none !important;
-  margin-bottom: 1.5em;
-  margin-left: 3em !important;
-}
-
-ol>li:before {
-  content: counter(li);
-  counter-increment: li;
-  background-color: var(--sidebar);
-  border-radius: 50%;
-  display: block;
-  float: left;
-  margin-left: -3em;
-  margin-top: -.3em;
-  width: 2em;
-  height: 2em;
-  color: var(--dark-purple);
-  text-align: center;
-  line-height: 2em;
-  font-weight: 600;
-}
-
-
-/* ------------------------------------------------------------ */
-/* Accessibility-related changes                                */
-/* ------------------------------------------------------------ */
-.rst-content div[role="main"] a,
-.rst-content div[role="main"] a:visited {
-  color: var(--mid-purple);
-  text-decoration: underline;
-}
-
-.rst-content div[role="main"]  a:hover {
-  color: var(--bright-purple);
-}
-
-.rst-content div[role="navigation"] a,
-.rst-content div[role="navigation"] a:visited {
-  color: var(--mid-purple);
-}
-
-.mkdocs-search {
-  display: flex;
-  margin-top: 20px;
-}
-
-.wy-side-nav-search input[type="text"],
-.mkdocs-search input[type=text] {
-  border-radius: 50px 0 0 50px;
-  height: 32px;
-  border-right: none;
-  margin: 0;
-}
-
-.mkdocs-search button {
-  background-color: var(--off-white);
-  border: none;
-  box-shadow: none;
-  color: var(--mid-purple);
-  border-radius: 0 50px 50px 0;
-  height: 32px;
-  width: 2.5em;
-  overflow: hidden;
-}
-
-.mkdocs-search {
-  border-radius: 50px;
-}
-
-.mkdocs-search:focus-within {
-  box-shadow: 0 2px 25px 0 var(--blacker-shadow);
-  transition: all .5s ease;
-}
-
-.rst-content div[role="main"] .mkdocs-search input[type="text"] {
-  border-right: none;
-  font-size: 100%;
-  height: 48px;
-  margin: 0;
-}
-
-.rst-content div[role="main"] .mkdocs-search button {
-  border-left: none;
-  font-size: 100%;
-  height: 48px;
-}
-
-.rst-content div[role="main"] .mkdocs-search button:before {
-  font-size: 140%;
-  position: relative;
-  left: -7px;
-  top: -1px;
-}
-
-.search-results {
-  margin-top: 0;
-}

docs_theme/breadcrumbs.html

@@ -1,49 +0,0 @@
-<!--
-Copied from https://github.com/mkdocs/mkdocs/blob/master/mkdocs/themes/readthedocs/breadcrumbs.html
-Then lightly modified for accessibility
--->
-
-<div role="navigation" aria-label="breadcrumbs navigation">
-  <ul class="wy-breadcrumbs">
-    <li><a href="{{ nav.homepage.url|url }}" class="icon icon-home" aria-label="{% trans %}Docs{% endtrans %}"></a> &raquo;</li>
-    {%- if page %}
-      {%- for doc in page.ancestors[::-1] %}
-        {%- if doc.link %}
-          <li><a href="{{ doc.link|e }}">{{ doc.title }}</a> &raquo;</li>
-        {%- else %}
-          <li>{{ doc.title }} &raquo;</li>
-        {%- endif %}
-      {%- endfor %}
-      <li>{{ page.title }}</li>
-    {%- endif %}
-    <li class="wy-breadcrumbs-aside">
-      {%- block repo %}
-      {%- if page and page.edit_url %}
-        {%- if config.repo_name|lower == 'github' %}
-          <a href="{{ page.edit_url }}" class="icon icon-github"> {% trans repo_name=config.repo_name %}Edit on {{ repo_name }}{% endtrans %}</a>
-        {%- elif config.repo_name|lower == 'bitbucket' %}
-          <a href="{{ page.edit_url }}" class="icon icon-bitbucket"> {% trans repo_name=config.repo_name %}Edit on {{ repo_name }}{% endtrans %}</a>
-        {%- elif config.repo_name|lower == 'gitlab' %}
-          <a href="{{ page.edit_url }}" class="icon icon-gitlab"> {% trans repo_name=config.repo_name %}Edit on {{ repo_name }}{% endtrans %}</a>
-        {%- elif config.repo_name %}
-          <a href="{{ page.edit_url }}">{% trans repo_name=config.repo_name %}Edit on {{ repo_name }}{% endtrans %}</a>
-        {%- else %}
-          <a href="{{ page.edit_url }}">{% trans %}Edit{% endtrans %}</a>
-        {%- endif %}
-      {%- endif %}
-      {%- endblock %}
-    </li>
-  </ul>
-  {%- if config.theme.prev_next_buttons_location|lower in ['top', 'both']
-        and page and (page.next_page or page.previous_page) %}
-    <div class="rst-breadcrumbs-buttons" role="navigation" aria-label="{% trans %}Breadcrumb Navigation{% endtrans %}">
-      {%- if page.previous_page %}
-        <a href="{{ page.previous_page.url|url }}" class="btn btn-neutral float-left" title="{{ page.previous_page.title }}"><span class="icon icon-circle-arrow-left" aria-hidden="true"></span> {% trans %}Previous{% endtrans %}</a>
-      {%- endif %}
-      {%- if page.next_page %}
-        <a href="{{ page.next_page.url|url }}" class="btn btn-neutral float-right" title="{{ page.next_page.title }}">{% trans %}Next{% endtrans %} <span class="icon icon-circle-arrow-right" aria-hidden="true"></span></a>
-      {%- endif %}
-    </div>
-  {%- endif %}
-  <hr/>
-</div>

docs_theme/img/favicon.svg

@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="64px" height="64px" viewBox="0 0 64 64" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 55 (78076) - https://sketchapp.com -->
-    <title>favicon</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="linearGradient-1">
-            <stop stop-color="#986B9D" offset="0%"></stop>
-            <stop stop-color="#664C8B" offset="100%"></stop>
-        </linearGradient>
-    </defs>
-    <g id="favicon" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <path d="M47,9.75231557 L47,37 L42,32 L37,37 L37,7 L25,7 C17.8202983,7 12,12.8202983 12,20 L12,44 C12,51.1797017 17.8202983,57 25,57 L32,57 L32,7 L34,7 L34,57 L39,57 C46.1797017,57 52,51.1797017 52,44 L52,20 C52,15.8373552 50.0435392,12.1316662 47,9.75231557 Z M47.097641,7.37132944 C51.2495133,10.039075 54,14.6983322 54,20 L54,44 C54,49.3016678 51.2495133,53.960925 47.097641,56.6286706 C52.7817736,55.2392133 57,50.1122164 57,44 L57,20 C57,13.8877836 52.7817736,8.76078667 47.097641,7.37132944 Z M16.902359,56.6286706 C12.7504867,53.960925 10,49.3016678 10,44 L10,20 C10,14.6983322 12.7504867,10.039075 16.902359,7.37132944 C11.2182264,8.76078667 7,13.8877836 7,20 L7,44 C7,50.1122164 11.2182264,55.2392133 16.902359,56.6286706 Z M52.097641,7.37132944 C56.2495133,10.039075 59,14.6983322 59,20 L59,44 C59,49.3016678 56.2495133,53.960925 52.097641,56.6286706 C57.7817736,55.2392133 62,50.1122164 62,44 L62,20 C62,13.8877836 57.7817736,8.76078667 52.097641,7.37132944 Z M11.902359,56.6286706 C7.7504867,53.960925 5,49.3016678 5,44 L5,20 C5,14.6983322 7.7504867,10.039075 11.902359,7.37132944 C6.21822638,8.76078667 2,13.8877836 2,20 L2,44 C2,50.1122164 6.21822638,55.2392133 11.902359,56.6286706 Z M15,5 L49,5 C57.2842712,5 64,11.7157288 64,20 L64,44 C64,52.2842712 57.2842712,59 49,59 L15,59 C6.71572875,59 0,52.2842712 0,44 L0,20 C2.0539126e-15,11.7157288 6.71572875,5 15,5 Z" id="Combined-Shape" fill="url(#linearGradient-1)" fill-rule="nonzero"></path>
-    </g>
-</svg>

docs_theme/img/jrnl_white.svg

@@ -1,10 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="90px" height="98px" viewBox="0 0 90 98" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 55 (78076) - https://sketchapp.com -->
-    <title>jrnl_white</title>
-    <desc>Created with Sketch.</desc>
-    <g id="jrnl_white" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <path d="M63,5.34786368 L63,43 L58,38 L53,43 L53,5 L30,5 C22.8202983,5 17,10.8202983 17,18 L17,58 C17,65.1797017 22.8202983,71 30,71 L45,71 L45,5 L47,5 L47,71 L60,71 C67.1797017,71 73,65.1797017 73,58 L73,18 C73,11.8528367 68.7334,6.70219128 63,5.34786368 Z M67.6693542,5.10618565 C72.0593056,7.72299627 75,12.5180801 75,18 L75,58 C75,63.4819199 72.0593056,68.2770037 67.6693542,70.8938143 C74.060623,70.0745197 79,64.6140865 79,58 L79,18 C79,11.3859135 74.060623,5.92548026 67.6693542,5.10618565 Z M22.3306458,70.8938143 C17.9406944,68.2770037 15,63.4819199 15,58 L15,18 C15,12.5180801 17.9406944,7.72299627 22.3306458,5.10618565 C15.939377,5.92548026 11,11.3859135 11,18 L11,58 C11,64.6140865 15.939377,70.0745197 22.3306458,70.8938143 Z M73.6693542,5.10618565 C78.0593056,7.72299627 81,12.5180801 81,18 L81,58 C81,63.4819199 78.0593056,68.2770037 73.6693542,70.8938143 C80.060623,70.0745197 85,64.6140865 85,58 L85,18 C85,11.3859135 80.060623,5.92548026 73.6693542,5.10618565 Z M16.3306458,70.8938143 C11.9406944,68.2770037 9,63.4819199 9,58 L9,18 C9,12.5180801 11.9406944,7.72299627 16.3306458,5.10618565 C9.93937703,5.92548026 5,11.3859135 5,18 L5,58 C5,64.6140865 9.93937703,70.0745197 16.3306458,70.8938143 Z M18,3 L72,3 C80.2842712,3 87,9.71572875 87,18 L87,58 C87,66.2842712 80.2842712,73 72,73 L18,73 C9.71572875,73 3,66.2842712 3,58 L3,18 C3,9.71572875 9.71572875,3 18,3 Z" id="Combined-Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-        <path d="M24.22,95.092 C24.0293324,95.092 23.7616684,95.0736668 23.417,95.037 C23.0723316,95.0003332 22.7680013,94.9306672 22.504,94.828 L22.856,92.65 C23.1786683,92.7526672 23.5673311,92.804 24.022,92.804 C24.6380031,92.804 25.0706654,92.6243351 25.32,92.265 C25.5693346,91.9056649 25.694,91.3666703 25.694,90.648 L25.694,82.642 L28.356,82.285 L28.356,90.692 C28.356,92.1880075 28.0003369,93.2953297 27.289,94.014 C26.5776631,94.7326703 25.5546733,95.092 24.22,95.092 Z M41.4,84.892 C41.1799989,84.8186663 40.8756686,84.7416671 40.487,84.661 C40.0983314,84.5803329 39.6473359,84.54 39.134,84.54 C38.8406652,84.54 38.5290017,84.569333 38.199,84.628 C37.8689984,84.686667 37.6380007,84.7379998 37.506,84.782 L37.506,94 L34.844,94 L34.844,83.044 C35.3573359,82.8533324 35.9989962,82.6736675 36.769,82.505 C37.5390039,82.3363325 38.3933286,82.252 39.332,82.252 C39.5080009,82.252 39.7133322,82.2629999 39.948,82.285 C40.1826678,82.3070001 40.4173322,82.3363332 40.652,82.373 C40.8866678,82.4096669 41.1139989,82.4536664 41.334,82.505 C41.5540011,82.5563336 41.7299993,82.6039998 41.862,82.648 L41.4,84.892 Z M46.81,82.868 C47.3233359,82.7213326 47.9906626,82.5820007 48.812,82.45 C49.6333374,82.3179993 50.5426617,82.252 51.54,82.252 C52.4786714,82.252 53.2633302,82.3803321 53.894,82.637 C54.5246698,82.893668 55.0269981,83.2529977 55.401,83.715 C55.7750019,84.1770023 56.0389992,84.7343301 56.193,85.387 C56.3470008,86.0396699 56.424,86.7546628 56.424,87.532 L56.424,94 L53.762,94 L53.762,87.95 C53.762,87.3339969 53.7216671,86.8096688 53.641,86.377 C53.5603329,85.9443312 53.4283342,85.5923347 53.245,85.321 C53.0616658,85.0496653 52.8123349,84.8516673 52.497,84.727 C52.1816651,84.6023327 51.7966689,84.54 51.342,84.54 C51.004665,84.54 50.6526685,84.5619998 50.286,84.606 C49.9193315,84.6500002 49.6480009,84.6866665 49.472,84.716 L49.472,94 L46.81,94 L46.81,82.868 Z M66.784,94.22 C65.991996,94.2053333 65.3356693,94.1173341 64.815,93.956 C64.2943307,93.7946659 63.8800015,93.5636682 63.572,93.263 C63.2639985,92.9623318 63.0476673,92.5883356 62.923,92.141 C62.7983327,91.6936644 62.736,91.1840029 62.736,90.612 L62.736,82.692 L65.398,82.252 L65.398,90.106 C65.398,90.4286683 65.4236664,90.6999989 65.475,90.92 C65.5263336,91.1400011 65.6179993,91.3269992 65.75,91.481 C65.8820007,91.6350008 66.0616655,91.7523329 66.289,91.833 C66.5163345,91.9136671 66.8059982,91.9759998 67.158,92.02 L66.784,94.22 Z" id="jrnl" fill="#FFFFFF" fill-rule="nonzero"></path>
-    </g>
-</svg>

docs_theme/img/logo.svg

@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="90px" height="98px" viewBox="0 0 90 98" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 55 (78076) - https://sketchapp.com -->
-    <title>logo</title>
-    <desc>Created with Sketch.</desc>
-    <defs>
-        <linearGradient x1="50%" y1="0%" x2="50%" y2="100%" id="linearGradient-1">
-            <stop stop-color="#986B9D" offset="0%"></stop>
-            <stop stop-color="#664C8B" offset="100%"></stop>
-        </linearGradient>
-    </defs>
-    <g id="logo" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <path d="M63,5.34786368 L63,43 L58,38 L53,43 L53,5 L30,5 C22.8202983,5 17,10.8202983 17,18 L17,58 C17,65.1797017 22.8202983,71 30,71 L45,71 L45,5 L47,5 L47,71 L60,71 C67.1797017,71 73,65.1797017 73,58 L73,18 C73,11.8528367 68.7334,6.70219128 63,5.34786368 Z M67.6693542,5.10618565 C72.0593056,7.72299627 75,12.5180801 75,18 L75,58 C75,63.4819199 72.0593056,68.2770037 67.6693542,70.8938143 C74.060623,70.0745197 79,64.6140865 79,58 L79,18 C79,11.3859135 74.060623,5.92548026 67.6693542,5.10618565 Z M22.3306458,70.8938143 C17.9406944,68.2770037 15,63.4819199 15,58 L15,18 C15,12.5180801 17.9406944,7.72299627 22.3306458,5.10618565 C15.939377,5.92548026 11,11.3859135 11,18 L11,58 C11,64.6140865 15.939377,70.0745197 22.3306458,70.8938143 Z M73.6693542,5.10618565 C78.0593056,7.72299627 81,12.5180801 81,18 L81,58 C81,63.4819199 78.0593056,68.2770037 73.6693542,70.8938143 C80.060623,70.0745197 85,64.6140865 85,58 L85,18 C85,11.3859135 80.060623,5.92548026 73.6693542,5.10618565 Z M16.3306458,70.8938143 C11.9406944,68.2770037 9,63.4819199 9,58 L9,18 C9,12.5180801 11.9406944,7.72299627 16.3306458,5.10618565 C9.93937703,5.92548026 5,11.3859135 5,18 L5,58 C5,64.6140865 9.93937703,70.0745197 16.3306458,70.8938143 Z M18,3 L72,3 C80.2842712,3 87,9.71572875 87,18 L87,58 C87,66.2842712 80.2842712,73 72,73 L18,73 C9.71572875,73 3,66.2842712 3,58 L3,18 C3,9.71572875 9.71572875,3 18,3 Z" id="Combined-Shape" fill="url(#linearGradient-1)" fill-rule="nonzero"></path>
-        <path d="M24.22,95.092 C24.0293324,95.092 23.7616684,95.0736668 23.417,95.037 C23.0723316,95.0003332 22.7680013,94.9306672 22.504,94.828 L22.856,92.65 C23.1786683,92.7526672 23.5673311,92.804 24.022,92.804 C24.6380031,92.804 25.0706654,92.6243351 25.32,92.265 C25.5693346,91.9056649 25.694,91.3666703 25.694,90.648 L25.694,82.642 L28.356,82.285 L28.356,90.692 C28.356,92.1880075 28.0003369,93.2953297 27.289,94.014 C26.5776631,94.7326703 25.5546733,95.092 24.22,95.092 Z M41.4,84.892 C41.1799989,84.8186663 40.8756686,84.7416671 40.487,84.661 C40.0983314,84.5803329 39.6473359,84.54 39.134,84.54 C38.8406652,84.54 38.5290017,84.569333 38.199,84.628 C37.8689984,84.686667 37.6380007,84.7379998 37.506,84.782 L37.506,94 L34.844,94 L34.844,83.044 C35.3573359,82.8533324 35.9989962,82.6736675 36.769,82.505 C37.5390039,82.3363325 38.3933286,82.252 39.332,82.252 C39.5080009,82.252 39.7133322,82.2629999 39.948,82.285 C40.1826678,82.3070001 40.4173322,82.3363332 40.652,82.373 C40.8866678,82.4096669 41.1139989,82.4536664 41.334,82.505 C41.5540011,82.5563336 41.7299993,82.6039998 41.862,82.648 L41.4,84.892 Z M46.81,82.868 C47.3233359,82.7213326 47.9906626,82.5820007 48.812,82.45 C49.6333374,82.3179993 50.5426617,82.252 51.54,82.252 C52.4786714,82.252 53.2633302,82.3803321 53.894,82.637 C54.5246698,82.893668 55.0269981,83.2529977 55.401,83.715 C55.7750019,84.1770023 56.0389992,84.7343301 56.193,85.387 C56.3470008,86.0396699 56.424,86.7546628 56.424,87.532 L56.424,94 L53.762,94 L53.762,87.95 C53.762,87.3339969 53.7216671,86.8096688 53.641,86.377 C53.5603329,85.9443312 53.4283342,85.5923347 53.245,85.321 C53.0616658,85.0496653 52.8123349,84.8516673 52.497,84.727 C52.1816651,84.6023327 51.7966689,84.54 51.342,84.54 C51.004665,84.54 50.6526685,84.5619998 50.286,84.606 C49.9193315,84.6500002 49.6480009,84.6866665 49.472,84.716 L49.472,94 L46.81,94 L46.81,82.868 Z M66.784,94.22 C65.991996,94.2053333 65.3356693,94.1173341 64.815,93.956 C64.2943307,93.7946659 63.8800015,93.5636682 63.572,93.263 C63.2639985,92.9623318 63.0476673,92.5883356 62.923,92.141 C62.7983327,91.6936644 62.736,91.1840029 62.736,90.612 L62.736,82.692 L65.398,82.252 L65.398,90.106 C65.398,90.4286683 65.4236664,90.6999989 65.475,90.92 C65.5263336,91.1400011 65.6179993,91.3269992 65.75,91.481 C65.8820007,91.6350008 66.0616655,91.7523329 66.289,91.833 C66.5163345,91.9136671 66.8059982,91.9759998 67.158,92.02 L66.784,94.22 Z" id="jrnl" fill="#674C8B" fill-rule="nonzero"></path>
-    </g>
-</svg>

docs_theme/img/logo_white.svg

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<svg width="84px" height="70px" viewBox="0 0 84 70" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-    <!-- Generator: Sketch 55 (78076) - https://sketchapp.com -->
-    <title>logo_white</title>
-    <desc>Created with Sketch.</desc>
-    <g id="logo_white" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd">
-        <path d="M60,2.34786368 L60,40 L55,35 L50,40 L50,2 L27,2 C19.8202983,2 14,7.82029825 14,15 L14,55 C14,62.1797017 19.8202983,68 27,68 L42,68 L42,2 L44,2 L44,68 L57,68 C64.1797017,68 70,62.1797017 70,55 L70,15 C70,8.85283673 65.7334,3.70219128 60,2.34786368 Z M64.6693542,2.10618565 C69.0593056,4.72299627 72,9.51808015 72,15 L72,55 C72,60.4819199 69.0593056,65.2770037 64.6693542,67.8938143 C71.060623,67.0745197 76,61.6140865 76,55 L76,15 C76,8.38591347 71.060623,2.92548026 64.6693542,2.10618565 Z M19.3306458,67.8938143 C14.9406944,65.2770037 12,60.4819199 12,55 L12,15 C12,9.51808015 14.9406944,4.72299627 19.3306458,2.10618565 C12.939377,2.92548026 8,8.38591347 8,15 L8,55 C8,61.6140865 12.939377,67.0745197 19.3306458,67.8938143 Z M70.6693542,2.10618565 C75.0593056,4.72299627 78,9.51808015 78,15 L78,55 C78,60.4819199 75.0593056,65.2770037 70.6693542,67.8938143 C77.060623,67.0745197 82,61.6140865 82,55 L82,15 C82,8.38591347 77.060623,2.92548026 70.6693542,2.10618565 Z M13.3306458,67.8938143 C8.94069436,65.2770037 6,60.4819199 6,55 L6,15 C6,9.51808015 8.94069436,4.72299627 13.3306458,2.10618565 C6.93937703,2.92548026 2,8.38591347 2,15 L2,55 C2,61.6140865 6.93937703,67.0745197 13.3306458,67.8938143 Z M15,0 L69,0 C77.2842712,-1.33226763e-15 84,6.71572875 84,15 L84,55 C84,63.2842712 77.2842712,70 69,70 L15,70 C6.71572875,70 2.66453526e-15,63.2842712 0,55 L0,15 C-8.8817842e-16,6.71572875 6.71572875,1.33226763e-15 15,0 Z" id="Combined-Shape" fill="#FFFFFF" fill-rule="nonzero"></path>
-    </g>
-</svg>

docs_theme/img/sprites.svg

@@ -1,14 +0,0 @@
-<svg width="400" height="160" viewBox="0 0 400 160" fill="none" xmlns="http://www.w3.org/2000/svg">
-<g id="sprites">
-<path id="path10" fill-rule="evenodd" clip-rule="evenodd" d="M176.001 24.001C176.001 10.7458 186.746 0 200.002 0C213.257 0 224.003 10.7471 224 24.001C224 37.2562 213.254 48.002 199.999 48.002C195.938 48.002 192.117 46.9846 188.765 45.2019L172.083 61.8826L172.087 61.8866C170.806 63.192 169.028 64.004 167.058 64.004C163.16 64.004 160 60.8452 160 56.9464C160 54.973 160.812 53.1969 162.117 51.9142L162.103 51.9022L178.791 35.2175C177.014 31.8667 176.001 28.0532 176.001 24.001ZM167.058 60.4732C168.054 60.4732 168.946 60.0545 169.59 59.3865L185.718 43.2605C183.82 41.8457 182.14 40.1657 180.73 38.2643L164.598 54.3969L164.615 54.4129C163.948 55.0596 163.528 55.949 163.528 56.945C163.528 58.8958 165.108 60.4732 167.058 60.4732ZM200.002 44.0045C188.957 44.0045 180.001 35.0455 180.001 24.0037C180.001 12.9592 188.957 4.00283 200.002 4.00283C211.043 4.00283 220.003 12.9592 220.003 24.0037C220.003 35.0468 211.045 44.0045 200.002 44.0045ZM201.002 11.0018C201.002 10.4498 200.551 10.0017 200.002 10.0017C192.268 10.0017 186.001 16.2687 186.001 24.0023C186.001 24.5544 186.449 25.0024 187.001 25.0024C187.553 25.0024 188.001 24.5544 188.001 24.0023C188.001 17.3754 193.373 12.0018 200.002 12.0018C200.551 12.0018 201.002 11.5525 201.002 11.0018Z" fill="#684688"/>
-<path id="path12" fill-rule="evenodd" clip-rule="evenodd" d="M42 26V18C42 8.05733 33.9427 0 24 0C14.0573 0 6 8.05733 6 18V26C2.68533 26 0 28.6853 0 32V38V40V44V46C0 55.9427 8.05733 64 18 64H30C39.9427 64 48 55.9427 48 46V44V40V38V32C48 28.684 45.312 26 42 26ZM10 18C10 10.268 16.268 4 24 4C31.732 4 38 10.268 38 18V26H34V18.004C34 12.48 29.524 8.004 24 8.004C18.476 8.004 14 12.48 14 18.004V26H10V18ZM32 18.0067V18C32 13.5827 28.4173 10 24 10C19.5813 10 16 13.5813 16 18V18.004V26H32V18.0067ZM44 38V40V44V46C44 53.7173 37.7173 60 30 60H18C10.2827 60 4 53.7173 4 46V44V40V38V32C4 30.896 4.896 30 6 30H10H38H42C43.1027 30 44 30.896 44 32V38ZM28 42C28 39.7907 26.208 38 24 38C21.792 38 20 39.7907 20 42C20 43.2133 20.6667 45.52 21.3333 47.344C21.8787 48.828 22.5627 49.996 24 49.996C25.564 49.996 26.1213 48.84 26.668 47.364C27.344 45.536 28 43.2173 28 42Z" fill="#684688"/>
-<path id="path6" fill-rule="evenodd" clip-rule="evenodd" d="M37.4495 102.225L56 110.175V88.9754L49.2056 93.8301C44.3508 88.4239 37.3366 85 29.5 85C17.0237 85 6.58791 93.6333 3.7737 105.244L8.72074 107.291C10.6738 97.6002 19.2306 90.2993 29.5 90.2993C35.5547 90.2993 41.001 92.8572 44.8646 96.9285L37.4495 102.225ZM29.5 132.701C23.4453 132.701 17.9966 130.143 14.1354 126.073L21.5505 120.773L3 112.824V134.025L9.79444 129.17C14.6467 134.576 21.6634 138 29.5 138C41.9945 138 52.4412 129.342 55.2397 117.709L50.2975 115.594C48.3894 125.344 39.8083 132.701 29.5 132.701Z" fill="#684688"/>
-<path id="Combined Shape" fill-rule="evenodd" clip-rule="evenodd" d="M124 84H130.667C138.03 84 144 89.9695 144 97.3333V126.667C144 134.03 138.03 140 130.667 140H124H100H93.3333C85.9695 140 80 134.03 80 126.667V97.3333C80 89.9695 85.9695 84 93.3333 84H100H124ZM110.667 88H100C94.8453 88 90.6667 92.1787 90.6667 97.3333V126.667C90.6667 131.821 94.8453 136 100 136H110.667V88ZM114.667 88V136H124C129.155 136 133.333 131.821 133.333 126.667V97.3333C133.333 94.1617 131.751 91.3595 129.333 89.6729V109.333L124 105.333L118.667 109.333V88H114.667ZM134.13 135.336C136.127 133.005 137.333 129.977 137.333 126.667V97.3333C137.333 94.0233 136.127 90.9949 134.13 88.6638C137.57 90.0393 140 93.4025 140 97.3333V126.667C140 130.597 137.57 133.961 134.13 135.336ZM89.8697 135.336C87.8729 133.005 86.6667 129.977 86.6667 126.667V97.3333C86.6667 94.0233 87.8728 90.9949 89.8697 88.6638C86.43 90.0393 84 93.4025 84 97.3333V126.667C84 130.597 86.43 133.961 89.8697 135.336Z" fill="#684688"/>
-<path id="path8" fill-rule="evenodd" clip-rule="evenodd" d="M363.625 13.625V2L384 16.5417L363.625 31.0833V22.375C335.716 22.375 332.168 42.2843 331.708 47.375C332.463 13.711 363.625 13.625 363.625 13.625ZM320 16.5417C320 12.1097 323.568 8.54167 328 8.54167H353.333L344 12.5417H328C325.784 12.5417 324 14.3257 324 16.5417V52.5417C324 54.7577 325.784 56.5417 328 56.5417H369.333C371.549 56.5417 373.333 54.7577 373.333 52.5417V32.5417L377.333 29.875V52.5417C377.333 56.9737 373.765 60.5417 369.333 60.5417H328C323.568 60.5417 320 56.9737 320 52.5417V16.5417Z" fill="#684688"/>
-<path id="path16" fill-rule="evenodd" clip-rule="evenodd" d="M272 3C254.327 3 240 13.7453 240 27C240 35.2547 245.557 42.532 254.016 46.852C254.016 46.878 254.012 46.8999 254.008 46.9224C254.004 46.9459 254 46.97 254 47C254 50.1096 251.986 53.4268 250.683 55.5737L250.683 55.5739C250.483 55.9023 250.3 56.2033 250.144 56.472H250.148C250.053 56.692 250 56.9333 250 57.188C250 58.188 250.809 59 251.812 59C251.902 59 252.025 58.9887 252.127 58.9792C252.239 58.9689 252.326 58.9609 252.321 58.972C258.572 57.948 264.46 52.2053 265.828 50.5427C267.827 50.836 269.887 51 272 51C289.671 51 304 40.2547 304 27C304 13.7453 289.672 3 272 3ZM272 13C272.552 13 273 13.448 273 14C273 14.552 272.549 15 272 15C261.345 15 252 20.608 252 27C252 27.552 251.552 28 251 28C250.448 28 250 27.552 250 27C250 19.412 260.075 13 272 13ZM266.408 46.5867C268.284 46.86 270.165 47 272 47C287.439 47 300 38.028 300 27C300 15.972 287.436 7 272 7C256.56 7 244 15.972 244 27C244 33.4147 248.424 39.504 255.836 43.2893C257.175 43.972 258.016 45.3467 258.016 46.8507C258.016 46.96 258.011 47.0907 257.999 47.2187C257.956 49.2867 257.347 51.292 256.567 53.0827C259.444 51.372 261.88 49.0467 262.736 48.004C263.503 47.072 264.64 46.544 265.828 46.544C266.02 46.544 266.213 46.5547 266.408 46.5867Z" fill="#684688"/>
-<path id="path22" fill-rule="evenodd" clip-rule="evenodd" d="M160 112C160 94.3267 174.327 80 192 80C209.673 80 224 94.3267 224 112C224 129.673 209.673 144 192 144C174.327 144 160 129.673 160 112ZM220 112C220 96.536 207.464 84 192 84C176.536 84 164 96.536 164 112C164 124.684 172.434 135.391 184 138.833V137.75V135.125V132.875C184 130.334 184.875 128.5 186.583 127.333C185.501 127.229 184.489 127.062 183.583 126.875C182.838 126.721 182.282 126.524 181.545 126.261C181.387 126.205 181.22 126.146 181.042 126.083C180.031 125.73 179.135 125.282 178.333 124.792C177.532 124.301 176.74 123.656 176 122.875C175.26 122.094 174.625 121.239 174.125 120.25C173.625 119.261 173.25 118.052 172.958 116.667C172.666 115.281 172.5 113.75 172.5 112.083C172.5 108.854 173.563 106.104 175.667 103.833C174.708 101.355 174.833 98.667 176 95.7083C176.012 95.7042 176.025 95.6992 176.039 95.6938C176.097 95.6718 176.175 95.6422 176.292 95.625C176.437 95.6037 176.781 95.6253 177.292 95.6667C177.802 95.708 178.365 95.8227 178.958 96C179.552 96.1773 180.344 96.5107 181.333 97C182.323 97.4907 183.354 98.0827 184.458 98.8333C186.896 98.1467 189.437 97.8333 192.125 97.8333C194.792 97.8333 197.396 98.1453 199.875 98.8333C201.626 97.6453 203.178 96.813 204.583 96.2917C205.989 95.7703 206.959 95.5207 207.5 95.5833L208.292 95.6667C209.458 98.604 209.584 101.333 208.625 103.833C210.729 106.105 211.75 108.854 211.75 112.083C211.75 113.75 211.625 115.281 211.333 116.667C211.041 118.052 210.625 119.261 210.125 120.25C209.625 121.239 209.03 122.094 208.292 122.875C207.553 123.656 206.761 124.302 205.958 124.792C205.156 125.281 204.261 125.73 203.25 126.083C202.239 126.437 201.28 126.688 200.375 126.875C199.47 127.062 198.459 127.188 197.375 127.292C199.104 128.48 200 130.354 200 132.875V135.375V137.667V138.833C211.566 135.391 220 124.684 220 112Z" fill="#684688"/>
-<path id="path3858" fill-rule="evenodd" clip-rule="evenodd" d="M100 0C99.0049 0 98.0752 0.350804 97.3333 0.958333C96.5914 1.56586 96 2.50111 96 3.625V5.33333H94.6667V6.66667H87.3333C87.264 6.66305 87.1944 6.66305 87.125 6.66667C86.1491 6.76895 85.3281 7.68544 85.3333 8.66667V9.33333H83.3333C82.2862 9.33344 81.3334 10.2862 81.3333 11.3333V12.125C80.563 12.3974 80.0044 13.1829 80 14V18C80.0001 19.0472 80.9528 19.9999 82 20H85.3333V53.3333L83.6667 54.9167C83.0569 55.2687 82.6604 55.9626 82.6667 56.6667V60.6667C82.6668 61.7138 83.6195 62.6666 84.6667 62.6667H95.2083H104.667H104.875H115.333C116.381 62.6666 117.333 61.7138 117.333 60.6667V56.6667C117.34 55.9626 116.943 55.2687 116.333 54.9167L114.667 53.3333V20H118C119.047 19.9999 120 19.0472 120 18V14C119.996 13.1829 119.437 12.3974 118.667 12.125V11.3333C118.667 10.2862 117.714 9.33344 116.667 9.33333H114.667V8.66667C114.667 7.6195 113.714 6.66677 112.667 6.66667H105.333V5.33333H104V3.625C104 2.50111 103.409 1.56586 102.667 0.958333C101.925 0.350804 100.995 0 100 0ZM100 2.66667C100.274 2.66667 100.684 2.81724 100.958 3.04167C101.232 3.26609 101.333 3.47936 101.333 3.625V5.33333H98.6667V3.625C98.6667 3.47936 98.7676 3.26609 99.0417 3.04167C99.3157 2.81724 99.7255 2.66667 100 2.66667ZM112 12V10.6667H88V12H85.3333C85.2542 12.8356 85.0919 13.6063 84 13.5417V17.3333H89.3333H110.667H116V13.4167C114.82 13.6844 114.596 12.9828 114.667 12H112ZM110.667 20V56L113.333 57.8333V58.6667H86.6667V57.8333L89.3333 56V20H110.667ZM92 28V22.6667H94.6667V28H92ZM96 22.6667V28H98.6667V22.6667H96ZM101.333 28V22.6667H104V28H101.333ZM105.333 22.6667V28H108V22.6667H105.333ZM92 34.6667V29.3333H94.6667V34.6667H92ZM96 29.3333V34.6667H98.6667V29.3333H96ZM101.333 34.6667V29.3333H104V34.6667H101.333ZM105.333 29.3333V34.6667H108V29.3333H105.333ZM101.333 42.6667C101.333 41.6527 102.153 40.8333 103.167 40.8333C104.181 40.8333 105 41.6527 105 42.6667C105 43.6806 104.181 44.5 103.167 44.5C102.153 44.5 101.333 43.6806 101.333 42.6667Z" fill="#684688"/>
-<path id="path20" fill-rule="evenodd" clip-rule="evenodd" d="M247.472 80L243.472 115.792L247.43 116.208L251.013 84H291.93L295.513 116.208L299.472 115.792L295.472 80H247.472ZM255.472 88V92H287.472V88H255.472ZM255.472 100V96H287.472V100H255.472ZM255.472 104V108H287.472V104H255.472ZM255.472 116V112H287.472V116H255.472ZM241.472 120C240.372 120 239.749 120.873 240.097 121.917L246.847 142.083C247.195 143.127 248.372 144 249.472 144H293.472C294.572 144 295.749 143.127 296.097 142.083L302.847 121.917C303.196 120.873 302.572 120 301.472 120H241.472ZM279.472 124H263.472V128H279.472V124Z" fill="#684688"/>
-<path id="Vector" d="M370.378 82H380.145L358.811 107.042L384 141H364.209L348.787 120.416L331.052 141H321.285L344.161 114.253L320 82H340.305L354.313 100.88L370.378 82ZM366.908 134.969H372.305L337.349 87.6378H331.438L366.908 134.969Z" fill="white"/>
-</g>
-</svg>

docs_theme/index.html

@@ -1,127 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-<!DOCTYPE html>
-<html lang="en">
-
-<head>
-    <meta charset="utf-8">
-    <title>jrnl - The Command Line Journal</title>
-    <meta name="description" content="Collect your thoughts and notes without leaving the command line.">
-    <meta name="image" content="https://jrnl.sh/en/stable/img/banner_og.png">
-    <meta itemprop="name" content="jrnl - The Command Line Journal">
-    <meta itemprop="description" content="Collect your thoughts and notes without leaving the command line.">
-    <meta itemprop="image" content="https://jrnl.sh/en/stable/img/banner_og.png">
-    <meta name="twitter:card" content="summary">
-    <meta name="twitter:title" content="jrnl - The Command Line Journal">
-    <meta name="twitter:description" content="Collect your thoughts and notes without leaving the command line.">
-    <meta name="twitter:creator" content="jrnl">
-    <meta name="twitter:image:src" content="https://jrnl.sh/en/stable/img/banner_twitter.png">
-    <meta name="og:title" content="jrnl - The Command Line Journal">
-    <meta name="og:description" content="Collect your thoughts and notes without leaving the command line.">
-    <meta name="og:image" content="https://jrnl.sh/en/stable/img/banner_og.png">
-    <meta name="og:url" content="https://jrnl.sh">
-    <meta name="og:site_name" content="jrnl - The Command Line Journal">
-    <meta name="og:type" content="website">
-    <meta name="viewport" content="width=device-width">
-    <link href='http://fonts.googleapis.com/css?family=Open+Sans:300,400' rel='stylesheet' type='text/css'>
-    <link rel="stylesheet" href="assets/colors.css">
-    <link rel="stylesheet" href="assets/index.css">
-    <link rel="shortcut icon" href="img/favicon.ico">
-    <script type="application/ld+json">
-    {
-        "@context": "https://schema.org",
-        "@type": "SoftwareApplication",
-        "applicationCategory": "https://schema.org/LifestyleApplication",
-        "name": "jrnl",
-        "description": "Collect your thoughts and notes without leaving the command line.",
-        "operatingSystem": ["macOS", "Windows", "Linux"],
-        "thumbnailUrl": "https://jrnl.sh/en/stable/img/banner_og.png",
-        "installUrl": "https://jrnl.sh/en/stable/installation",
-        "softwareVersion": "2.5"
-    }
-    </script>
-</head>
-
-<body>
-    <header>
-        <aside>
-            <a id="twitter" href="https://twitter.com/intent/tweet?text=Collect+your+thoughts+and+notes+without+leaving+the+command+line.+https%3A%2F%2Fjrnl.sh+via+@JrnlSh"><i class="icon twitter"></i>Tell your friends</a>
-        </aside>
-        <div id="title">
-            <img id="logo" src="img/jrnl_white.svg" width="90px" height="98px" title="jrnl" alt="jrnl logo" />
-            <h1>Collect your thoughts and notes <br />without leaving the command line.</h1>
-        </div>
-        <div id="prompt">
-            <div id="terminal">
-                <div id="typed"></div>
-            </div>
-        </div>
-    </header>
-    <main>
-        <nav>
-            <a href="overview">Documentation</a>
-            <a href="installation" class="cta">Get Started</a>
-            <a href="http://github.com/jrnl-org/jrnl" title="View on Github">Fork on GitHub</a>
-            <a id="twitter-nav" href="https://twitter.com/intent/tweet?text=Collect+your+thoughts+and+notes+without+leaving+the+command+line.+https%3A%2F%2Fjrnl.sh+via+@JrnlSh">Tell your friends on X</a>
-        </nav>
-        <div class="flex">
-            <section>
-                <i class="icon nli"></i>
-                <h3>Human friendly.</h3>
-                <p>jrnl has a natural-language interface so you don't have to remember cryptic shortcuts when you're writing down your thoughts.</p>
-            </section>
-            <section>
-                <i class="icon future"></i>
-                <h3>Future-proof.</h3>
-                <p>Your journals are stored in plain-text files that will still be readable in 50 years when your fancy proprietary apps will have gone the way of the dodo.</p>
-            </section>
-            <section>
-                <i class="icon secure"></i>
-                <h3>Secure.</h3>
-                <p>Encrypt your journals with industry-strength AES encryption. Nobody will be able to read your dirty secrets&mdash;not even you, if you lose your password!</p>
-            </section>
-            <section>
-                <i class="icon sync"></i>
-                <h3>Accessible anywhere.</h3>
-                <p>Sync your journal files with other tools like Dropbox to capture your thoughts wherever you are.</p>
-            </section>
-            <section>
-                <i class="icon github"></i>
-                <h3>Free &amp; Open Source.</h3>
-                <p>jrnl is made by a bunch of really friendly and remarkably amazing people. Maybe even <a href="https://www.github.com/jrnl-org/jrnl" title="Fork jrnl on GitHub">you</a>?</p>
-            </section>
-            <section>
-                <i class="icon folders"></i>
-                <h3>For work and play.</h3>
-                <p>Effortlessly access several journals for all parts of your life.</p>
-            </section>
-        </div>
-    </main>
-    <footer>
-        jrnl is made with love by <a href="https://github.com/jrnl-org/jrnl/graphs/contributors" title="Contributors">many fabulous people</a>. If you need help, <a href="https://github.com/jrnl-org/jrnl/issues/new/choose" title="Open a new issue on Github">submit an issue</a> on Github.
-    </footer>
-    <script src="https://unpkg.com/typed.js@2.1.0/dist/typed.umd.js"></script>
-    <script>
-    new Typed("#typed", {
-        strings: [
-            "jrnl Started writing my memoirs on the command line. 🎉🔥💻🔥🎉",
-            "jrnl yesterday 2pm: used jrnl to keep track of accomplished tasks. The done.txt for my todo.txt",
-            "jrnl <b>-from</b> 2019 <b>-until</b> may<br /><i>`(displays all entries from January 2019 to last May)`</i>",
-            "jrnl A day on the beach with @beth and @frank. Tagging them so I can easily look this up later.",
-            "jrnl <b>--tags</b><br /><i>`@frank    7<br />@beth    5</i>`",
-            "jrnl <b>--format</b> json<br /><i>`(Outputs your entire journal as json)</i>`",
-            "jrnl <b>--encrypt</b><br /><i>`(AES encryption. Don't lose your password!)</i>`"
-        ],
-        typeSpeed: 20, // less is faster
-        backSpeed: 10,
-        backDelay: 2500,
-        loop: true,
-        showCursor: false
-    });
-    </script>
-</body>
-
-</html>

docs_theme/index.js

@@ -1 +0,0 @@
-var typed2 =

docs_theme/main.html

@@ -1,17 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-{% extends "base.html" %}
-
-{%- block search_button %}
-  {% if 'search' in config['plugins'] %}
-    <div role="search">
-      <form id ="rtd-search-form" class="wy-form mkdocs-search" action="{{ base_url }}/search.html" method="get">
-        <input type="text" name="q" placeholder="Search docs" title="Type search term here" />
-        <button class="icon icon-search" aria-label="submit"></button>
-      </form>
-    </div>
-  {% endif %}
-{%- endblock %}

docs_theme/requirements.txt

@@ -1,2 +0,0 @@
-mkdocs>=1.4
-jinja2==3.1.6

docs_theme/search.html

@@ -1,34 +0,0 @@
-<!--
-Copyright © 2012-2023 jrnl contributors
-License: https://www.gnu.org/licenses/gpl-3.0.html
--->
-
-{% extends "main.html" %}
-
-{% block content %}
-
-<div role="search">
-  <form id ="content_search" class="wy-form mkdocs-search" action="{{ base_url }}/search.html" method="get">
-
-    <span role="status" aria-live="polite" class="ui-helper-hidden-accessible"></span>
-    <input
-      name="q"
-      id="mkdocs-search-query"
-      type="text"
-      class="search_input search-query ui-autocomplete-input"
-      placeholder="Search the Docs"
-      autocomplete="off"
-      autofocus
-      title="Type search term here"
-    >
-    <button class="icon icon-search" aria-label="submit"></button>
-  </form>
-</div>
-
-  <h1 id="search">Results</h1>
-
-  <div id="mkdocs-search-results" class="search-results">
-    Searching...
-  </div>
-
-{% endblock %}

features/core.feature

@@ -0,0 +1,49 @@
+Feature: Basic reading and writing to a journal
+
+    Scenario: Loading a sample journal
+        Given we use the config "basic.json"
+        When we run "jrnl -n 2"
+        Then we should get no error
+        and the output should be
+            """
+            2013-06-09 15:39 My first entry.
+            | Everything is alright
+
+            2013-06-10 15:40 Life is good.
+            | But I'm better.
+            """
+
+    Scenario: Writing an entry from command line
+        Given we use the config "basic.json"
+        When we run "jrnl 23 july 2013: A cold and stormy day. I ate crisps on the sofa."
+        Then we should see the message "Entry added"
+        When we run "jrnl -n 1"
+        Then the output should contain "2013-07-23 09:00 A cold and stormy day."
+
+    Scenario: Filtering for dates
+        Given we use the config "basic.json"
+        When we run "jrnl -on 2013-06-10 --short"
+        Then the output should be "2013-06-10 15:40 Life is good."
+        When we run "jrnl -on 'june 6 2013' --short"
+        Then the output should be "2013-06-10 15:40 Life is good."
+
+    Scenario: Emoji support
+        Given we use the config "basic.json"
+        When we run "jrnl 23 july 2013: 🌞 sunny day. Saw an 🐘"
+        Then we should see the message "Entry added"
+        When we run "jrnl -n 1"
+        Then the output should contain "🌞"
+        and the output should contain "🐘"
+
+    Scenario: Writing an entry at the prompt
+        Given we use the config "basic.json"
+        When we run "jrnl" and enter "25 jul 2013: I saw Elvis. He's alive."
+        Then we should get no error
+        and the journal should contain "2013-07-25 09:00 I saw Elvis."
+        and the journal should contain "He's alive."
+
+    Scenario: Displaying the version number
+        Given we use the config "basic.json"
+        When we run "jrnl -v"
+        Then we should get no error
+        Then the output should contain "version"

features/data/configs/basic.json

@@ -0,0 +1,14 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": false,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "",
+  "journals": {
+    "default": "features/journals/simple.journal"
+  },
+  "tagsymbols": "@"
+}

features/data/configs/broken.json

@@ -0,0 +1,15 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": false,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true
+  "password": "",
+  "journals": {
+    "default": "features/journals/simple.journal"
+    "work": "features/journals/work.journal",
+  },
+  "tagsymbols": "@"
+}

features/data/configs/bug153.json

@@ -0,0 +1,14 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": false,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "",
+  "journals": {
+    "default": "features/journals/bug153.dayone"
+  },
+  "tagsymbols": "@"
+}

features/data/configs/dayone.json

@@ -0,0 +1,14 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": false,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "",
+  "journals": {
+    "default": "features/journals/dayone.dayone"
+  },
+  "tagsymbols": "@"
+}

features/data/configs/empty_folder.json

@@ -0,0 +1,14 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": false,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "",
+  "journals": {
+    "default": "features/journals/empty_folder"
+  },
+  "tagsymbols": "@"
+}

features/data/configs/encrypted.json

@@ -0,0 +1,14 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": true,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "",
+  "journals": {
+    "default": "features/journals/encrypted.journal"
+  },
+  "tagsymbols": "@"
+}

features/data/configs/encrypted_with_pw.json

@@ -0,0 +1,14 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": true,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "bad doggie no biscuit",
+  "journals": {
+    "default": "features/journals/encrypted.journal"
+  },
+  "tagsymbols": "@"
+}

features/data/configs/multiple.json

@@ -0,0 +1,17 @@
+{
+  "default_hour": 9,
+  "timeformat": "%Y-%m-%d %H:%M",
+  "linewrap": 80,
+  "encrypt": false,
+  "editor": "",
+  "default_minute": 0,
+  "highlight": true,
+  "password": "",
+  "journals": {
+    "default": "features/journals/simple.journal",
+    "simple": "features/journals/simple.journal",
+    "work": "features/journals/work.journal",
+    "ideas": "features/journals/nothing.journal"
+  },
+  "tagsymbols": "@"
+}