unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cayetano Santos <csantosb@inventati.org>
To: guix-devel@gnu.org
Subject: Emacs next variants
Date: Thu, 09 Mar 2023 19:51:23 +0100	[thread overview]
Message-ID: <87r0txr99u.fsf@inventati.org> (raw)


Hi guix,

  As for today, the inheritance of emacs, master branch, variants is as
  follows

    (emacs-next-tree-sitter (emacs-next-gtk (emacs-next (emacs))))

  Having tree-sitter is really useful, but optional, and doesn’t produce
  any harm to users. They may opt to use it, or not.

  This is not the case of the gtk variant. If one wants to use
  tree-sitter, the gtk variant is mandatory. When under x server, this
  produces a welcome warning advising about unattended effects, crashes,
  and leak of support when combining gtk emacs with x server.

  So, is there any reason for this dependency chain ? Why not ?

    (emacs-next-gtk (emacs-next-tree-sitter (emacs-next (emacs))))

Best,

Cayetano


             reply	other threads:[~2023-03-09 19:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 18:51 Cayetano Santos [this message]
2023-03-10 12:07 ` Emacs next variants 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
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0txr99u.fsf@inventati.org \
    --to=csantosb@inventati.org \
    --cc=guix-devel@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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).