Repository navigation
nvim: Detect structured file types when editing pass entries - #144
Merged
Merged
Conversation
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
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.
Detect Structured File Types When Editing pass Entries
Neovim detects the original format of filenames such as
config.json.txt, so structured secrets opened throughpass editget the expected language support.Rationale
Pass appends
.txtto its decrypted temporary filename even when the entry is namedconfig.jsonorcredentials.toml. Neovim therefore detects plain text. Delegating detection to Neovim after removing the final suffix reuses its built-in and custom mappings while preserving the actual filename that pass reads back for encryption.Key Changes
.txt, with normal detection for unknown formats and ordinary text files.