Fall back to STANDARD_FAST_CONTENT_TYPE if STANDARD_CONTENT_TYPE is not set #135
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
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.
Goal
I was having issues with opening files/directories on gvfs remote mounts (ssh and smb). Whenever I'd try to open files on a remote mount, I'd get the
The given locations contain no images.error overlay.After a bit of digging, I was able to find that gvfs is no longer always providing
standard::content-typefor files.This branch updates Viewnior to fall back to
standard::fast-content-typeifstandard::content-typeis not availableReferences