unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pouar@pouar.net, James Cloos <cloos@jhcloos.com>, 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 17:19:05 +0200	[thread overview]
Message-ID: <m2lfhs436e.fsf@gmail.com> (raw)
In-Reply-To: <83y2lsuta6.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Sep 2020 17:50:41 +0300")

>>>>> On Wed, 02 Sep 2020 17:50:41 +0300, Eli Zaretskii <eliz@gnu.org> said:

    >> From: James Cloos <cloos@jhcloos.com>
    >> Cc: rpluim@gmail.com,  pouar@pouar.net,  43148@debbugs.gnu.org
    >> Date: Wed, 02 Sep 2020 10:28:24 -0400
    >> 
    >> >>>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
    >> 
    EZ> So you are saying that the OP's problem started happening only
    EZ> yesterday?
    >> 
    >> no.
    >> 
    >> i'm saying that my current compile of master is twenty some hour old,
    >> uses xaw3d and cairo, and that, with -Q at least, menus display.

    Eli> Are you also using Lucid?

I donʼt think !Lucid + xaw3d is possible, but I haven't checked.

    Eli> If so, then maybe this problem cannot be easily reproduced on every
    Eli> platform in this build?

Iʼve just built emacs-27 with Lucid and xaw3d, and the menus display
fine. Iʼve tried YAMAMOTO-san's suggestion about
Emacs.pane.menubar.font, but with a non-existent font, and that also
works fine.

Robert





  reply	other threads:[~2020-09-02 15:19 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
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 [this message]
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=m2lfhs436e.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=43148@debbugs.gnu.org \
    --cc=cloos@jhcloos.com \
    --cc=eliz@gnu.org \
    --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).