unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Frank Fischer <frank.fischer@mathematik.tu-chemnitz.de>
Cc: 15155@debbugs.gnu.org
Subject: bug#15155: 24.3; wrap-prefix in adaptive-wrap-prefix-mode with variable-pitch has wrong face
Date: Wed, 21 Aug 2013 21:33:58 -0400	[thread overview]
Message-ID: <jwv4naimrzo.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ob8q4y67.fsf@mathematik.tu-chemnitz.de> (Frank Fischer's message of "Wed, 21 Aug 2013 21:54:40 +0200")

> Then make the X window small enough so that the lines in the *scratch*
> buffer wrap. The color of the wrap-prefix (i.e. the semicolons ;;) is
> black and seems fixed width instead of red and using variable-pitch
> font.  It seems as if the wrap-prefix does not inherit the face of the
> original (comment) prefix.  This becomes more apparent when adding
> whitespaces at the beginning of the first line. Then the indentation of
> the next (wrapped) lines will also increase, however by a different
> amount because of the different font.  I suppose the wrap-prefix somehow
> uses the global default font and not the font defined by variable-pitch.
> Note that this used to work in Emacs 23 (tested with 23.4.1) where the
> wrap-prefix in the successive lines has the same face as the original
> prefix.

I have the vague impression of having already seen such a bug-report,
except the other way around (where the user complained that the
wrap-prefix was displayed in the font that happened to be active where
the line got truncated), so we "fixed" it for Emacs-24.

At least that was within the redisplay engine.  So maybe the problem we
have now is that adaptive-wrap constructs the prefix without paying
attention to existing faces.


        Stefan





  reply	other threads:[~2013-08-22  1:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 19:54 bug#15155: 24.3; wrap-prefix in adaptive-wrap-prefix-mode with variable-pitch has wrong face Frank Fischer
2013-08-22  1:33 ` Stefan Monnier [this message]
2013-08-22  7:04   ` Frank Fischer
2013-08-22 14:54     ` Eli Zaretskii
2013-08-22 15:26       ` Frank Fischer
2013-08-22 16:03         ` Eli Zaretskii
2013-08-22 16:15           ` Frank Fischer
2013-08-22 16:56             ` Eli Zaretskii
2013-08-22 20:32               ` Frank Fischer
2013-08-23  6:41                 ` Eli Zaretskii
2013-08-23 13:17                   ` Frank Fischer
2013-08-23 14:29                     ` Eli Zaretskii
2013-08-23 15:17                       ` Frank Fischer
2013-08-23 15:38                     ` Stefan Monnier
2013-08-24  9:58                       ` Frank Fischer
2013-08-26  4:14                         ` Stefan Monnier
2013-08-23 15:39                     ` Stefan Monnier
2013-08-22 18:15       ` Stefan Monnier
2013-08-22 18:49         ` Eli Zaretskii
2013-08-22 14:50   ` 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

  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=jwv4naimrzo.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=15155@debbugs.gnu.org \
    --cc=frank.fischer@mathematik.tu-chemnitz.de \
    /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).