unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Andrew Tropin <andrew@trop.in>,
	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: Fri, 10 Mar 2023 20:36:48 +0100	[thread overview]
Message-ID: <2d93af21c569ede63b95d6265d0a4bae88f2a5cd.camel@gmail.com> (raw)
In-Reply-To: <878rg4zbta.fsf@trop.in>

Am Freitag, dem 10.03.2023 um 22:44 +0400 schrieb Andrew Tropin:
> > > 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
> > 
> > As for the NEWS-29 file:
> > 
> > "Running this configuration on X is known to have problems, such as
> > undesirable frame positioning and various issues with keyboard
> > input of sequences such as 'C-;' and 'C-S-u'."
> > 
> > C.
> 
> I haven't used X for a while, but if it's still the case for 30
> version, I guess we can inherit pgtk from tree-sitter.
Correct me if I'm wrong, but isn't the point of C-S-u with pure GTK to
use GNOME's ibus widget?  Granted, we have other problems with ibus
currently, but it's still a part that makes the pgtk branch feel
gnomier.

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.

Cheers


  reply	other threads:[~2023-03-10 19:37 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 [this message]
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=2d93af21c569ede63b95d6265d0a4bae88f2a5cd.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=andrew@trop.in \
    --cc=csantosb@inventati.org \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.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 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).