unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
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
Date: Fri, 09 Aug 2024 15:02:24 +0300	[thread overview]
Message-ID: <86ed6xlx9r.fsf@gnu.org> (raw)
In-Reply-To: <87frre3pxa.fsf@dataswamp.org> (message from Emanuel Berg on Fri,  09 Aug 2024 13:18:25 +0200)

> From: Emanuel Berg <incal@dataswamp.org>
> Date: Fri, 09 Aug 2024 13:18:25 +0200
> 
> Eli Zaretskii wrote:
> 
> >>> Why do you need that?
> >> 
> >> I want it to work with M-x, C-u M-x, and C-u 100 M-x.
> >
> > This is rather unusual, and you should expect to have some
> > more-than-normally complicate code in that case.
> 
> What do you mean? It is the same for `forward-line'
> 
> C-u   M-x forward-line RET
> C-u 4 M-x forward-line RET

No, it isn't.  forward-line accepts a numeric argument, and that's
all.  All you need to do to support that is use the corresponding
'interactive' code.

> > Also, someone pointed out that you could write this in just
> > 83 characters.
> 
> Really? Well, well, let's see the code then!

It was posted, I just counted the characters.

> > That usually makes little sense in Emacs. Interactive and
> > non-interactive uses have different semantics.
> 
> Same default for any kind of call makes little sense. Usually!
> 
> I OTOH thinks that is the first policy I can think of.

Then your code is unlikely to be accepted into Emacs.

> > That happens, but very rarely. Well-designed clean code
> > should avoid that.
> 
> It is better if everyone, well-designers or not, could use
> a clean interface to do that. Then one could simply use it and
> not having to rely on people writing great Elisp for
> everything.

Code doesn't write itself.  Good design is always needed for elegant
code.



  reply	other threads:[~2024-08-09 12:02 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 [this message]
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
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=86ed6xlx9r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=incal@dataswamp.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).