unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Proposing to add express to ELPA
Date: Sat, 19 Aug 2023 09:04:39 +0000	[thread overview]
Message-ID: <87bkf3xv14.fsf@posteo.net> (raw)
In-Reply-To: <EA6F7ED8-BFFF-4D56-B166-550015F9A963@gmail.com> (Yuan Fu's message of "Fri, 18 Aug 2023 22:09:52 -0700")

Yuan Fu <casouri@gmail.com> writes:

>> On Aug 11, 2023, at 10:14 AM, Yuan Fu <casouri@gmail.com> wrote:
>> 
>> 
>> 
>>> On Jul 31, 2023, at 11:38 AM, Yuan Fu <casouri@gmail.com> wrote:
>>> 
>>> Hi all,
>>> 
>>> Since Emacs 29 is now released, I’d like to propose adding expreg
>>> to ELPA. Expreg can be considered a lite version of
>>> expand-region. The notable difference is its use of tree-sitter for
>>> language-specific expansions. I also took the liberty to do things
>>> differently than expand-region, eg, expreg uses a smaller number of
>>> expanders [1]; it is easier to debug when the expansion isn’t what
>>> you expected; and it only provides two functions for expansion and
>>> contraction, and one variable for adding/removing expanders—no
>>> transient maps and other “smart” features, nor different variables
>>> to set for each major mode.
>> 
>> What do you think, guys? Should it be added to ELPA?
>> 
>> Yuan
>
> I think I might have write access to ELPA, so if no one objects and no one adds it to ELPA, I’ll add it later :-)

If you have access to emacs.git, you should also have access to
elpa.git.  Just make sure to test building the package locally before
pushing anything.

> Yuan



  reply	other threads:[~2023-08-19  9:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 18:38 [ELPA] Proposing to add express to ELPA Yuan Fu
2023-08-01  8:07 ` Philip Kaludercic
2023-08-01 19:09   ` Yuan Fu
2023-08-11 17:14 ` Yuan Fu
2023-08-11 18:10   ` Emanuel Berg
2023-08-11 18:14   ` Philip Kaludercic
2023-08-19  5:09   ` Yuan Fu
2023-08-19  9:04     ` Philip Kaludercic [this message]
2023-08-20 17:07       ` Yuan Fu
2023-08-21  1:10     ` Richard Stallman
2023-08-21  4:08       ` Yuan Fu
2023-08-21  9:04         ` Tassilo Horn
2023-08-21  9:23           ` Tassilo Horn
2023-08-22  1:38           ` Yuan Fu
2023-08-22  9:56             ` Tassilo Horn
2023-08-28  7:23               ` Yuan Fu
2023-08-28  7:26                 ` Tassilo Horn

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=87bkf3xv14.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=casouri@gmail.com \
    --cc=emacs-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/emacs.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).