unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: "Paul W. Rankin" <hello@paulwrankin.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Improving aesthetics & readability of backquote
Date: Mon, 20 May 2019 15:48:52 +0100	[thread overview]
Message-ID: <87d0kdi3l7.fsf@tcd.ie> (raw)
In-Reply-To: <m2zhnhmcp3.fsf@paulwrankin.com> (Paul W. Rankin's message of "Tue, 21 May 2019 00:18:32 +1000")

"Paul W. Rankin" <hello@paulwrankin.com> writes:

> On Mon, May 20 2019, Basil L. Contovounesios wrote:
>>> Are you suggesting that ,@b is easier to comprehend than (splice b)? I think
>>> that is a hard case to make. Try to put yourself in the mindset of someone
>>> just
>>> learning Emacs Lisp.
>>
>> I think this is a subjective matter, so the question is, as you say in
>> your other message, whether aliases should be added for those that
>> prefer the latter form; not which form each person finds most readable.
>
> I've written a function that doubles a number x, but I'm thinking about what to
> call it...
>
>    _||x&    or    (double x)
>
> Jokes aside, yes I do think Emacs would benefit from an option for people to use
> a clearer syntax for lisp form interpolation.

No objections from me.  My point was that the discussion should remain
focussed on the addition of such aliases, their implementation and
whether it's worth it, not about which form one finds more readable, as
that is a matter of personal taste.

-- 
Basil



  reply	other threads:[~2019-05-20 14:48 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  3:03 Improving aesthetics & readability of backquote Paul W. Rankin
2019-05-20  3:38 ` Stefan Monnier
2019-05-22 15:44   ` Stefan Monnier
2019-05-20  8:52 ` Alan Mackenzie
2019-05-20 13:25   ` Paul W. Rankin
2019-05-20 14:02     ` Alan Mackenzie
2019-05-20 14:26       ` Paul W. Rankin
2019-05-20 16:08         ` Ken Olum
2019-05-20 23:19   ` Richard Stallman
2019-05-21  2:06     ` Paul W. Rankin
2019-05-21  2:22       ` Noam Postavsky
2019-05-21  2:39         ` Paul W. Rankin
2019-05-21 20:19       ` Richard Stallman
2019-05-22  2:46         ` Paul W. Rankin
2019-05-22  7:56           ` Eli Zaretskii
2019-05-22  8:55             ` Paul W. Rankin
2019-05-22 15:57               ` Michael Heerdegen
2019-05-22 16:13                 ` 조성빈
2019-05-22 16:13               ` Michael Heerdegen
2019-05-22 22:40               ` Richard Stallman
2019-05-20  8:59 ` Lars Ingebrigtsen
2019-05-20 13:35   ` Paul W. Rankin
2019-05-20 13:47     ` Basil L. Contovounesios
2019-05-20 14:18       ` Paul W. Rankin
2019-05-20 14:48         ` Basil L. Contovounesios [this message]
2019-05-20 15:25     ` Lars Ingebrigtsen
2019-05-20 23:21       ` Richard Stallman
2019-05-21  2:34         ` Paul W. Rankin
2019-05-22 16:14 ` Sam Steingold

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=87d0kdi3l7.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=emacs-devel@gnu.org \
    --cc=hello@paulwrankin.com \
    --cc=larsi@gnus.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).