unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Miles' patch still fixes xfaces.c
Date: Tue, 27 May 2003 00:02:09 +0000 (UTC)	[thread overview]
Message-ID: <m19KRur-000IeBC@rattlesnake.com> (raw)
In-Reply-To: 200305262027.h4QKRtlO001787@rum.cs.yale.edu

The recent change to xfaces.c has not fixed the problem that
no one can permanently change
        :weight bold 
to
        :weight normal
in the variable `mode-line-buffer-identification', which is
buffer-local and in other places.

As far as I know, this problem resulted from a change on 19 Nov 2002
in mode-line-buffer-identification

(Several other bugs also appeared at the same time.)

Although the bug does not look too bad with a plain vanilla instance
of Emacs, with an `10x20' font, 
    -Misc-Fixed-Medium-R-Normal--20-200-75-75-C-100-ISO8859-1
the new bold creation technique fills in letters such as `m'
so that they become unreadable rectangles.

The word `Emacs' becomes unreadable.

Fortunately, Miles Bader posted a semi-fix on 18 Dec 2002.  This was a
`semi-fix' because his code sometimes led to a race condition and a
crash in Emacs.  But not very often.

Mile's patch is

    diff -u -r1.266 xfaces.c
    --- src/xfaces.c	17 Nov 2002 23:51:19 -0000	1.266
    +++ src/xfaces.c	18 Dec 2002 05:26:34 -0000

and works with the new version of xfaces.c, version 1.277 
(CVS from 2003 May 26 23:00 UTC)

However, it would be nice to see a clean fix to this problem, which is
to be able to specify any characteristic for `bold', including a
color, and including being able to set the weight of something that is
`bold' to `normal'.

The old messages are: 

    Bold by moving pixels problem
    starting on 20 Nov 2002

    signal handling bogosities
    starting on 19 Dec 2002

The patch is from 

    From: Miles Bader <miles@lsi.nec.co.jp>
    Subject: Re: Bold by moving pixels problem
    Date: 18 Dec 2002 19:01:01 +0900

Thanks!

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

  parent reply	other threads:[~2003-05-27  0:02 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 ` Robert J. Chassell [this message]
2003-05-27 22:40   ` Miles' patch still fixes xfaces.c Richard Stallman
2003-05-28  0:46     ` Robert J. Chassell
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=m19KRur-000IeBC@rattlesnake.com \
    --to=bob@rattlesnake.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).