From: Sebastian Urban <mrsebastianurban@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 35044@debbugs.gnu.org
Subject: bug#35044: 25.2; Description of "disappearing" faces (Emacs Manual)
Date: Thu, 25 Apr 2019 00:01:16 +0200 [thread overview]
Message-ID: <91458fc2-3478-998d-f34d-ae2145d07936@gmail.com> (raw)
In-Reply-To: <87a7ghsqms.fsf@gmail.com>
> I'm unclear how this will help a beginner user. It sounds like
> it's describing a potential source of buggy behaviour.
Well this is why I didn't want to write it, also it's more like
concept/idea rather than a patch. Again new users should not be
surprised by this behaviour, so a line of warning would be nice, but
if it sounds like description of bug... Maybe a footnote "This is not
a bug!" at the end (yes, this is a joke).
> Not sure what you mean by "hardcoded" faces.
Quote (for example) RET character (C-q RET), then do 'describe-char'
on it and you'll get something like "hardcoded face: escape-glyph" in
the description.
---
About that change 'face -> 'font-lock-face in table.el, I would
probably need to report another bug/wishlist thing, am I correct?
S. U.
next prev parent reply other threads:[~2019-04-24 22:01 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 [this message]
2019-04-26 12:49 ` Noam Postavsky
2019-04-27 15:55 ` Sebastian Urban
2019-04-27 21:20 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=91458fc2-3478-998d-f34d-ae2145d07936@gmail.com \
--to=mrsebastianurban@gmail.com \
--cc=35044@debbugs.gnu.org \
--cc=npostavs@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 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.