From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: introduction to lisp
Date: Tue, 20 Jun 2017 10:42:55 +0200 [thread overview]
Message-ID: <20170620084255.GA13647@tuxteam.de> (raw)
In-Reply-To: <86tw3b9rvh.fsf@zoho.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Jun 20, 2017 at 06:59:14AM +0200, Emanuel Berg wrote:
> Kaushal Modi wrote:
>
> > Example: - How do I bind F1? - Do C-h k F1..
> > Realize that emacs shows that as <f1> -
> > Simply wrap that with (kbd "...") and you
> > have (kbd "<f1>") - Put that in the
> > global-set-key or define-key form.
>
> But that evaluates to [f1], so then why not
>
> (global-set-key [f1]
> (lambda () (interactive) (message "Formula 1")) )
But that evaluates to
(global-set-key [f1] #[nil "ÀÁ!" [message "Formula 1"] 2 nil nil])
(I just asked byte-compile to tell me that). So why not write that
right away?
Of course, that was a bit tongue-in-cheek ;-P
What I mean: sometimes it makes sense to let people go the
extra ten meters to meet the computer (mainly because there's
an interesting spot to meet [1]), sometimes it makes sense
to let the computer do the walk, perhaps because the spot to
meet is pretty boring (personally, I find conventions to name
keys pretty boring, to be honest).
Which is which depends, of course, on Things :)
[1] as is the case with lambda calculus and The Lisps.
Giving up on traditional infix arithmetic may feel
awkward at first, but tends to bring some kind of
Enlightenment upon (some of) us. Then we get high
and all worked up and try to convince others and
they look at us with those strange looks ;-D
Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAllI4A8ACgkQBcgs9XrR2kYAYwCeJOvUx7eh/rWAwKtRy5RzhjFX
FLEAniZYfQlEGmVL6IPBfuN5QKx4EyvY
=RO1E
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-06-20 8:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 19:28 introduction to lisp Jude DaShiell
2017-06-18 10:03 ` Emanuel Berg
2017-06-20 0:10 ` John Ankarström
2017-06-20 0:25 ` Kaushal Modi
2017-06-20 4:59 ` Emanuel Berg
2017-06-20 8:42 ` tomas [this message]
2017-06-20 9:04 ` Emanuel Berg
2017-06-20 10:41 ` tomas
2017-06-25 7:34 ` Narendra Joshi
2017-06-25 10:08 ` Footnotes [was: introduction to lisp] tomas
2017-06-20 12:29 ` introduction to lisp Kaushal Modi
2017-06-20 12:57 ` Emanuel Berg
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=20170620084255.GA13647@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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.
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).