how to speed up Lisp devel time

[Christopher Dimech <dimech@gmx.com>]

> Sent: Saturday, August 10, 2024 at 6:00 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Emanuel Berg" <incal@dataswamp.org>
> Cc: emacs-devel@gnu.org
> Subject: Re: how to speed up Lisp devel time
>
> > From: Emanuel Berg <incal@dataswamp.org>
> > Date: Fri, 09 Aug 2024 18:19:58 +0200
> >
> > (defun draw-scale (&optional end step i)
> >   (interactive (if (numberp current-prefix-arg)
> >                    (list current-prefix-arg)
> >                  current-prefix-arg))
>
> Using "p" doesn't prevent you from testing the value of
> current-prefix-arg, if that is what you want to do.
>
> But in general, having commands with more than one optional argument
> (two when the command acts on a region) is not recommended, because it
> complicates the interactive usage.

This complexity is not inherently negative, and there are compelling
reasons to embrace it in certain situations.  Commands with multiple
optional arguments offer greater flexibility.

They allow users to fine-tune the behavior of a command without needing
multiple versions of the same command.  For example, a command that
processes text in a region might need to handle different edge cases or
modes of operation.  Providing multiple optional arguments, users can
specify exactly how they want the command to behave, which can be more
efficient and powerful than using multiple commands or a simpler interface.
And more advanced users often seek out commands that provide granular control.

In an environment like Emacs, which is known for its powerful, customizable,
and sometimes complex commands, advanced users often appreciate the ability
to use optional arguments.

Embrace complexity, complexity is not inherently bad, it's a trade-off.
Proper documentation, intuitive default behaviors, and a clear understanding
of when and how to use optional arguments can ensure that this complexity
enhances the user experience rather than detracting from it.