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

Scaling artifacts in Far Manager and Midnight commander #5240

Closed
parml opened this issue Apr 4, 2020 · 3 comments
Closed

Scaling artifacts in Far Manager and Midnight commander #5240

parml opened this issue Apr 4, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@parml
Copy link

parml commented Apr 4, 2020

Environment

Windows build number: Microsoft Windows NT 10.0.19041.0
Windows Terminal version: microsoft-windows-terminal 0.10.781.0

Any other software?
Chocolatey
Far

Steps to reproduce

  1. Install Far Manager. (e.g. with Chocolatey in an admin-enabled pwsh choco install far).
  2. Change your Display scaling to 125%. (Settings -> System -> Display -> Scale and layout -> 'Change the size of text...')
  3. Open Windows terminal. Open a Cmd, PowerShell or PowerShell Core tab.
  4. Start Far Manager. Type far.

Expected behavior

No unwanted artifacts due to scaling.

Actual behavior

Unwanted artifacts as black horizontal lines when scaling other than 100%, 200%. (c.f. PNG screenshot)

Note

PowerShell and PowerShell Core in their own windows behave correctly with all scaling settings(c.f. PNG screenshot)
Issue pertains to midnight commander in WSL instances (sudo apt install mc) (c.f. PNG screenshot)

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 4, 2020
@j4james
Copy link
Collaborator

j4james commented Apr 4, 2020

This is probably #3626, which has recently has a PR merged, so it should hopefully be fixed soon.

@DHowett-MSFT
Copy link
Contributor

This definitely is a /dupe of #3626! Thanks, as always, James.

@ghost
Copy link

ghost commented Apr 5, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Apr 5, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Apr 5, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants