-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
Navigating between windows command shell and terminal #87848
Comments
I'll concur that the integrated terminal is extremely broken in VSCode. I'm a powershell user, and it's not even worth having the integrated terminal open. A good solution is to hit the '+' button, and open a new terminal. This seems to fix a lot of the navigation issues (think |
@shogerr Opening a new terminal doesn't fix the problem, and I shouldn't have to open a new terminal, terminal should operate the same way it does within windows itself. |
@SheepDomination, hey, I totally agree. I've just noticed that for myself, tab navigation etc seems to work in a terminal session that has not been opened as the integrated terminal. It's more of a lead to whomever takes up this ticket, that something about the behavior of the integrated terminal breaks the expected functionality of the terminal itself. Thanks for replying that you don't notice a change in behavior. I'll try and construct my replies so that the intention of the reply is a bit more clear. Did you notice any change at all in a new terminal session, or is it exactly the same? |
@shogerr In your second reply I got that I should try the tab key, whether I was right or wrong, I tried it; although unsuccessful. |
It looks like this issue has been assigned to someone. I've honestly not tried to troubleshoot this issue, and I'd also like to see some attention paid to this issue. That's pretty much why I replied: the more replies an issue gets, the bots will respond and up the priority. Microsoft painfully applies automation to their issues, so you have to wade through that nonsense. Let's hope Github doesn't turn into the Visual Studio developer forum. That would be a nightmare. |
@shogerr That explains why responses take so long, as you mentioned; it's automated. Otherwise you wait days for a response, if any response at all. |
Does the same thing happen with Windows Terminal? https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701 |
Isn't that kind of extreme to put Windows Terminal on? That's a UWP application, and after test driving it, I already know that it will never be permanent part of my system, ever. Other users may not have the same feeling, but... they just might. Could the user not install pwsh 7, rc1 instead? Would that not be a little more reasonable? |
@shogerr Windows Terminal provides and maintains the backend used for launching the processes and emulating pseudoterminals, I'm suggesting installing it so we can see if the bug is part of that component of VS Code's frontend. |
@SheepDomination Consider that when you create an issue here, you are getting involved with the development process for the application. Your issues helps improve the product because now you are participating in the development process: you are now a developer on the project in part. So, don't think of these issues like tickets that demand resolution from the team, but rather think of them like your contribution to the project as a developer: that's the nature of open source. An issue may or may not be addressed as part of the development process, depending on the discussion that happens here. @Tyriar Understood. |
@Tyriar It doesn't work well in Windows Terminal either. When I try to move the cursor up, it continues to go down among other issues as you see. |
While the issues look a little different, I suggest following this up with the terminal team first so they can fix the component that we depend on (conpty), then refile here if it's still a problem. https://github.com/microsoft/terminal Please link the terminal issue here when you create/find it. |
When running the same program in both a vanilla command shell in windows and within vscode terminal. The results are not identical when navigating between files ?
Windows Command Shell
Terminal in Code
The text was updated successfully, but these errors were encountered: