Handle P4 special characters #91
Open
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
P4V restores the original filenames when syncing a file, but in the command line output of p4 commands the escapes are not restored, therefore the escape sequences "escaped" through p4-fusion into the Git repo filenames. This change resolves this bug. Co-authored-by: Márton Marczell <[email protected]>
Contributor
Author
|
In this fix, This can be changed so |
Contributor
Author
|
This will probably fix #74 |
Contributor
Author
|
[Docs (see Reserved characters)](https://help.perforce.com/helix-core/server-apps/p4guide/2022.2/Content/P4Guide/syntax.syntax.restrictions.html |
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.
P4V restores the original filenames when syncing a file, but in the command line output of p4 commands the escapes are not restored, therefore the escape sequences "escaped" through p4-fusion into the Git repo filenames. This change resolves this bug.