From: Robert Pluim <rpluim@gmail.com>
To: James Cloos <cloos@jhcloos.com>
Cc: pouar@pouar.net, 43148@debbugs.gnu.org
Subject: bug#43148: 27.1; Widget text seems to disappear when building with Cairo and Xaw
Date: Wed, 02 Sep 2020 12:45:07 +0200 [thread overview]
Message-ID: <m25z8wcv9o.fsf@gmail.com> (raw)
In-Reply-To: <m3tuwgxyr7.fsf@carbon.jhcloos.org> (James Cloos's message of "Wed, 02 Sep 2020 06:24:12 -0400")
>>>>> On Wed, 02 Sep 2020 06:24:12 -0400, James Cloos <cloos@jhcloos.com> said:
>>>>> "RP" == Robert Pluim <rpluim@gmail.com> writes:
RP> I can understand that, but nobody is stepping up to e.g. make Lucid
RP> work well on HiDPI screens, so it will become increasingly
RP> irrelevant.
James> why?
James> for emacs, higher dpi mostly just means larger fonts.
No it means "why canʼt I read the text in Emacs on my new HiDPI
monitor, everything else adapts automatically. What do you mean I have
to reconfigure Emacs to use larger fonts?"
James> if images ever need scaling, that should not be hard to do in emacs
James> itself.
James> gtk is horrid. (1 was ok; it only went downhill when novel got
James> involved, and that trend has continued.)
What alternative is there?
James> and the push for hb+cxr over m17n+xft means xaw(3d) w/ cairo should
James> become more and more common.
Iʼm not sure I see the connection there.
Robert
next prev parent reply other threads:[~2020-09-02 10:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 2:21 bug#43147: 27.1; Widget text seems to disappear when building with Cairo and Xaw Pouar Dragon
2020-09-01 14:09 ` bug#43148: " Eli Zaretskii
2020-09-01 15:05 ` Robert Pluim
2020-09-01 15:51 ` Eli Zaretskii
2020-09-01 16:13 ` Robert Pluim
2020-09-01 16:48 ` Eli Zaretskii
2020-09-02 6:59 ` Robert Pluim
2020-09-02 10:24 ` James Cloos
2020-09-02 10:45 ` Robert Pluim [this message]
2020-09-02 14:05 ` Eli Zaretskii
2020-09-02 14:28 ` James Cloos
2020-09-02 14:50 ` Eli Zaretskii
2020-09-02 15:19 ` Robert Pluim
2020-09-02 15:25 ` Eli Zaretskii
2020-09-02 13:57 ` Eli Zaretskii
2020-09-02 11:38 ` Peder O. Klingenberg
2020-09-03 9:09 ` Robert Pluim
2020-09-03 9:18 ` Robert Pluim
2020-11-25 2:30 ` Basil L. Contovounesios
2020-11-28 8:22 ` YAMAMOTO Mitsuharu
2020-12-01 13:10 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-03 2:13 ` YAMAMOTO Mitsuharu
2020-12-03 8:18 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 8:41 ` YAMAMOTO Mitsuharu
2020-12-04 9:28 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 9:48 ` Robert Pluim
2020-12-04 10:09 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 10:33 ` Robert Pluim
2020-12-04 10:58 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-04 11:46 ` Robert Pluim
2020-12-04 12:14 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-05 6:51 ` YAMAMOTO Mitsuharu
2020-12-05 7:14 ` tastytea via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-06 5:26 ` YAMAMOTO Mitsuharu
2020-12-06 5:58 ` Eli Zaretskii
2020-09-02 2:15 ` YAMAMOTO Mitsuharu
2020-09-28 10:46 ` Pouar Dragon
2020-11-23 17:38 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m25z8wcv9o.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=43148@debbugs.gnu.org \
--cc=cloos@jhcloos.com \
--cc=pouar@pouar.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).