From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: How to customize an option to a dynamic value (computed by lisp form)
Date: Sat, 27 Aug 2016 13:50:58 +0200 [thread overview]
Message-ID: <20160827115058.GA20511@tuxteam.de> (raw)
In-Reply-To: <bd25d4be-3f7f-49d9-a973-179eb74ab375@default>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, Aug 26, 2016 at 01:59:00PM -0700, Drew Adams wrote:
> > > What does that mean? A variable has a single, static, literal value at
> > > any time.
>
> > https://en.wikipedia.org/wiki/Literal_(computer_programming)
>
> Which says:
>
> "In computer science, a literal is a _notation_ for _representing_
> a fixed value in source code."
I think you are talking past each other (i.e. both of you are right,
in a way :)
There are many "dynamic" options, at least in effect, as far as I
understand Jorge.
Of course, the option's *value* itself is expressed as a literal
and is static, but it is "something dynamic", like a function (think
hooks), an expression, a shell command to be called or some form
of "implicit expression" written in a custom mini-language (think
`c-offset-alist'.
The job of interpreting the option as dynamic lies with the "receiver"
of the option, i.e. with the function(s) *using* that option.
Typically wrapped in some function.
Does that help?
regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlfBfqIACgkQBcgs9XrR2kYfWgCeIdd6mMIZB/LfL7TX3NOnulX6
QRQAnirSlgGtsZM7Pe6s/m9sjeJLeSVm
=LpLJ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-08-27 11:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 20:26 How to customize an option to a dynamic value (computed by lisp form) Jorge
2016-08-24 17:50 ` Pascal J. Bourguignon
2016-08-25 17:55 ` Jorge
2016-08-25 20:54 ` Drew Adams
2016-08-26 12:54 ` Jorge
2016-08-26 13:26 ` Jorge
2016-08-26 14:28 ` Drew Adams
2016-08-26 19:02 ` Jorge
2016-08-26 20:18 ` Jorge
2016-08-26 20:59 ` Drew Adams
2016-08-27 11:50 ` tomas [this message]
2016-08-30 20:42 ` Jorge
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=20160827115058.GA20511@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).