Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation about journal-level config values #1196

Closed
sriniv27 opened this issue Feb 20, 2021 · 2 comments · Fixed by #1199
Closed

Update documentation about journal-level config values #1196

sriniv27 opened this issue Feb 20, 2021 · 2 comments · Fixed by #1199
Labels
documentation Improvements or additions to documentation 📌 This can't go stale

Comments

@sriniv27
Copy link
Contributor

Documentation Change

Affected Page(s)

What Could Be Better?

The section on multiple journal files makes a passing mention that a specific journal can have its own configured options, but the examples are only limited to preferences for encrypt. It is left to the reader to extrapolate that things like timeformat, editor, etc. can also be configured on a per-journal basis.

Other Information

I think that a couple of code snippets or even an extension of the existing snippet should suffice.

Another (not necessarily exclusive) option is to update recipes with workflows that allude to it.

@sriniv27 sriniv27 added 🆕 New! documentation Improvements or additions to documentation labels Feb 20, 2021
@wren wren changed the title Per-journal configuration could have more examples showing that journals can have *any* amount of customizations applied to them Update documentation about journal-level config values Feb 20, 2021
@wren wren added 📌 This can't go stale and removed 🆕 New! labels Feb 20, 2021
@wren
Copy link
Member

wren commented Feb 20, 2021

Good catch!

@micahellison
Copy link
Member

Resolved by #1199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation 📌 This can't go stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants