unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: irenezerafa <irenezerafa@protonmail.com>
Cc: 51715@debbugs.gnu.org
Subject: bug#51715: defface forms not having dynamic value
Date: Tue, 09 Nov 2021 15:26:48 +0200	[thread overview]
Message-ID: <83ee7p5ujr.fsf@gnu.org> (raw)
In-Reply-To: <4r0LmHf2yOM8ZtFlkSfgFoHOVu-qI0dwHhAlsf2WxQbn_V5qvtb4t_c7teGE7DqtW8tlI0DRo9pMo0lVCbz33QZni6U0oaIHog5YxKecn80=@protonmail.com> (bug-gnu-emacs@gnu.org)

> Date: Tue, 09 Nov 2021 11:41:10 +0000
> From:  irenezerafa via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I am getting into quite messy code because my macro creates
> defface forms.  Those do not have a dynamic value, but use the
> value they get at the time they are evaluated. So using something
> like a variable purple-intense does not help, because its value
> would be a reference to one value, not a function that returns a
> value (and having a function as a value would not be possible for
> a face).
> 
> Because the purpose of faces is to be configurable by the user,
> could there be some improvements to easily tackle such problems?

Please tell more.  Which face attributes did you want to make dynamic,
and how?





  reply	other threads:[~2021-11-09 13:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09 11:41 bug#51715: defface forms not having dynamic value irenezerafa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 13:26 ` Eli Zaretskii [this message]
2021-11-09 14:17   ` irenezerafa
2021-11-09 15:00     ` Eli Zaretskii
2021-11-09 15:36       ` irenezerafa
2021-11-09 15:40       ` irenezerafa
2021-11-10  0:36     ` Lars Ingebrigtsen
2021-11-10 15:08       ` Stefan Kangas
2021-11-10 16:48         ` Eli Zaretskii
2021-11-14  2:28           ` Lars Ingebrigtsen

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=83ee7p5ujr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51715@debbugs.gnu.org \
    --cc=irenezerafa@protonmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).