From: Philip Kaludercic <philipk@posteo.net>
To: Charles Choi <kickingvegas@gmail.com>
Cc: emacs-devel@gnu.org, Stefan Kangas <stefankangas@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Request to distribute Casual packages on NonGNU ELPA
Date: Wed, 25 Sep 2024 20:15:36 +0000 [thread overview]
Message-ID: <87y13fqyl3.fsf@posteo.net> (raw)
In-Reply-To: <D49214A1-3437-46B2-94FD-3248AA19DDFF@gmail.com> (Charles Choi's message of "Wed, 25 Sep 2024 13:05:22 -0700")
Charles Choi <kickingvegas@gmail.com> writes:
> Philip -
>
> Thanks for responding. My answers to your questions as follows:
>
>> I haven't tried the code yet, and reviewing these will take some time,
>> but my understanding that this is reinventing a lot of Emacs
>> functionality using Transient, right?
>
> The Casual packages should be viewed as user interface porcelains to
> existing Emacs functionality and takes great effort to not "reinvent"
> nor re-implement existing commands and their associated variables. No
> functions are advised by Casual. The Casual packages do however
> re-imagine the interactive user interfaces to said commands and
> variables as keyboard-driven menus.
Sorry, I was not clear: Read the "Reinventing" as "Rebinding". And IIUC
then this is the case.
>> Do you have any preferred or recommended order in which you think that I
>> should review the code? From the names I am guessing that casual-lib is
>> a dependency that the others share?
>
> casual-lib is a common library to all the Casual packages. It is
> recommended that this package be reviewed first. casual-suite is an
> umbrella package that includes all Casual packages and as such should
> be reviewed last.
>
> At current there are 13 Casual packages to review. Here's a
> recommended order of review that skews toward the simpler packages to
> be reviewed earlier. That said the only strict guidance is to review
> casual-lib first and casual-suite last.
>
> https://github.com/kickingvegas/casual-lib/
>
> https://github.com/kickingvegas/casual-isearch/
> https://github.com/kickingvegas/casual-symbol-overlay/
> https://github.com/kickingvegas/casual-avy/
> https://github.com/kickingvegas/casual-re-builder/
> https://github.com/kickingvegas/casual-dired/
> https://github.com/kickingvegas/casual-bookmarks/
> https://github.com/kickingvegas/casual-calc/
> https://github.com/kickingvegas/casual-ibuffer/
> https://github.com/kickingvegas/casual-info/
> https://github.com/kickingvegas/casual-agenda/
> https://github.com/kickingvegas/casual-editkit/
>
> https://github.com/kickingvegas/casual-suite/
Thanks.
>> Another question that I can only raise now as I haven't looked at the
>> code in greater detail yet is how deep the transient dependency goes.
>> Would it be possible to re-use quick-help instead? I had sketched
>> something along those lines a few months back, where a map could bind a
>> pseudo-key to return a `help-quick-sections' like structure. The
>> advantage is that you only have to list commands and descriptions,
>> without trying to bind key again inside of Transient, as I understand it
>> being the case right now.
>
> The Casual packages use Transient to implement keyboard-driven menus
> with opinionated bindings. I consider these binding decisions to be
> core to the value of Casual in that they support a truly hand-crafted
> user experience. I have no interest in refactoring their behavior to
> use quick-help, nor in maintaining strict conformance to existing
> default command bindings. That said, many existing default command
> bindings are supported in Casual. If any of these positions are a
> block to publication on NonGNU ELPA, I will retract my request for
> review. Hopefully though this is not the case as I have the greatest
> enthusiasm to see these packages being reviewed and published on ELPA.
No, none of this is blocking. I just find it worthwhile to discuss some
more foundational questions before adding a package to ELPA, as an
outsides perspective can sometimes help to uncover questions that an
author might not have considered until now.
>
> All my best -
>
> Charles
>
> —
> Charles Y. Choi, Ph.D.
> kickingvegas@gmail.com
>
>
>
--
Philip Kaludercic on siskin
next prev parent reply other threads:[~2024-09-25 20:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 21:35 Request to distribute Casual packages on NonGNU ELPA Charles Choi
2024-09-25 17:30 ` Stefan Kangas
2024-09-25 18:30 ` Philip Kaludercic
2024-09-25 20:05 ` Charles Choi
2024-09-25 20:15 ` Philip Kaludercic [this message]
2024-09-26 18:06 ` Charles Choi
2024-09-28 3:08 ` Richard Stallman
2024-09-28 3:08 ` Richard Stallman
2024-09-28 8:52 ` Charles Choi
2024-09-27 15:52 ` Philip Kaludercic
2024-09-27 16:04 ` Philip Kaludercic
2024-09-27 18:12 ` Charles Choi
2024-09-27 18:58 ` Stefan Monnier
2024-09-27 20:05 ` Philip Kaludercic
2024-09-28 14:02 ` Philip Kaludercic
2024-09-26 19:08 ` Charles Choi
2024-09-27 4:40 ` Stefan Kangas
2024-09-27 15:34 ` Philip Kaludercic
2024-09-27 16:13 ` Charles Choi
2024-09-27 16:03 ` Stefan Monnier
2024-09-27 19:20 ` Charles Choi
2024-09-30 3:26 ` Richard Stallman
2024-09-30 3:57 ` Emanuel Berg
2024-10-03 3:33 ` Richard Stallman
2024-09-25 23:44 ` Stefan Kangas
2024-09-26 17:01 ` Charles Choi
2024-09-26 18:05 ` Adam Porter
2024-09-27 15:18 ` Philip Kaludercic
2024-09-27 5:43 ` Stefan Kangas
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=87y13fqyl3.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=kickingvegas@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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/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).