From: Simon Tournier <zimon.toutoune@gmail.com>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: csantosb@inventati.org, guix-devel@gnu.org,
Andrew Tropin <andrew@trop.in>
Subject: Re: Emacs next variants
Date: Fri, 10 Mar 2023 19:14:16 +0100 [thread overview]
Message-ID: <CAJ3okZ2OuC0PsQ3S1VE2SL6H+7FKChRdM87vuKQadWs1tx07Gg@mail.gmail.com> (raw)
In-Reply-To: <87v8j8czk4.fsf@protonmail.com>
Hi,
On Fri, 10 Mar 2023 at 17:59, John Kehayias
<john.kehayias@protonmail.com> wrote:
> During this discussion some changes were made to this inheritance structure in
>
> <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=b4c64ddce44bb31332784c3f8e037bd565194604>
>
> and
>
> <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=070c335a91d5c245f0360e12c794e9109f9faaf1>
Thanks for pointing that. From my understanding, it does not change
what Cayetanos is raising: emacs-next-tree-sitter is built using
'--with-pgtk'. In fact, the package emacs-next-tree-sitter is built
using the master branch (Emacs 30 unbranched yet) with tree-sitter
*and* pgtk support.
Cheers,
simon
next prev parent reply other threads:[~2023-03-10 18:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 18:51 Emacs next variants Cayetano Santos
2023-03-10 12:07 ` Simon Tournier
2023-03-10 14:56 ` Cayetano Santos
2023-03-10 15:39 ` Simon Tournier
2023-03-10 16:59 ` John Kehayias
2023-03-10 18:14 ` Simon Tournier [this message]
2023-03-10 18:24 ` Cayetano Santos
2023-03-10 18:44 ` Andrew Tropin
2023-03-10 19:36 ` Liliana Marie Prikler
2023-03-12 5:18 ` Andrew Tropin
2023-03-12 7:46 ` Liliana Marie Prikler
2023-03-12 8:47 ` Andrew Tropin
2023-04-26 18:52 ` Mekeor Melire
2023-06-13 5:26 ` Andrew Tropin
2023-03-12 9:46 ` indieterminacy
2023-03-12 12:51 ` Liliana Marie Prikler
2023-03-10 20:39 ` Cayetano Santos
2023-03-12 5:11 ` Andrew Tropin
2023-03-10 18:36 ` Andrew Tropin
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=CAJ3okZ2OuC0PsQ3S1VE2SL6H+7FKChRdM87vuKQadWs1tx07Gg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=andrew@trop.in \
--cc=csantosb@inventati.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.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/guix.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.