From: Yuan Fu <casouri@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [ELPA] Proposing to add express to ELPA
Date: Tue, 1 Aug 2023 12:09:43 -0700 [thread overview]
Message-ID: <87E8B2CD-CE95-4C9F-8764-C996FBDC91C5@gmail.com> (raw)
In-Reply-To: <87r0onjido.fsf@posteo.net>
> On Aug 1, 2023, at 1:07 AM, Philip Kaludercic <philipk@posteo.net> wrote:
>
> Yuan Fu <casouri@gmail.com> writes:
>
>> Hi all,
>
> Hi,
>
>> 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.
>>
>> The obvious downsides is that, of course, it’s pretty useless on
>> anything other than lisp if you don’t have tree-sitter grammars and
>> major mode installed. You can use it in a non-tree-sitter major mode,
>> as long the tree-sitter grammar exists. You only need to create a
>> parser and expreg will automatically use the parser [2].
>>
>> I’ve been using it for months and ironed out all sorts of edge-cases, and can recommend it for daily usage.
>
> this looks nice! I have a few comments that might be interesting:
Thanks for going over it. I incorporated your suggestions.
Yuan
next prev parent reply other threads:[~2023-08-01 19:09 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 [this message]
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
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=87E8B2CD-CE95-4C9F-8764-C996FBDC91C5@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).