Support printf formats in terminfo strings #7161
Closed
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
|
After discussion in IRC, I'm going to add some methods to |
terminfo parameterized strings supports a limited subset of printf-style formatting operations, such as %rust-lang#5.3d.
|
Turns out I actually don't even need those new methods to remove the unsafe blocks. |
|
The PR has been updated to remove all unsafe blocks. |
|
@kballard: test failed: http://buildbot.rust-lang.org/builders/auto-linux-all-opt/builds/13 bors appears to be stuck though |
|
Closing temporarily at @thestinger's request |
bors
added a commit
that referenced
this pull request
Jun 21, 2013
Introduce support for terminfo's subset of printf-style formatting on doxXs operations. r? @thestinger
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.
Introduce support for terminfo's subset of printf-style formatting on doxXs operations.
r? @thestinger