From: Rusi <rustompmody@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [screenshot] Emacs instant colors (and the Elisp full cycle)
Date: Tue, 21 Apr 2015 19:24:48 -0700 (PDT) [thread overview]
Message-ID: <1d573ae0-bede-416b-987b-e1c973dafbee@googlegroups.com> (raw)
In-Reply-To: <87zj61w1h4.fsf@debian.uxu>
On Wednesday, April 22, 2015 at 4:04:22 AM UTC+5:30, Emanuel Berg wrote:
> Rusi writes:
>
> >> If you understand exactly what I mean, take a look
> >> at this screenshot to be even more confused:
> >>
> >> http://user.it.uu.se/~embe8573/pics/instant-colors.png
> >
> > Cute!
>
> Ain't it the truth!
>
> But it is also practical because often you do not
> remember what face is which color.
>
> For the purists, agreed, this is non-textbook usage
> because the thought is of course to set those faces to
> something sensible (sensible colors) *once*, and from
> that point use the faces semantically, to express
> purpose - the assumption being their color values make
> sense. However, it has happened to me many times that
> I do *not* use them that way but instead use them as
> mere (?) placeholders for face colors, and then it is
> very useful to just type the face name to see the
> color it represents.
>
> Besides, in principle it doesn't conflicts supposedly
> (?) proper usage to have them in cool colors, only
> then that is more a cool stunt rather than an
> advantage in productivity as well.
>
> > As it happens I was trying to illustrate/educate
> > folks on the python list on something very similar
> > about the nature and power of lisp:
> >
> > https://groups.google.com/d/msg/comp.lang.python/QF0-A1F4miw/GOHMu0HNZocJ
>
> Holly would if she could. If you have a non-JavaScript
> version of that I'll read it.
Thread starts here
https://mail.python.org/pipermail/python-list/2015-April/701924.html
BartC asks for switchable syntax:
https://mail.python.org/pipermail/python-list/2015-April/701998.html
Dan Sommers understands that "you want Lisp, the programmable programming language." : https://mail.python.org/pipermail/python-list/2015-April/702018.html
Subsequent would show that no one really understands what lisp is about
or even the possibility of 'switchable syntax'
>
> > If you tell me the underlying machinery, I'll point
> > them to it. [Or of course you can join that
> > conversation]
>
> You ask me to tell you so THEY will understand? :)
>
> Well, in the smallest possible picture, it is very
> simple. When the face names themselves are typed in
> a buffer, they appear in the same color as they would
> give the entities that are associated with them.
> This makes it is easier to set up such associations
> because you can see on the face name what the result
> will be.
>
> What this illustrates on a somewhat bigger scale is
> that Elisp is used to improve the tool which you use
> to write Elisp.
>
> On the biggest scale it is the computer exponential
> success story with computers and programmers taking
> turns making each other better. That is in principle
> equally true with bulky compiled languages (like C),
> however with Lisp (and not just this particular
> example) you can feel it instantly. It is a mighty
> realization, even for a might programmer.
>
> Did that make sense? Perhaps only to people who
> already understand it. Remember the words of
> Saint Morpheus: "Unfortunately, no one can be told
> what the Matrix is. You have to see it for yourself."
The broader picture(s) is fine; I was asking specifically about the fontlock
Is it vanilla FL or have you done something to make the name of the facename
have the color named?
Because it is exactly this kind of 'introspection' that that thread (non)understands
next prev parent reply other threads:[~2015-04-22 2:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 0:13 [screenshot] Emacs instant colors (and the Elisp full cycle) Emanuel Berg
2015-04-21 4:11 ` Rusi
2015-04-21 22:39 ` Emanuel Berg
2015-04-22 2:24 ` Rusi [this message]
2015-04-22 2:52 ` Emanuel Berg
2015-04-22 3:06 ` Rusi
2015-04-23 0:51 ` Emanuel Berg
2015-04-23 4:33 ` Rusi
2015-04-23 15:08 ` Emanuel Berg
2015-04-24 1:45 ` Rusi
2015-04-22 7:46 ` Marcin Borkowski
[not found] ` <mailman.1334.1429688786.904.help-gnu-emacs@gnu.org>
2015-04-22 11:52 ` Rusi
2015-04-23 1:08 ` Gnus, Emacs, and Emacs people blogs (was: Re: [screenshot] Emacs instant colors (and the Elisp full cycle)) Emanuel Berg
[not found] ` <87d22vhcrw.fsf_-_@debian.uxu>
2015-04-23 2:52 ` Emanuel Berg
2015-04-22 6:26 ` [screenshot] Emacs instant colors (and the Elisp full cycle) tomas
[not found] ` <mailman.1329.1429683980.904.help-gnu-emacs@gnu.org>
2015-04-23 3:07 ` Emanuel Berg
2015-04-23 6:46 ` tomas
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=1d573ae0-bede-416b-987b-e1c973dafbee@googlegroups.com \
--to=rustompmody@gmail.com \
--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).