We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Posh should support terminal boxes/borders around content.
These can be simply expressed in a string, and the spaces in that string can be used to content placement.
$Posh.Host.UI.Boxes/Borders
$Posh.Host.UI.Boxes # should return the known boxes
Posh.Host.Ui.Boxes.Add
Posh.Host.UI.Boxes.Remove
Boxes should be defined in NoteProperties of Posh.Host.UI.Boxes.
Posh.Host.UI.Boxes
Boxes should normally be defined by a simple string.
For example, a "box" could be made out of "*"
$Posh.Host.UI.Boxes.Add("Star", '*')
A box could also be provided by a grid of characters, for example:
$Posh.Host.UI.Boxes.Add("PipeDash", @' |-| | | |-| '@)
The blank spacing in this box could be filled with content, and the characters bracketing that blank space can be extended.
This logic gets even more interesting if the box definition is a 5x5 matrix:
$Posh.Host.UI.Boxes.Add("Double", @' ╔═╦═╗ ║ ║ ║ ╠═╬═║ ║ ║ ║ ╚═╩═╝ '@)
Essentially, can define what all types of intersection should look like within a box, we can extend that box infinitely.
There should be several of these built-in boxes.
After several have been defined, we should start work on the Box pseudotype:
Posh.Host.UI.Box
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Posh should support terminal boxes/borders around content.
These can be simply expressed in a string, and the spaces in that string can be used to content placement.
$Posh.Host.UI.Boxes/Borders
should return a collection of boxes/borders #335Posh.Host.Ui.Boxes.Add
should add a box #336Posh.Host.UI.Boxes.Remove
should remove a box #337Boxes should be defined in NoteProperties of
Posh.Host.UI.Boxes
.Boxes should normally be defined by a simple string.
For example, a "box" could be made out of "*"
A box could also be provided by a grid of characters, for example:
The blank spacing in this box could be filled with content, and the characters bracketing that blank space can be extended.
This logic gets even more interesting if the box definition is a 5x5 matrix:
Essentially, can define what all types of intersection should look like within a box, we can extend that box infinitely.
There should be several of these built-in boxes.
After several have been defined, we should start work on the Box pseudotype:
Posh.Host.UI.Box
Pseudotype #372The text was updated successfully, but these errors were encountered: