From: Luca Ferrari <fluca1978@infinito.it>
To: Emanuel Berg <embe8573@student.uu.se>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: random color of variables in programming languages
Date: Thu, 12 Dec 2013 15:21:23 +0000 [thread overview]
Message-ID: <CAKoxK+5TOzim6KUx+2Ma0oGTfOuKoN8qZ7wnnH+TkkZNBXZt=Q@mail.gmail.com> (raw)
In-Reply-To: <87txefid7c.fsf@nl106-137-194.student.uu.se>
On Wed, Dec 11, 2013 at 4:06 PM, Emanuel Berg <embe8573@student.uu.se> wrote:
> I don't know. That seems like a cool idea though. Then
> you would see (i.e., not read) all the occurrences of
> that variable at once. However I don't know how it
> would work in practice.
I've used it within kdevelop and I have to say it takes a few to get
used to, but then it is really cool.
> If you were to put it up, I wouldn't recommend random
> colors, instead you could use the variable *name* (the
> letters) as function input to be mapped to colors: the
> first letter - the ASCII position, "normalized" - could
> be red, the second - same for green - etc.
>
Using the variable name is a good idea, even if names could easily
produce a clash.
However, any suggestion on where to start (in elisp code) for variable
font face?
Thanks,
Luca
next prev parent reply other threads:[~2013-12-12 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.8911.1386765750.10748.help-gnu-emacs@gnu.org>
2013-12-11 16:06 ` random color of variables in programming languages Emanuel Berg
2013-12-12 15:21 ` Luca Ferrari [this message]
[not found] ` <mailman.9022.1386861695.10748.help-gnu-emacs@gnu.org>
2013-12-12 21:05 ` Emanuel Berg
2013-12-20 1:36 ` Emanuel Berg
2013-12-23 14:51 ` Luca Ferrari
[not found] ` <mailman.10142.1387810292.10748.help-gnu-emacs@gnu.org>
2013-12-24 19:31 ` Emanuel Berg
2013-12-11 12:42 Luca Ferrari
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKoxK+5TOzim6KUx+2Ma0oGTfOuKoN8qZ7wnnH+TkkZNBXZt=Q@mail.gmail.com' \
--to=fluca1978@infinito.it \
--cc=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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.