Explicitly declare support for opening a path #2006
Conversation
This file contains 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
Without the field code, application launchers are not sure if starting nnn with a path argument is allowed. See https://specifications.freedesktop.org/desktop-entry-spec/latest/exec-variables.html
N-R-K
approved these changes
Feb 27, 2025
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.
While the nnn
.desktopfile hasMimeType=inode/directory, it is missing a field code to specify how the command line should be constructed with the directory's path. This can cause application launchers to disregard nnn as a file manager candidate.See https://specifications.freedesktop.org/desktop-entry-spec/latest/exec-variables.html.