From: Noam Postavsky <npostavs@gmail.com>
To: Sebastian Urban <mrsebastianurban@gmail.com>
Cc: 35044@debbugs.gnu.org
Subject: bug#35044: 25.2; Description of "disappearing" faces (Emacs Manual)
Date: Sat, 27 Apr 2019 17:20:58 -0400 [thread overview]
Message-ID: <87ftq3p2kl.fsf@gmail.com> (raw)
In-Reply-To: <af3547c0-e44d-ec80-0b25-fdd9de10c890@gmail.com> (Sebastian Urban's message of "Sat, 27 Apr 2019 17:55:55 +0200")
Sebastian Urban <mrsebastianurban@gmail.com> writes:
> To sum things up, approach for this bug won't be updating "Emacs
> manual", because it could end up as an excuse for bug(s), but rather:
>
> 1. updating "Elisp manual" with advice to use 'font-lock-face' over
> 'face' (which you already did with patch) - dev pov,
>
> 2. updating "table.el" to use 'font-lock-face' instead 'face' - user
> pov.
Yes.
> But won't it (especially point 2.) start a "face hunt", because there
> may be other functions/modes that have the same problem - using 'face'
> when they should use 'font-lock-face'... or should I just don't care
> until it happen?
Yes, it's quite possible that other functions/modes have the same
problem. But there's no need to specifically hunt them down (unless you
want to).
next prev parent reply other threads:[~2019-04-27 21:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 19:43 bug#35044: 25.2; Description of "disappearing" faces (Emacs Manual) Sebastian Urban
2019-04-16 21:33 ` Sebastian Urban
2019-04-17 12:59 ` Basil L. Contovounesios
2019-04-19 20:19 ` Sebastian Urban
2019-04-17 17:03 ` Eli Zaretskii
2019-04-17 22:37 ` Noam Postavsky
2019-04-18 2:34 ` Eli Zaretskii
2019-04-19 20:32 ` Sebastian Urban
2019-04-19 21:47 ` Noam Postavsky
2019-04-20 6:23 ` Eli Zaretskii
2019-04-22 20:03 ` Sebastian Urban
2019-04-22 20:59 ` Noam Postavsky
2019-04-24 22:01 ` Sebastian Urban
2019-04-26 12:49 ` Noam Postavsky
2019-04-27 15:55 ` Sebastian Urban
2019-04-27 21:20 ` Noam Postavsky [this message]
2019-04-28 21:17 ` Sebastian Urban
2019-04-28 21:22 ` Noam Postavsky
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=87ftq3p2kl.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35044@debbugs.gnu.org \
--cc=mrsebastianurban@gmail.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).