From: "Óscar Fuentes" <ofv@wanadoo.es>
To: help-gnu-emacs@gnu.org
Subject: Re: branch feature/native-comp
Date: Mon, 11 Jan 2021 00:49:55 +0100 [thread overview]
Message-ID: <87eeiswdwc.fsf@telefonica.net> (raw)
In-Reply-To: 3155523.KtHYCLeg2q@linux-izun
AW <alexander.willand@t-online.de> writes:
> Hi!
>
> OS: Linux, Tumbleweed by openSUSE
>
> 1) Is there somewhere a description of the git branches of emacs at http://
> git.savannah.gnu.org/cgit/emacs.git ?
AFAIK, no.
> 2) Linux on desktop is moving towards wayland. As far as I understand it
> (probably completely wrong), this is done with a kind of GTK-Emacs.
>
> There is a pure gtk feature branch, "feature/pgtk". I compiled it and it works
> under "pure" wayland.
>
> By the way, "./configure --with-native-comp" didn't work (no surprise).
It is --with-nativecomp, but see below.
> But there is also a branch feature/native-comp, which doesn't work under
> wayland. I checked this branch out as well, compiled it, installed it, but no
> fun: At least I always get the GTK error "cannot open display: 1". But in
> a x11 environment (KDE Plasma) in a short test there were no issues.
The native-comp branch is not merged with into pgtk branch (nor into
master, so --with-nativecomp only works on the native-comp branch (and
that option is required to enable the feature)), so right now neither
branch contains those two features.
> As far as I understand it, sense of the latter branch is to speed up Emacs.
> And that makes me curious...
>
> Is there a way to get this native-compiled feature into an Emacs working under
> wayland?
You can try creating a new branch that merges those two.
next prev parent reply other threads:[~2021-01-10 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 22:24 branch feature/native-comp AW
2021-01-10 23:49 ` Óscar Fuentes [this message]
2021-01-11 18:15 ` AW
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=87eeiswdwc.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=help-gnu-emacs@gnu.org \
/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).