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 17:58:00 +0300 [thread overview]
Message-ID: <86bk21lp53.fsf@gnu.org> (raw)
In-Reply-To: <87a5hl4x9b.fsf@dataswamp.org> (message from Emanuel Berg on Fri, 09 Aug 2024 15:54:40 +0200)
> From: Emanuel Berg <incal@dataswamp.org>
> Date: Fri, 09 Aug 2024 15:54:40 +0200
>
> Eli Zaretskii wrote:
>
> >>> 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.
>
> Okay, bad example.
>
> What about this one, then?
>
> C-u C-u a
> aaaaaaaaaaaaaaaa
>
> C-u 17 a
> aaaaaaaaaaaaaaaaa
These all are handled by the 'p' interactive code. So all you need is
this:
(defun some-fun (arg)
(interactive "p")
> >>> 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.
>
> Here is the original code [last], I said it was 402 chars but
> excluding the initial whitespace every line it is 376 chars.
>
> One can make it shorter here and there, but to write that in
> 83 chars of Elisp - well, let's see it.
https://lists.gnu.org/archive/html/emacs-devel/2024-08/msg00314.html
next prev parent reply other threads:[~2024-08-09 14:58 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 [this message]
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=86bk21lp53.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).