fz0x1/jrnl
1
0
Fork 0
mirror of https://github.com/jrnl-org/jrnl.git synced 2025-05-12 09:28:31 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: vscode file history

Browse source
This commit is contained in:
Giuseppe D'Andrea 2023-02-12 12:01:44 +01:00
parent b4da3a51f7
commit 2775e390fc
No known key found for this signature in database
GPG key ID: 049CE9D9F970140E
1 changed files with 19 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
docs/privacy-and-security.md
View file

@ -73,6 +73,25 @@ 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 has a built-in local file history. When enabled, the file
contents of an editor that is saved will be stored to a history location to be
able to restore or review the contents later.
This leaky feature can be disabled for all files (including those for which
you might need the history) by unchecking the `workbench.localHistory.enabled`
setting in the [Settings editor](https://code.visualstudio.com/docs/getstarted/settings#_settings-editor).
Alternatively, you can configure a [pattern](https://code.visualstudio.com/docs/editor/codebasics#_advanced-search-options) in the `workbench.localHistory.exclude`
setting for excluding only specific files from local file history. For excluding
unencrypted temporary file generated by `jrnl`, you can set the `**/jrnl*.jrnl`
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`.
### Vim
Vim stores progress data in a so called Viminfo file located at `~/.viminfo`
@ -178,7 +197,6 @@ In Windows, the keychain is the Windows Credential Manager (WCM), which can't be
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.
## Notice any other risks?
Please let the maintainers know by [filing an issue on GitHub](https://github.com/jrnl-org/jrnl/issues).