unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Unknown <unknown@unknown.invalid>
To: 황병희 <soyeomul@red-october.yw.doraji.xyz>
Cc: help-gnu-emacs@gnu.org
Subject: Re: just question Wayland and Emacs
Date: Sun, 29 Sep 2019 20:02:34 +0900	[thread overview]
Message-ID: <68431EFB-29D4-4AC0-A10B-2C4FF0B5F00A@icloud.com> (raw)
In-Reply-To: <AF8E0FA4-0A9D-46BA-9B7E-4F22EF905AE2@icloud.com>


Sorry, forgot to CC the mailing list. 


> 2019. 9. 29. 오전 11:43, 황병희 <soyeomul@red-october.yw.doraji.xyz> 작성:
> 
> Hi i am chromebook user. Someday far later, if again i buy new chromebook
> (Pixelbook Go -- Atlas), i would like to use Emacs via Crostini. Already
> Chrome OS is going with Wayland as the version 76.0.3809.136 [1].

Why would  XWayland not be an option? Is it for Wayland purity? Or does XWayland not work in ChromeOS?

> So i
> question. How is it going to be Wayland porting for Emacs?

I’m not a developer, but I think Emacs doesn’t have a working Wayland backend. [0]
It does have a fork[1] working on a pure GTK3 backend though, so maybe that might be sufficient for your use. 

[0] https://emacs.stackexchange.com/questions/48561/is-there-an-x11-free-build-of-emacs-that-can-run-on-wayland-not-going-through-x

[1] https://github.com/masm11/emacs

> As end user, i'm
> somewhat curious about that. Really i will like Wayland-Emacs^^^
> 
> Sincerely,
> 
> [1] https://forum.ubuntu-kr.org/download/file.php?id=15282
> 
> -- 
> ^고맙습니다 _地平天成_ 감사합니다_^))//


       reply	other threads:[~2019-09-29 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AF8E0FA4-0A9D-46BA-9B7E-4F22EF905AE2@icloud.com>
2019-09-29 11:02 ` Unknown [this message]
2019-10-08 12:44   ` just question Wayland and Emacs 황병희
2019-09-29  2:42 황병희

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=68431EFB-29D4-4AC0-A10B-2C4FF0B5F00A@icloud.com \
    --to=unknown@unknown.invalid \
    --cc=help-gnu-emacs@gnu.org \
    --cc=soyeomul@red-october.yw.doraji.xyz \
    /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.
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).