From: Charles Choi <kickingvegas@gmail.com>
To: emacs-devel@gnu.org
Cc: Stefan Kangas <stefankangas@gmail.com>,
Philip Kaludercic <philipk@posteo.net>
Subject: Re: Request to distribute Casual packages on NonGNU ELPA
Date: Thu, 26 Sep 2024 11:06:24 -0700 [thread overview]
Message-ID: <E24652A5-6CB6-4140-BD44-7E5907544705@gmail.com> (raw)
In-Reply-To: <87y13fqyl3.fsf@posteo.net>
Philip -
Appreciate your clarifications.
With regards to your comment on foundational questions, as best as I understand it, `quick-help` offers some level of control over display layout but is fundamentally a tool to provide informational help about a mode's bindings (typically default) to its commands. In contrast, Transient menus are designed to be a direct interface to the commands. Casual leverages the Transient library to create a keyboard-driven menu interface to this effect.
For Casual package users, a design intent of the Casual menus is to be the _primary_ means of accessing a mode's commands, as opposed to the current practice of using keybindings or the mini-buffer prompt as a primary interface. It is not a design intent of Casual to help on-board users to the existing default bindings of a mode, nor to cater to users who already know them for which Casual is not their intended audience.
In my view, tools such as `quick-help` and `which-key` reinforce keybindings and mini-buffer prompts as the primary user interface to a mode's commands. Casual is an attempt to offer an alternate primary interface, in this case, hand-crafted keyboard-driven menus. This said, Casual has no design intent to be a mutually exclusive user interface. All existing user interfaces to commands (keybinding, mini-buffer prompt, mouse menus) are still available.
Regards -
Charles
—
Charles Y. Choi, Ph.D.
kickingvegas@gmail.com
next prev parent reply other threads:[~2024-09-26 18:06 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
2024-09-26 18:06 ` Charles Choi [this message]
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=E24652A5-6CB6-4140-BD44-7E5907544705@gmail.com \
--to=kickingvegas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--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).