Fix escaping of PS1 #7
Open
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
When traveling from the puppet manifest to the actual PS1 variable, a number of (un)escaping cycles happen: * we want these 2 characters in PS1: '\$' * Since PS1 is set as a double quoted string, we need to escape both the backslash and the dollar (to prevent variable expansion): "\\\$" * Puppet adds an additional layer of escaping. It's a single quoted string, so only the backslashes need escaping: '\\\\\\$'
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.
When traveling from the puppet manifest to the actual PS1 variable, a
number of (un)escaping cycles happen:
backslash and the dollar (to prevent variable expansion): "\\\$"
string, so only the backslashes need escaping: '\\\\\\$'