unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: how to speed up Lisp devel time
Date: Sat, 10 Aug 2024 00:27:35 +0700	[thread overview]
Message-ID: <CAP_d_8V2RCW3c4iaMX5pnENyZMz3Sp79wu=98-Kz=dX7=a6GPQ@mail.gmail.com> (raw)
In-Reply-To: <871q2x4ra3.fsf@dataswamp.org>

On Fri, 9 Aug 2024 at 23:09, Emanuel Berg <incal@dataswamp.org> wrote:

> But actually it should be like this for interactive use:
>
> - With M-x: Prompt string for all three variables using their
>   default values as suggestions.
>
>   It should prompt again for each variable if it fails its
>   validation until it is OK. Whenever failing it should say
>   for example "end must be: (<= 0 end)" so the user knows what
>   went wrong.

If your command has three arguments, asking for them in succession
with validation and re-asking is the wrong UI/UX.

* A user may want to see the values entered for the first N arguments
when typing the (N+1)th.
* A user may want to fix a typo in the Nth argument when typing the (N+1)th.
* A user may want to recall the whole set of arguments from the
history, and optionally modify one or more of them.
* A user may want to switch to a different window or frame while
composing one of the arguments.

Interactive interface for more than one argument must be explicitly
designed. Asking for a more defaulting, more validating sequential
‘read-*’ is like asking Henry Ford for a faster horse.



  parent reply	other threads:[~2024-08-09 17:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  7:16 how to speed up Lisp devel time Emanuel Berg
2024-08-09  7:24 ` Eli Zaretskii
2024-08-09  7:39   ` Emanuel Berg
2024-08-09 10:43     ` Eli Zaretskii
2024-08-09 11:18       ` Emanuel Berg
2024-08-09 12:02         ` Eli Zaretskii
2024-08-09 13:54           ` Emanuel Berg
2024-08-09 14:58             ` Eli Zaretskii
2024-08-09 16:03               ` Emanuel Berg
2024-08-09 16:16                 ` Emanuel Berg
2024-08-09 17:54                   ` Eli Zaretskii
2024-08-09 18:56                     ` Christopher Dimech
2024-08-09 21:57                       ` Emanuel Berg
2024-08-09 21:47                     ` Emanuel Berg
2024-08-09 17:27                 ` Yuri Khan [this message]
2024-08-09 21:21                   ` Emanuel Berg
2024-08-10  2:14                   ` Emanuel Berg
2024-08-10  6:01                     ` Yuri Khan
2024-08-10  6:08                       ` Emanuel Berg
2024-08-10  6:44                         ` Yuri Khan
2024-08-10  7:22                           ` Emanuel Berg
2024-08-10  7:51                             ` Emanuel Berg
2024-08-10  4:32                   ` Emanuel Berg
2024-08-10  5:58                     ` Eli Zaretskii
2024-08-09 14:59             ` Eduardo Ochs
2024-08-09 16:19               ` Emanuel Berg
2024-08-09 18:00                 ` Eli Zaretskii
2024-08-09 18:54                   ` Christopher Dimech
2024-08-09 22:17                     ` Emanuel Berg
2024-08-09 22:00                   ` Emanuel Berg
2024-08-09  8:24   ` Emanuel Berg
2024-08-09 10:36     ` Christopher Dimech

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='CAP_d_8V2RCW3c4iaMX5pnENyZMz3Sp79wu=98-Kz=dX7=a6GPQ@mail.gmail.com' \
    --to=yuri.v.khan@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).