From: Andrew Tropin <andrew@trop.in>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
csantosb@inventati.org, Simon Tournier <zimon.toutoune@gmail.com>
Cc: John Kehayias <john.kehayias@protonmail.com>, guix-devel@gnu.org
Subject: Re: Emacs next variants
Date: Sun, 12 Mar 2023 12:47:44 +0400 [thread overview]
Message-ID: <87cz5ebbkf.fsf@trop.in> (raw)
In-Reply-To: <ca6e28296523fa673c295d1a4757eae8673250c5.camel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
On 2023-03-12 08:46, Liliana Marie Prikler wrote:
> Am Sonntag, dem 12.03.2023 um 09:18 +0400 schrieb Andrew Tropin:
>> > As for tree-sitter-with/without-gtk, I have no opinion here. We
>> > could try exporting package rewriters so that everyone can have
>> > their cup of tea, but maintaining one's own Emacs on the
>> > user/channel level ought not to be too difficult either.
>>
>> I guess inheriting pgtk from tree-sitter looks most logical here: no
>> potential problems for X users, tree-sitter for wayland users.
>> Updated the inheritance hierarchy.
> For the future, I think we should be careful not to be too close to the
> master branch. emacs-next has thus far historically been a package to
> try out things for the next release, not the one after that. The
> inclusion of a package variant with tree-sitter necessitated a change,
> but for packages that don't need it we should go back to tailing pre-
> releases as soon as reasonable.
Sure, I think after the release of emacs-29 we can make emacs-next to
track emacs-30 and deprecate emacs-next-tree-sitter and after emacs-30
release we will include tree-sitter in emacs package itself and also we
will be able to move emacs-next-pgtk to emacs-pgtk.
--
Best regards,
Andrew Tropin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2023-03-12 8:48 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
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 [this message]
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=87cz5ebbkf.fsf@trop.in \
--to=andrew@trop.in \
--cc=csantosb@inventati.org \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=liliana.prikler@gmail.com \
--cc=zimon.toutoune@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/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.