From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.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: Tue, 01 Sep 2020 18:51:47 +0300 [thread overview]
Message-ID: <83d035wl4c.fsf@gnu.org> (raw)
In-Reply-To: <m2d035edv0.fsf@gmail.com> (message from Robert Pluim on Tue, 01 Sep 2020 17:05:55 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: Pouar Dragon <pouar@pouar.net>, YAMAMOTO Mitsuharu
> <mituharu@math.s.chiba-u.ac.jp>, 43148@debbugs.gnu.org
> Date: Tue, 01 Sep 2020 17:05:55 +0200
>
> >>>>> On Tue, 01 Sep 2020 17:09:18 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: Pouar Dragon <pouar@pouar.net>
> >> Date: Mon, 31 Aug 2020 21:34:46 -0500
> >>
> >> widgets when building with Xaw and Cairo seem to have missing text,
> >> looking like this
> >>
> >> problem seems to go away when 5f4e8e2e088de9fb76cb631077c6eddd3219f594
> >> is reverted
>
> Eli> Thanks. I hope Yamamoto-san will be able to take a look at this.
>
> Putting on my 'let's simplify' hat, is this really a combination we
> want to spend time on? Lucid + Xaw + Cairo is decidedly non-mainstream
> (Iʼm surprised it even builds).
I wasn't aware that it's a rare configuration. We definitely support
Lucid, right? If so, is Xaw the problem? and if it is, what are the
alternatives that are less "non-mainstream"?
next prev parent reply other threads:[~2020-09-01 15:51 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 [this message]
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
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=83d035wl4c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43148@debbugs.gnu.org \
--cc=pouar@pouar.net \
--cc=rpluim@gmail.com \
/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).