unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Stephan Hennig <mailing_list@arcor.de>
Cc: emacs-devel@gnu.org
Subject: Re: linum and AUCTeX: line number face
Date: Mon, 17 Sep 2007 17:02:36 +0200	[thread overview]
Message-ID: <86tzpt5o8j.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <fcm15l$ib7$1@sea.gmane.org> (Stephan Hennig's message of "Mon\, 17 Sep 2007 15\:57\:02 +0200")

Stephan Hennig <mailing_list@arcor.de> writes:

> Stephen Berman schrieb:
>
>> If you customize the linum face to default, then all line numbers 
>> have the default face.  It seems the default face does not "inherit" 
>> the face properties of the string that the linum display property is 
>> on, whereas, for example, the shadow face, used by default by 
>> linum.el version 0.9n and later, does inherit at least some face 
>> properties or attributes.
>
> Thanks!  For \bfseries using default face works for all fonts I've
> tried.  But for \section commands the behaviour is even more strange.
>
> As long as default face refers to, e.g., 'Courier New' or 'Bitstream
> Vera Sans Mono' all seems to be well.  But when default refers to, e.g.,
> 'Outline-Consolas' or 'Lucida Sans Typewriter' weight is still inherited
> from line's face if there's a \section command in that line.
>
> To reproduce the problem, put the following lines into file .emacs:
>
> (progn (cd "~/elisp") (normal-top-level-add-subdirs-to-load-path))
> (require 'linum)
> (custom-set-faces
>   ;; custom-set-faces was added by Custom.
>   ;; If you edit it by hand, you could mess it up, so be careful.
>   ;; Your init file should contain only one such instance.
>   ;; If there is more than one, they won't work right.
>  '(default ((t (:stipple nil :background "SystemWindow" :foreground
> "SystemWindowText" :inverse-video nil :box nil :strike-through nil
> :overline nil :underline nil :slant normal :weight normal :height 108
> :width normal :family "Bitstream Vera Sans Mono"))))
>  '(linum ((t (:inherit default))))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

That is not the default face.

Try (copy-face 'default 'linum) or (put 'linum 'face-alias 'default instead).

Inheriting will, of course, be overridden by any new properties.
That's the whole point of it.

-- 
David Kastrup

  reply	other threads:[~2007-09-17 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46ea83d1$0$16117$9b4e6d93@newsspool1.arcor-online.net>
2007-09-16 10:30 ` linum and AUCTeX: line number face Stephan Hennig
2007-09-16 21:11   ` Stephen Berman
2007-09-17 13:57     ` Stephan Hennig
2007-09-17 15:02       ` David Kastrup [this message]
2007-09-17 16:20         ` Stefan Monnier
2007-09-17 22:54           ` Stephen Berman
2007-10-11 16:30             ` Stephan Hennig
2007-09-17 17:38         ` Stephan Hennig
2007-09-17 22:54           ` Stephen Berman
2007-09-18  9:51             ` Stephan Hennig
2007-09-17 22:54       ` Stephen Berman

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=86tzpt5o8j.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mailing_list@arcor.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).