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

True color mode with powershell doesn't scroll correctly #1569

Closed
Thraka opened this Issue May 21, 2018 · 3 comments

Comments

Projects
2 participants
@Thraka

Thraka commented May 21, 2018

Versions

ConEmu build: 180506 x64
OS version: Windows 10 1703 x64
Used shell version: PowerShell

Problem description

The position of the fancy 256 background colors do not scroll with the content. I'm using \Addons\AnsiColors256.ans to print out the color content to test. If my prompt has a single line (as seen in the gif below) the part of the background colors stay in the same place as the content scrolls.

problem

Additionally, when my prompt is two lines (a new line character in the prompt) the results are messed up right away and when scrolling the 16 color boxes scroll at 2 lines per ENTER pressed and the 256 color boxes scroll at 1 line per ENTER pressed. This is different from the single line prompt shown in the gif above where the 256 color boxes stay in the same position all the time.

Steps to reproduce

  1. Open powershell tab
  2. run gc PATH TO YOUR CONEMU\Addons\AnsiColors256.ans
  3. Hit enter over and over to scroll the screen with new lines

Additional files

settings.zip

@Maximus5 Maximus5 added this to To Do in ANSI via automation May 21, 2018

@Maximus5 Maximus5 moved this from To Do to In progress in ANSI May 27, 2018

@Maximus5 Maximus5 moved this from In progress to Ready for Testing in ANSI May 29, 2018

@Thraka

This comment has been minimized.

Thraka commented Jun 6, 2018

Verified fixed. Thanks!

@Thraka Thraka closed this Jun 6, 2018

ANSI automation moved this from Ready for Testing to Done Jun 6, 2018

@Thraka

This comment has been minimized.

Thraka commented Jun 6, 2018

Should I have not closed this? I didn't realize you had some automation stuff doing things...

@Maximus5

This comment has been minimized.

Owner

Maximus5 commented Jun 6, 2018

Issues in "Ready for Testing" shall be either closed or moved back to backlog on problems

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment