From: "C. Scott Ananian" <cananian@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 20619@debbugs.gnu.org
Subject: bug#20619: Another HiDPI issue
Date: Wed, 18 May 2016 08:24:19 -0400 [thread overview]
Message-ID: <CAHD_y+ZJpz9DadEWP1R4JeDi2NyfSDNt3oG5GT05Tczpcgud9w@mail.gmail.com> (raw)
In-Reply-To: <CAHD_y+Z1D37uNOcnrn2SaxSO9bksEOV_Ni0QhZ2fE1nLvMRD+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
What would be *more* useful, instead of guilt-tripping contributors, is to
offer some technical advice on the issue: where my program is likely to be
fine, what part of the code I might consider reading, and useful insight at
all. Then you might motivate me to scratch my own itch and *gain* a
contributor. Instead you are in the process of losing two.
On May 18, 2016 8:20 AM, "C. Scott Ananian" <cscott@cscott.net> wrote:
It's not like it's hard to reproduce: download gnome-tweak-tool and set
your scaling factor to 2. It doesn't require any special hardware.
[-- Attachment #2: Type: text/html, Size: 836 bytes --]
next prev parent reply other threads:[~2016-05-18 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 18:20 bug#20619: 24.5; Pop-up menus clipped on HiDPI (Gtk3/X11) Michael Droettboom
2015-05-23 12:06 ` Jan Djärv
2016-05-11 15:02 ` bug#20619: Another HiDPI issue C. Scott Ananian
2016-05-16 8:20 ` martin rudalics
2016-05-16 18:31 ` C. Scott Ananian
2016-05-18 7:00 ` martin rudalics
2016-05-18 12:20 ` C. Scott Ananian
[not found] ` <CAHD_y+aqKdHYBucR3VkwduiVWDex4oCmX6EeYYkoKC+Fb=RoSA@mail.gmail.com>
[not found] ` <CAHD_y+Z1D37uNOcnrn2SaxSO9bksEOV_Ni0QhZ2fE1nLvMRD+g@mail.gmail.com>
2016-05-18 12:24 ` C. Scott Ananian [this message]
2016-05-19 12:55 ` martin rudalics
2016-12-22 15:33 ` bug#20619: Improving HiDPI experience with emacs Eugen Dedu
2016-12-23 20:30 ` bug#20619: Scrollbars Eugen Dedu
2016-12-24 7:56 ` Eli Zaretskii
2016-12-27 22:45 ` Eugen Dedu
2016-12-28 15:41 ` Eli Zaretskii
2016-12-28 16:35 ` Eugen Dedu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHD_y+ZJpz9DadEWP1R4JeDi2NyfSDNt3oG5GT05Tczpcgud9w@mail.gmail.com \
--to=cananian@gmail.com \
--cc=20619@debbugs.gnu.org \
--cc=cscott@cscott.net \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.