unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "Peder O. Klingenberg" <peder@news.klingenberg.no>
Cc: 43148@debbugs.gnu.org
Subject: bug#43148: 27.1; Widget text seems to disappear when building with Cairo and Xaw
Date: Thu, 03 Sep 2020 11:18:53 +0200	[thread overview]
Message-ID: <m25z8v2p6q.fsf@gmail.com> (raw)
In-Reply-To: <m2eenj2pme.fsf@gmail.com> (Robert Pluim's message of "Thu, 03 Sep 2020 11:09:29 +0200")

>>>>> On Thu, 03 Sep 2020 11:09:29 +0200, Robert Pluim <rpluim@gmail.com> said:

>>>>> On Wed, 02 Sep 2020 13:38:12 +0200, "Peder O. Klingenberg" <peder@news.klingenberg.no> said:
    Peder> On ti., 2020-09-01 kl. 17.05 +0200 +0200, Robert Pluim wrote:
    >>> 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).

    Peder> (GTK simply doesn't work for me because I depend on daemon mode and Emacs not
    Peder> crashing when a display goes away.)

What I meant to say before I rudely interrupted myself: thereʼs an
effort to have emacs use 'pure' GTK that might solve this, although
the solution could end up at 'use Wayland', which as far as I know
doesnʼt have the equivalent of X display forwarding yet, so that still
wouldnʼt solve your issue (assuming youʼre doing ssh -X or similar).

Robert








  reply	other threads:[~2020-09-03  9:18 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
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 [this message]
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=m25z8v2p6q.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=43148@debbugs.gnu.org \
    --cc=peder@news.klingenberg.no \
    /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).