-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Support fixed width terminal windows #74501
Comments
@tlemo I'm interested in your use case? Do you just use small windows and/or some program is better on wide? |
Hi Daniel,
It's both. Perhaps a bit ironically, but on widescreen monitors it's nice to be able to use the terminal on the side (instead of top/bottom docking), so you end up with relatively narrow terminal windows.
And building from the command line can easily produce lines longer than 100+ columns. Same with some non-build logs. The general case is line-oriented output, where line wrapping can be jarring.
…On Thu, May 30, 2019 at 6:54 PM Daniel Imms ***@***.***> wrote:
@tlemo <https://github.com/tlemo> I'm interested in your use case? Do you
just use small windows and/or some program is better on wide?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#74501?email_source=notifications&email_token=ADJPEKPBAAPOUWR2JTDTHXTPYCAN3A5CNFSM4HQHVRIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWT7IWQ#issuecomment-497546330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADJPEKJZZ4TJTOMP6GO6EOTPYCAN3ANCNFSM4HQHVRIA>
.
|
Related: #79246 |
@Tyriar, I create PS functions that output other context specific PS commands that are quite long (because of blob paths, connection strings etc.) These then need to be copied and pasted in a single line, so having the original output wrap disrupts this methodology. |
@jagdishrajan you're meant to be able to be easily copy wrapped lines by double clicking them, is PS's table formatting preventing that or something? (if so you could try column selection with alt+drag) |
Integrated terminal with (1) no line wrapping + (2) horizontal scroll would also be useful to me. Use case Logs may include long strings: urls, ids, tokens, etc. -- also, nested JSON. I don't need to see all their contents; I just need to be able to see back up the history of logs. With line wrap, the visual structure is disrupted and it's hard to see what's going on. I'm on a small laptop, and I have the terminal as a column at the right. Current workaround |
I often print in the Terminal the contents of a pandas |
@Tyriar, terminal output can be used for many purposes such as reviewing results, copying portions of results or "other commands as results" and re-pasting them. As @tony-bony said columnar output that's aligned is difficult to review when wrapped. It's also important to select and copy multiple lines and vertical selection of results. When selecting these results switching to the mouse rather continuing to use the keyboard is inconvenient. (Vscode editor has works well with its Ctrl+Alt+Shift+arrow shortcut for this). |
My requirement is also similar to what @tony-bony has suggested above. VScode should allow to at least use the full width of the screen when Terminal docked at the bottom. It's not happening right now. Any workaround or timeline for this fix of terminal width? |
This would also be great for vs live sessions, most of the time the shared terminal ends up being 40x10 or something terrible like that. |
I would like to see a button which toggles wrap on/off entirely. When one is scrolling and skimming the terminal output, no wrap is nicer. When one needs to see the output of a particular line, wrap becomes necessary. A button or even just a keyboard shortcut to toggle line wraps in the integrated terminal on/off would be a nice feature. |
just out of curiosity how do you get that? for me it does not go in the next line it goes back to the beginning and starts overwriting what I have there, incredibly annoying. I really would like to not have any wrap at all. |
+1: I'm outputting from PC Lint Plus and using the tasks' problem catcher with regex. This all breaks down when I get new lines inserted anywhere for no obvious reasons (other than it wraps based on terminal width pixel count). |
I'm trying to compare output lines for mistakes that could cause a problem and it's difficult when lines suddenly wrap at an arbitrary point in the middle of a word. Also, some lines I'm dealing with are rather long and quickly make the task impossible when a single line wraps enough times to consume my entire visible terminal space vertically. Additionally, with line wrapping it's not always clear when I'm dealing with a new line of output versus the continuation of a wrapped line, depending on the length of the lines and how they begin and end. I can bail to an external terminal for now but that creates a lot of back-and-forth context switching that interrupts my flow. |
This could benefit the debugger feature "Run in Terminal" too. See the issue #100522, multiple extensions (such as JS, Dart, Java) are complaining that the startup command is very verbose, occupies multiple lines in the terminal and pollutes the program output. If it only renders the startup command in one line, that will mitigate the pain point. So allow disabling line wrapping in integrated terminal could make the terminal more clean. |
@testforstephen but it would need to be switched to wrapped after anyway which would wrap the line, otherwise the whole terminal would act differently to other terminals. |
Is it possible to turn off wrap on a certain line and still have all other lines wrapped? If not, I would like to have a user setting to control the line wrap for all terminals. |
@testforstephen this feature is about being able to control the dimensions of the terminal (and having a scroll bar), there definitely isn't ever going to be any mixed wrapping or line wrapping setting because that's not how terminals work. |
I commented to this feature request because i saw multiple issues about "Disable line wrap in integrated terminal" were marked as duplicates with this one. Do you need us to reopen an issue about "Disable line wrap in integrated terminal" for more discussion there again? |
I'm also interested in this. We use GLog for output which emits quite a lot of boilerplate at the start of each entry (timestamp, thread ID, source file & line number). The source file in particular has a variable length, which makes the payload text in each output entry inconsistently indented. To help me parse quickly, I'd really like one line per output entry, with no wrapping. Being able to set a massive fixed output width and use a scrollbar would help enormously. |
This becomes an issue when looking at structured print output for data frames. it is important to be able to take a look at structured data while analyzing/transforming/visualizing it. Here is a wide data frame print in F# via Deedle in comparison to a terminal that implements a horizontal scrollbar: removing wrap / setting a very large fixed with with a horizontal scrollbar would come a long way for data analysis in VSCode for me. |
A horizontal scrollbar would be awesome but even without that, if it's too technically complex for some reason, just having the option to have the terminal cut off lines rather than wrap them would go a very long way. |
I see that the Debug Console has an option to disable wrapping. Why not the Output and Terminal too? Edit: It seems for the Output tab, I can add this to
|
Scroll bars don't work yet and only a command for discovery Part of #74501
Upstream issue: xtermjs/xterm.js#3464 |
This makes the terminal element ancestors have the correct dimensions which should make it easier to use the scrollable element object Part of #74501
Great, looking forward to seeing it in action! |
Issue Type: Feature Request
For the integrated terminal, please add an option to set a fixed logical width, and a horizontal scroll bar when the terminal window is smaller than the logical width. Related to #46192 (but specific to the integrated terminal).
Seems also likely that this is what #48897 was asking for.
Thanks.
VS Code version: Code 1.34.0 (a622c65, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.16299
The text was updated successfully, but these errors were encountered: