Repository navigation
Fix Windows file URIs against their own drive - #712
Merged
Merged
Conversation
ghostel--open-link handles every file://HOST/PATH URI itself: the path is percent-decoded as UTF-8, a local host opens the file directly and any other host opens it over TRAMP. Like fileref: links, all file links open in another window. The file:/PATH form without an authority is not handled, and `?' and `#' stay part of the file name. TRAMP name construction and URI path decoding move out of ghostel--update-directory into ghostel--tramp-path and ghostel--file-uri-decode, shared by OSC 7 and links.
Owner
|
Thanks. |
This branch was successfully deployed
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
2 participants
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.
Currently on Windows, the
file:///C:/data/file.txtwill not be resolved correctly. It got resolved to<current-drive>:/c:/data/file.txt.That's not correct according to RFC8089, this change fixed that.