-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
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
Feature Request: /help commands output to collapsible pane #644
Comments
Maybe it could be a cool differentiating feature to be able to select a region and pin it (or pull it out)? |
Maybe introduce the concept of Terminal specific commands. Maybe Which will place any output from that command into a side pane |
Named pipes would be ideal here I think, but if I recall correctly there are restrictions around UWP apps and pipes. Something like:
The unc syntax is unfortunate, but it would be more generic and helpful and reuse the existing cmd mechanisms. If I recall correctly, the restriction on named pipes with uwp apps is that you can do that between two uwp apps or two non-uwp apps, so maybe this will work? |
Not sure if it is possible to choose some kind of syntax that would be ignored by the existing command line, but recognised by the Windows Terminal. Just in case a batch script leaves it in when shared online |
I think this is probably the only reasonable suggestion here. Using Windows named pipes ties shell scripts to a specific terminal, and specifically a Windows-only terminal. It's often tough enough to get scripts to work on the same family of shells :) The same goes for using meta keywords like #region or something. @DHowett-MSFT 's suggestion doesn't tie the script to the terminal implementation, so it's the only sane one. |
If doing it as part of the typed command is a no go, then perhaps the ability to pin or drag output into a side pane. Perhaps with a pin icon beside the outputted text or via a context menu? Long output and having to select all the lines could be cumbersome |
It all depends on what the goal is. If the goal is to redirect output in a dynamic fashion, then pipes, etc. are the only portable way that I can think of offhand to do that through a shell, and people coming from a *NIX background are used to that model. If the goal is to simply create a collection of content for easy reference, then the "snip" and "pin" model might work quite nicely. |
Using named pipes shouldn't tie scripts to a specific terminal or a Windows-only terminal -- *NIX systems have those too, but I'm sure I'm just misunderstanding what the concern being expressed here is. The pipes concept is fairly universal in the developer world so it would be helpful to better understand the concern. The *NIX philosophy very much gravitates towards files. "snip" & "pin" vs redirection both have tradeoffs in opposite directions. |
For the record, Windows Terminal is a normal win32 application that's using UWP UI elements via XAML Islands. So named pipes aren't going to have the same problems for us that other UWP apps might have. I really do like this idea of pinning a region of output. Maybe we could store all the pinned blobs you have, and open a new pane on the side to display your pins? As far as doing it on the commandline, maybe we add support for |
When using command line tools, I often have to continuously repeat typing command /help to remind myself what I can do with the app.
If there was a way to output the text displayed when typing /help to a collapse box on the screen, I could then expand it to find a command, without having to keep either scrolling, or re-running the command
The text was updated successfully, but these errors were encountered: