From: Chong Yidong <cyd@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: David Edmondson <dme@dme.org>,
10395@debbugs.gnu.org, Miles Bader <miles@gnu.org>
Subject: bug#10395: 24.0.92; line-prefix text inherits face properties from the preceding line rather than following text
Date: Thu, 22 Mar 2012 15:32:53 +0800 [thread overview]
Message-ID: <877gydrsyi.fsf@gnu.org> (raw)
In-Reply-To: <87ipkokm0e.fsf@gnu.org> (Chong Yidong's message of "Sat, 07 Jan 2012 15:30:25 +0800")
Chong Yidong <cyd@gnu.org> writes:
>> So my vote is to leave this as it works now, and maybe document this
>> to avoid surprises.
>
> Agreed about leaving this alone for now, though I'd rather not commit to
> documenting it as "the" behavior just yet.
>
> OTOH, the "expected" behavior would be for the line-prefix not to
> inherit face properties at all, much like overlay before-strings.
Whoops. Looks like there's a realistic situation in which this pops up,
and looks bad: Bug#4281. I committed a fix for that (revno 107654),
before remembering about the discussion in this thread and the decision
to leave it alone.
I guess I could revert the fix. But first, is there a work-around for
Bug#4281? The line prefix applied by org-indent-set-line-properties
does have an explicit `face' property, but that didn't seem to stop the
global-hl-line-mode highlighting from leaking into the prefix.
next prev parent reply other threads:[~2012-03-22 7:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-28 12:47 bug#10395: 24.0.92; line-prefix text inherits face properties from the preceding line rather than following text David Edmondson
2011-12-29 14:02 ` Eli Zaretskii
2011-12-31 14:09 ` Eli Zaretskii
2012-01-03 10:15 ` David Edmondson
2012-01-03 11:12 ` Eli Zaretskii
2012-01-07 7:30 ` Chong Yidong
2012-01-07 8:12 ` Eli Zaretskii
2012-03-22 7:32 ` Chong Yidong [this message]
2012-03-22 17:11 ` Eli Zaretskii
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=877gydrsyi.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=10395@debbugs.gnu.org \
--cc=dme@dme.org \
--cc=eliz@gnu.org \
--cc=miles@gnu.org \
/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.