all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Fix some tooltip related problems
Date: Fri, 12 Jan 2018 14:15:49 +0000	[thread overview]
Message-ID: <CAArVCkShsnCsO4FkgioxMsWvsvH=b8i6hWaVA9BQacx8Fom_-g@mail.gmail.com> (raw)
In-Reply-To: <878td318od.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

Robert Pluim <rpluim@gmail.com> schrieb am Fr., 12. Jan. 2018 um 14:58 Uhr:

> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> OK. But if we stop supporting GTK at some point, what ends up being
> >> its replacement? I doubt we'll be able to support Lucid and Motif
> >> forever, given that X is going to be replaced with Wayland.
> >
> > We should indeed move to supporting Wayland natively; volunteers are
> > most welcome to work on that.  The Cairo support was supposed to be
> > the first step in that direction, but it has known bugs and needs a
> > lot of loving care for us to be able to turn it on by default.
> > Working on this requires to have experts on board that we
> > unfortunately don't seem to have at this time, and that gap bothers me
> > personally quite a lot, because I think it's a serious threat to
> > Emacs's future.
>
> I'm unclear as to how we could 'support Wayland natively' without
> using some kind of toolkit for menus, scrollbars, etc.
>

We would support Wayland by using GTK+ correctly. GTK+ already supports
Wayland; we just need to get rid of the weird GTK+/X hybrid, and write a
proper GTK+-only "terminal".

[-- Attachment #2: Type: text/html, Size: 1605 bytes --]

  reply	other threads:[~2018-01-12 14:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  9:53 Fix some tooltip related problems martin rudalics
2018-01-08 14:41 ` Drew Adams
2018-01-08 18:19   ` martin rudalics
2018-01-08 18:50     ` Drew Adams
2018-01-09  9:42       ` martin rudalics
2018-01-09 15:08         ` Drew Adams
2018-01-10 10:20           ` martin rudalics
2018-01-10 15:55             ` Drew Adams
2018-01-10 19:17               ` Alan Third
2018-01-10 21:02                 ` Drew Adams
2018-01-10 23:04                   ` Alan Third
2018-01-10 23:26                     ` Drew Adams
2018-01-11  3:39                   ` Eli Zaretskii
2018-01-11  7:03                 ` Yuri Khan
2018-01-11 14:32                   ` Drew Adams
2018-01-11 10:56               ` martin rudalics
2018-01-11 14:42                 ` Drew Adams
2018-01-11 17:06                   ` martin rudalics
2018-01-11 17:19                     ` Robert Pluim
2018-01-11 17:59                       ` Eli Zaretskii
2018-01-11 18:20                         ` martin rudalics
2018-01-11 23:33                         ` Daniele Nicolodi
2018-01-12  8:38                           ` Eli Zaretskii
2018-01-12  8:40                         ` Robert Pluim
2018-01-12  9:55                           ` Eli Zaretskii
2018-01-12 13:57                             ` Robert Pluim
2018-01-12 14:15                               ` Philipp Stephani [this message]
2018-01-11 19:54                       ` Richard Stallman
2018-01-11 23:26                       ` Stefan Monnier
2018-01-12  8:48                         ` Robert Pluim
2018-01-11 18:09                     ` Drew Adams
2018-01-11 18:54                       ` martin rudalics
2018-01-11 19:50                         ` Drew Adams
2018-01-12  8:47                           ` martin rudalics
2018-01-12 16:43                             ` Drew Adams
2018-01-08 18:47 ` Eli Zaretskii
2018-01-08 19:06   ` martin rudalics
2018-01-08 19:22     ` Eli Zaretskii
2018-01-09  9:42       ` martin rudalics
2018-01-19 18:54 ` martin rudalics

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='CAArVCkShsnCsO4FkgioxMsWvsvH=b8i6hWaVA9BQacx8Fom_-g@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 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.