unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Markus Triska <triska@metalevel.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	35005@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#35005: 27.0.50; Fontification unexpectedly works with anonymous faces
Date: Sat, 02 Nov 2019 10:10:27 +0100	[thread overview]
Message-ID: <87sgn6abjw.fsf__27028.0847953231$1572685885$gmane$org@metalevel.at> (raw)
In-Reply-To: <m25zs54mof.fsf@metalevel.at>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> OK, I'll adjust the text in the manual.  Names faces are preferable, but
> generating faces on the fly is sometimes necessary.

In my opinion, this issue is not resolved, please consider reopening it.

With the change that is now installed, the documentation reads:

   Many parts of Emacs require named faces, but some do not accept
   anonymous faces (e.g., the functions documented in @ref{Attribute
   Functions})

Where "require named faces" and "do not accept anonymous faces" amounts
to the same thing, so the wording seems not to be the intended one.

So in fact, the documentation now stresses further that named faces are
required, whereas the point of this issue is to document that anonymous
faces can be used for fontification. This still cannot be deduced from
the current manual. If that works, could you please document it?

Thank you and all the best,
Markus





  parent reply	other threads:[~2019-11-02  9:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 16:37 bug#35005: 27.0.50; Fontification unexpectedly works with anonymous faces Markus Triska
2019-03-28 16:14 ` Eli Zaretskii
2019-10-31 17:24   ` Lars Ingebrigtsen
2019-10-31 20:38     ` Stefan Monnier
2019-11-01 13:13       ` Lars Ingebrigtsen
     [not found]       ` <871rur4u4j.fsf@gnus.org>
2019-11-02  9:10         ` Markus Triska [this message]
     [not found]         ` <87sgn6abjw.fsf@metalevel.at>
2019-11-02 15:07           ` Lars Ingebrigtsen
     [not found]           ` <87mudee2pk.fsf@gnus.org>
2019-11-09 17:43             ` Markus Triska
     [not found]             ` <87y2wpndxs.fsf@metalevel.at>
2019-11-09 18:01               ` Stefan Monnier
     [not found]               ` <jwva795ue1u.fsf-monnier+emacs@gnu.org>
2019-11-09 20:02                 ` Lars Ingebrigtsen
     [not found]                 ` <87tv7czulh.fsf@gnus.org>
2019-11-09 21:02                   ` Markus Triska
     [not found]                   ` <87imnszrsx.fsf@metalevel.at>
2019-11-09 21:10                     ` Stefan Monnier
     [not found]                     ` <jwvd0e0u5f7.fsf-monnier+emacs@gnu.org>
2019-11-09 21:29                       ` Markus Triska
2019-11-14  9:00                       ` Eli Zaretskii
2019-11-10  1:52                     ` Drew Adams
2019-10-31 21:09     ` Markus Triska

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='87sgn6abjw.fsf__27028.0847953231$1572685885$gmane$org@metalevel.at' \
    --to=triska@metalevel.at \
    --cc=35005@debbugs.gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).