all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24925@debbugs.gnu.org
Subject: bug#24925: 25.1.50; Suboptimal explanation of FACESPEC in (elisp) Search-based Fontification
Date: Fri, 11 Nov 2016 18:06:27 +0100	[thread overview]
Message-ID: <87inrueyjw.fsf@web.de> (raw)
In-Reply-To: <83wpgac6om.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Nov 2016 18:39:05 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Date: Fri, 11 Nov 2016 17:20:38 +0100
> > 
> >      In this kind of element, FACESPEC is an expression whose value
> >      specifies the face to use for highlighting.  In the simplest case,
> >      FACESPEC is a Lisp variable (a symbol) whose value is a face name.
> > 
> > The first sentence is not good because an expression has no associated
> > value.
>
> ??? An expression certainly can have a value.

I really think that first sentence can be interpreted in different ways
when being read - see the rest of what I said.  Let's be more specific:
say that the expression is evaluated dynamically, and that the according
return value at that time is used. In contrast to having "a" value; like
evaluating only one time when the spec is added, or expecting the
expression to be constant.


Michael.





  reply	other threads:[~2016-11-11 17:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 16:20 bug#24925: 25.1.50; Suboptimal explanation of FACESPEC in (elisp) Search-based Fontification Michael Heerdegen
2016-11-11 16:39 ` Eli Zaretskii
2016-11-11 17:06   ` Michael Heerdegen [this message]
2016-11-11 17:57     ` Eli Zaretskii
2016-11-11 18:25       ` Michael Heerdegen
2016-11-11 19:08         ` Eli Zaretskii
2016-11-15  2:39           ` Michael Heerdegen

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=87inrueyjw.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=24925@debbugs.gnu.org \
    --cc=eliz@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.