From: Christopher Dimech <dimech@gmx.com>
To: Emanuel Berg <incal@dataswamp.org>
Cc: emacs-devel@gnu.org
Subject: how to speed up Lisp devel time
Date: Fri, 9 Aug 2024 12:36:50 +0200 [thread overview]
Message-ID: <trinity-a3e68b43-a006-448c-a003-5cc1ac5b2bd8-1723199810769@3c-app-mailcom-bs09> (raw)
In-Reply-To: <87plqi3xzr.fsf@dataswamp.org>
> Sent: Friday, August 09, 2024 at 8:24 PM
> From: "Emanuel Berg" <incal@dataswamp.org>
> To: emacs-devel@gnu.org
> Subject: Re: how to speed up Lisp devel time
>
> Eli Zaretskii wrote:
>
> >> One thing one could try is to replace boring, trivial stuff
> >> with non-Lisp syntax and have that embedded. [...]
> >
> > Why do you need that?
>
> It is faster to type (fewer chars), and easier to edit, and
> more easy to read because not so packed with parenthesis.
> Overall faster, less error-prone.
>
> Another example could be, instead `let'/`let*', "wet":
>
> (wet
> var1 0
> var2 (some-lisp)
> )
>
> It is always like `let*' so no more annoying errors based
> on that!
We simple need the additional tools that go beyond the traditional ways
of reading source code. I suggest incorporating the functionality
of rainbow-delimiters into core emacs so that the functionality is automatic.
That solves the difficulties mentioned.
> It comes in two forms, either
>
> (wet
> var1 0
> var2 (some-lisp)
> (some-lisp-body)
> )
>
> where var1 and var2 would be bound in the Lisp
> (some-lisp-body), or just
>
> (wet
> var1 0
> var2 (some-lisp)
> )
>
> Where they would be valid for the rest of where ever you place
> it - the rest of the `defun', for example.
>
> --
> underground experts united
> https://dataswamp.org/~incal
>
>
>
prev parent reply other threads:[~2024-08-09 10:36 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-a3e68b43-a006-448c-a003-5cc1ac5b2bd8-1723199810769@3c-app-mailcom-bs09 \
--to=dimech@gmx.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.