Skip to content
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

Closed
SheepDomination opened this issue Dec 29, 2019 · 12 comments
Closed

Navigating between windows command shell and terminal #87848

SheepDomination opened this issue Dec 29, 2019 · 12 comments
Assignees
Labels
info-needed Issue requires more information from poster terminal Integrated terminal issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@SheepDomination
Copy link

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
commandShell

Terminal in Code
vscodeterminal

@vscodebot vscodebot bot added the terminal Integrated terminal issues label Dec 29, 2019
@shogerr
Copy link

shogerr commented Dec 30, 2019

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 set-psreadlineoption -editmode emacs), but it's still far from useable.

@SheepDomination
Copy link
Author

@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.

@shogerr
Copy link

shogerr commented Dec 30, 2019

@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?

@SheepDomination
Copy link
Author

@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.
I didn't notice a change at all, it is exactly the same.

@shogerr
Copy link

shogerr commented Dec 30, 2019

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.

@SheepDomination
Copy link
Author

SheepDomination commented Dec 30, 2019

@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.
Someone told me it had to do with the Open source aspect of VSCode; now I know other wise, people can and will say anything.

@Tyriar
Copy link
Member

Tyriar commented Dec 30, 2019

Does the same thing happen with Windows Terminal? https://www.microsoft.com/en-us/p/windows-terminal-preview/9n0dx20hk701

@Tyriar Tyriar added the info-needed Issue requires more information from poster label Dec 30, 2019
@shogerr
Copy link

shogerr commented Dec 30, 2019

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?

@Tyriar
Copy link
Member

Tyriar commented Dec 30, 2019

@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.

@shogerr
Copy link

shogerr commented Dec 30, 2019

@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.

@SheepDomination
Copy link
Author

SheepDomination commented Dec 30, 2019

@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.
windowsterminal

@Tyriar
Copy link
Member

Tyriar commented Dec 31, 2019

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.

@Tyriar Tyriar closed this as completed Dec 31, 2019
@Tyriar Tyriar added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Dec 31, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster terminal Integrated terminal issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

3 participants