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

DPI not handled correctly anymore #423

Closed
blueyed opened this issue Jun 26, 2016 · 5 comments
Closed

DPI not handled correctly anymore #423

blueyed opened this issue Jun 26, 2016 · 5 comments

Comments

@blueyed
Copy link
Contributor

blueyed commented Jun 26, 2016

The DPI handling appears to have regressed when moving to xcb-xrm in a7922cc.

See #254 (comment) for the initial report, that could be made to work using *.dpi: 176 in xrdb.

@DaveDavenport
Copy link
Collaborator

thx. will look at it.

@DaveDavenport
Copy link
Collaborator

*.dpi might not be valid syntax (https://tronche.com/gui/x/xlib/resource-manager/file-syntax.html)

*dpi: 133 should work

@DaveDavenport
Copy link
Collaborator

Yep. Xlib was violating spec.

@Airblader
Copy link

On a separate note, it's currently a bad idea to use only *dpi, even if spec-compliant. Some tools and libraries such as xcb-util-cursor and cairo-xcb, which have not yet adopted xcb-util-xrm, do a hard-coded match on Xft.dpi and will not be able to properly read *dpi. So you should probably use

Xft.dpi: 133
*dpi: 133

Of course feel free to report bugs against those projects so they can adopt xcb-util-xrm. :-)

@github-actions
Copy link

github-actions bot commented Nov 2, 2020

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants