unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: 조성빈 <pcr910303@icloud.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: "Paul W. Rankin" <hello@paulwrankin.com>,
	emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>,
	rms@gnu.org
Subject: Re: Improving aesthetics & readability of backquote
Date: Thu, 23 May 2019 01:13:18 +0900	[thread overview]
Message-ID: <BA5F0F85-FAC2-4106-A44C-B062FBE0832A@icloud.com> (raw)
In-Reply-To: <877eaipjlv.fsf@web.de>


2019. 5. 23. 오전 12:57, Michael Heerdegen <michael_heerdegen@web.de> 작성:

> "Paul W. Rankin" <hello@paulwrankin.com> writes:
> 
>> Me:     As a comparatively new user, I remember when learning Emacs
>>        I found this part ugly and confusing. Here is a suggestion
>>        from such a perspective on how it could be improved.
> 
> Most people participating here have learned Lisp long time ago, so they
> probably don't remember how it was.

I learned Common Lisp about a year ago, and is teaching my friend CL. I learned Elisp a bit later, because I tried to customize my Emacs (which I started to use because of SLIME).
I think it’s pretty fair for me to say about beginner experiences.

> I'm quite sure that ` and , are indeed ugly, make Lisp more complicated
> and harder to learn.  But they have a huge advantage that more than
> outweighs all of that: they make complex list constructions much better
> readable.  But only after one got used to them.  Once you did get used
> to this syntax, it's invaluable.

I would say, it is indeed ugly; but it wasn’t a pain point. That’s not something begginers would say it’s complicated or harder to learn.
And, it allows beginners to gripe what ‘macro’ is, because it’s similar enough with real code to show that macros generate ‘code’ and different enough with real code to show that macros ‘generate’ code.
I immediately understood what macros do by just looking at the backquote, and my friend is having a similar experience.

> My personal opinion is that learners need to get used to it.  I'm not
> convinced allowing a different simpler syntax would be beneficial: it
> would complicate things and maybe keep newbies from learning a lesson
> they would need to learn anyway.
> 
> 
> Michael.
> 




  reply	other threads:[~2019-05-22 16:13 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                 ` 조성빈 [this message]
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
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=BA5F0F85-FAC2-4106-A44C-B062FBE0832A@icloud.com \
    --to=pcr910303@icloud.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=hello@paulwrankin.com \
    --cc=michael_heerdegen@web.de \
    --cc=rms@gnu.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).