From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: [screenshot] Emacs instant colors (and the Elisp full cycle)
Date: Thu, 23 Apr 2015 02:51:10 +0200 [thread overview]
Message-ID: <87r3rbhdkx.fsf@debian.uxu> (raw)
In-Reply-To: c15b9fbb-c935-4812-abe4-1c1170efd612@googlegroups.com
Rusi <rustompmody@gmail.com> writes:
> When I visit it, it does not do all the colorfulness
> of your screenshot And cant load it because there're
> all sorts of your own requires out there.
You only need `font-lock-add-keywords'. If you read
the documentation, you find out that what I did is
exactly what it does! That way you also find out
I didn't do anything else and the requires are
unrelated. See?
> Anyways... 'seriously man'... fontlock technicolor
> is not my priority
It is rather to be able to solve simple problems by
examining code and documentation peace and quiet and
not get discouraged at the first unknown encounter.
But I like "fontlock technicolor" :) Exactly.
> So I am not going to iterate over this... unless you
> give me a version that splashes my screen with color
> when called as $ emacs -Q emanuel-buffer.el
OK:
http://user.it.uu.se/~embe8573/captain-mr-king.el
Invoke:
emacs -Q -l captain-mr-king.el captain-mr-king.el
> [Or as I said earlier you can put the demo on that
> python thread yourself]
Well, this isn't exactly an example of Lisp being
a "programmable programming language". This is an
example of Emacs being programmable in Elisp as well
as a tool to write Elisp. The difference might (?) get
subtile down below. The example that would prove the
point should rather be a macro that changes the syntax
of Lisp, for example `dotimes' - myself, I'm not
a macro writer tho I use them (sometimes). Of course
you may still use this example in any way you like.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-04-23 0:51 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
2015-04-22 2:52 ` Emanuel Berg
2015-04-22 3:06 ` Rusi
2015-04-23 0:51 ` Emanuel Berg [this message]
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=87r3rbhdkx.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).