From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Cc: 36858@debbugs.gnu.org, spacibba@aol.com, rotim.davor@gmail.com,
mail@nicolasgoaziou.fr
Subject: bug#36858: 27.0.50; display bugs with display-fill-column-indicator-mode
Date: Sat, 10 Aug 2019 09:15:02 -0700 (PDT) [thread overview]
Message-ID: <c35f1ac1-30ab-4366-89ad-2c23af289d24@default> (raw)
In-Reply-To: <<83a7ch87j8.fsf@gnu.org>>
Not really intending to jump in here, but I
wonder if an enhancement like one of these
would be possible/useful. No idea whether
this really makes sense or is relevant to
this thread - just thinking out loud.
* Add a :set keyword for `defface'.
* Add an optional SET-FUNCTION arg to
`face-spec-set'. It would be invoked just
after the face gets set to SPEC.
Presumably, with something like that, code
could specify, for a given face, that setting
its attributes in certain ways would entail
performing some additional action.
For example, if background is set, without
also underlining (example - not limited to
this case), then the face would not be
applied to an eol char.
---
Otherwise, isn't it possible for the Org
code to check the face attributes and act
accordingly wrt the eol char?
Yes, this is a more general issue than just
for Org. That's why I was thinking of
something like the suggestion above: have
face-setting let you know what the current
case is (e.g. have it set a variable, which
you can test).
next parent reply other threads:[~2019-08-10 16:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<CAMWA6ANTAsSz4ckRGSTuVRCHJKZMDEd1SsBaJetW3bWRjPTRNQ@mail.gmail.com>
[not found] ` <<83zhkh8m5n.fsf@gnu.org>
[not found] ` <<CAMWA6AMvD5Vt=fDcHjufcrVUPy__tQ00tk9aobYjyrgoaSiF=w@mail.gmail.com>
[not found] ` <<83mugh8hqg.fsf@gnu.org>
[not found] ` <<CAMWA6ANXJvdCptHYV_qzXuwtfdoXM3Ygo577gPorgLRD1EQAJw@mail.gmail.com>
[not found] ` <<83imr58fji.fsf@gnu.org>
[not found] ` <<83d0hd8ceh.fsf@gnu.org>
[not found] ` <<CADn3Z2Ke4S+BCaniLWYxT3Vf6-gqt-oHCqcHj6rz22tG0ntw8g@mail.gmail.com>
[not found] ` <<83a7ch87j8.fsf@gnu.org>
2019-08-10 16:15 ` Drew Adams [this message]
2019-07-30 18:11 bug#36858: 27.0.50; display bugs with display-fill-column-indicator-mode Davor Rotim
2019-08-02 9:16 ` Eli Zaretskii
2019-08-02 10:25 ` Ergus
2019-08-02 11:53 ` Eli Zaretskii
2019-08-05 23:54 ` Ergus
2019-08-05 15:27 ` Ergus
2019-08-07 14:38 ` Eli Zaretskii
2019-08-07 16:20 ` Ergus
2019-08-07 16:37 ` Eli Zaretskii
2019-08-07 17:06 ` Ergus
2019-08-07 17:29 ` Eli Zaretskii
2019-08-07 19:46 ` Ergus
2019-08-08 7:17 ` Ergus
2019-08-08 17:33 ` Eli Zaretskii
2019-08-08 22:29 ` Ergus
2019-08-08 17:31 ` Eli Zaretskii
2019-08-08 22:32 ` Ergus
2019-08-06 10:44 ` Dmitry Gutov
2019-08-10 8:22 ` Eli Zaretskii
2019-08-10 8:35 ` Davor Rotim
2019-08-10 9:58 ` Eli Zaretskii
2019-08-10 10:12 ` Davor Rotim
2019-08-10 10:45 ` Eli Zaretskii
2019-08-10 11:53 ` Eli Zaretskii
2019-08-10 13:21 ` Carsten Dominik
2019-08-10 13:38 ` Eli Zaretskii
2019-08-10 14:17 ` Carsten Dominik
2019-08-10 14:41 ` Eli Zaretskii
2019-08-12 7:10 ` Carsten Dominik
2019-08-12 14:26 ` Eli Zaretskii
2019-08-10 18:02 ` Ergus
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=c35f1ac1-30ab-4366-89ad-2c23af289d24@default \
--to=drew.adams@oracle.com \
--cc=36858@debbugs.gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=eliz@gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=rotim.davor@gmail.com \
--cc=spacibba@aol.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).