[go: nahoru, domu]
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.

Sign up for GitHub

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

Jump to bottom

bug: The first execution of the pyenv command will cause the previous output to be cleared. #191

Open
Vixb1122 opened this issue Nov 14, 2020 · 3 comments
Open

bug: The first execution of the pyenv command will cause the previous output to be cleared. #191

Vixb1122 opened this issue Nov 14, 2020 · 3 comments

Comments

@Vixb1122
Copy link

Describe the bug
The first execution of the pyenv command will cause the previous output to be cleared.

To Reproduce
Steps to reproduce the behavior:

  1. open powershell, full output：
    image
  2. run 'pyenv vname', full output：
    image
  3. run 'pyenv vname' agiin, full output:
    image

Expected behavior
The previous output should not be cleared.

Desktop (please complete the following information):

  • OS: Windows 10
  • Tools used: PowerShell 7.1.0, Windows PowerShell and cmd both have this problem
  • Version: 2.64.3
@kirankotari
Copy link
Member

We are not sure what tools you are using, please check your tool settings. Pyenv is not cleaning the screen.

@Vixb1122
Copy link
Author
Vixb1122 commented Nov 15, 2020 •
edited
Loading

Can you tell me what the following line of code is for?

pyenv-win/pyenv-win/bin/pyenv.bat

Line 3 in b67712d

chcp 1250 >nul

After deleting the above code, this issue is solved.
@kirankotari

@kirankotari kirankotari reopened this Nov 15, 2020
@archiif
Copy link
archiif commented Dec 2, 2021

This also occurs with cmd.exe
Will this be fixed in the future?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kirankotari @Vixb1122 @archiif