From: Tassilo Horn <tsdh@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [ELPA] Proposing to add express to ELPA
Date: Mon, 21 Aug 2023 11:04:40 +0200 [thread overview]
Message-ID: <87y1i4223t.fsf@gnu.org> (raw)
In-Reply-To: <0788786E-04DA-46DD-AA93-12603C09976F@gmail.com>
Yuan Fu <casouri@gmail.com> writes:
>> Would someone please explain to me what expreg does? I am not
>> against adding it -- if it meets the criteria and people like it, why
>> not? -- but I'd like to know what feature we are adding.
>
> It’s similar to expand-region, where repeatedly pressing a key expands
> the active region to enclose larger and larger constructs, words,
> statements, defuns, etc. I guess the selling point is that it’s
> simpler to configure and supports tree-sitter—weak justifications, but
> people liked it and requested to have it on ELPA, so I happily
> followed suit.
I've just tried it and also like it. I've used expand-region in the
past but only its basic features so expreg works just as well for me.
The only thing which seems missing and so common to justify a default
expander is marking a complete sentence in prose text. Right now, it
immediately jumps from work to paragraph.
Bye,
Tassilo
next prev parent reply other threads:[~2023-08-21 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
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 [this message]
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=87y1i4223t.fsf@gnu.org \
--to=tsdh@gnu.org \
--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).