unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: Miles' patch still fixes xfaces.c
Date: Wed, 28 May 2003 00:46:17 +0000 (UTC)	[thread overview]
Message-ID: <m19Kp57-000IeGC@rattlesnake.com> (raw)
In-Reply-To: <E19Kn78-0004iY-6a@fencepost.gnu.org> (message from Richard Stallman on Tue, 27 May 2003 18:40:14 -0400)

   I don't remember the issue.  What does it mean to "permanently change"
   this?  And why can't you do it?  What happens if you try?

By "permanently change", I mean, put a change in my .emacs file that works.

The problem is that on my screen, some fonts display an unreadable
bold face when bold is set in the default manner.  A buffer list and
the mode line put some text in bold, the the problem is very
noticeable.

My solution is to change the `bold' weight to `normal' and to indicate
`bold' by changing the the color of the text.

The problem has been that the method of setting bold has been
hardwired at a low level, so it has been impossible to change the
font in my .emacs file.

In other words, by default `bold' is treated as a hard-wired command
to make the lines on a glyph wider.  It should be treated as the
equivalent of @strong in Texinfo, which indicates an argument that can
be displayed in various ways.

For example, I want to change  mode-line-buffer-identification
in my .emacs file by setting it like this:

    (setq
     mode-line-buffer-identification
     (quote
      (#("%14b" 0 4
         (face
          ;; (:weight bold)
          (:weight normal)
        ...

but that fails.  The buffer name still is unreadable because the lines
that make up the characters continue to be wider than usual.  The
buffer name is not changed to normal weight, unless I apply Miles'
fix.

The same happens with the buffer names in a buffer list.

   Can Miles explain what caused the problem?
   Maybe we can find a better fix based on that info.

I hope so.  He predicted that his fix would cause Emacs to crash
occasionally, and he was right, although crashes are rare.

-- 
    Robert J. Chassell                         Rattlesnake Enterprises
    http://www.rattlesnake.com                  GnuPG Key ID: 004B4AC8
    http://www.teak.cc                             bob@rattlesnake.com

  reply	other threads:[~2003-05-28  0:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-26 20:27 Printing elisp char literals Stefan Monnier
2003-05-26 20:49 ` David Kastrup
2003-05-27 10:39   ` Stephen J. Turnbull
2003-05-27  0:02 ` Miles' patch still fixes xfaces.c Robert J. Chassell
2003-05-27 22:40   ` Richard Stallman
2003-05-28  0:46     ` Robert J. Chassell [this message]
2003-05-31 19:52       ` Richard Stallman
2003-05-31 21:43         ` Robert J. Chassell

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=m19Kp57-000IeGC@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --cc=emacs-devel@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 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).