Workspace trust: improve docs#15531
Closed
xe-nul wants to merge 1 commit into
Closed
Conversation
xe-nul
commented
Mar 27, 2026
| Helix will not trust any workspace by default. | ||
|
|
||
| If you decide not to trust a workspace and don't want to be prompted about trust every time you start a new session in it, you can exclude the workspace by choosing `Never` option in trust selection window. | ||
| When you open a file in an untrusted workspace, you will be prompted about trust. You can make a choice with arrow keys, `<Tab>`, `<C-n>` and `<C-p>`, confirming selection with `<Enter>`. Typing anything else will close the menu selecting 'Not now' option. |
Contributor
Author
There was a problem hiding this comment.
This is probably more words than we really need, but what I am trying to say here is: you can make the menu go away by pressing pretty much any button except those that do something in the menu.
I think that's really important to understand, so that the thing doesn't get in the way. On the second thought, it should get pretty apparent when you actually use the thing yourself, so it might not need an explanation.
xe-nul
commented
Mar 27, 2026
| <!-- TODO: Windows paths --> | ||
| Lists of trusted and excluded workspaces, delimited by newline characters, are stored in: | ||
| - Linux and macOS: `~/.local/share/helix/trusted_workspaces` and `~/.local/share/helix/excluded_workspaces` | ||
| - Windows: `%AppData%/Roaming/helix/trusted_workspaces` and `%AppData%/Roaming/helix/excluded_workspaces` |
Contributor
Author
There was a problem hiding this comment.
Windows path is taken from etcetera's crate code. If I'm holding that code right, this is where it should be stored, but I hope someone with Windows box comes around and tells for sure.
Contributor
Author
|
Closed in favor of #15636 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When I wrote docs for the original PR, I tried to make them as comprehensive as possible. They weren't much comprehensible as a result.
Here, for clarity sake, I tried to remove things that probably shouldn't be explained in the first place.