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

Background image doesn't fill/cover ConEmu screen if pad size set larger than 0 #1231

Closed
zmni opened this Issue Aug 19, 2017 · 2 comments

Comments

Projects
2 participants
@zmni

zmni commented Aug 19, 2017

Versions

ConEmu build: 170814 Alpha x64
OS version: Windows 8.1 x64
Used shell version (Far Manager, git-bash, cmd, powershell, cygwin, whatever): cmd

Problem description

See title.

Steps to reproduce

  1. Set ConEmu pad size to any number larger than 0.
  2. Follow @Maximus5 guide on Ubuntu purple terminal colors in ConEmu.

Actual results

See title.

Expected results

Background image should entirely fill / cover ConEmu screen.

The only solution (now) is to manually change the color #0 equal to the color of the background image.

Additional files

ConEmu.xml.zip

screenshots

Maximus5 added a commit that referenced this issue Dec 26, 2017

gh-348, gh-1231, gh-1372: Let background image cover VCon pad areas too.
  When ‘Pad size’ is greater than zero or ‘Align ConEmu window size to cells’ is
  not checked or Splits exist the gaps may appears around VCon.

@Maximus5 Maximus5 added this to In progress in ConEmu Dec 27, 2017

@Maximus5 Maximus5 moved this from In progress to Ready for Testing in ConEmu Dec 27, 2017

@Maximus5 Maximus5 added the drawing label Dec 27, 2017

@Maximus5

This comment has been minimized.

Show comment
Hide comment
@zmni

This comment has been minimized.

Show comment
Hide comment
@zmni

zmni Jan 9, 2018

Will test this release asap. Thanks. 👍

zmni commented Jan 9, 2018

Will test this release asap. Thanks. 👍

@Maximus5 Maximus5 closed this Jan 18, 2018

ConEmu automation moved this from Ready for Testing to Done Jan 18, 2018

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