unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: <osv@javad.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 5679@debbugs.gnu.org
Subject: bug#5679: Emacs 23.1.93 pretest
Date: Thu, 04 Mar 2010 22:22:50 +0300	[thread overview]
Message-ID: <873a0f99it.fsf@osv.gnss.ru> (raw)
In-Reply-To: <87d3zk3qs4.fsf@stupidchicken.com> (Chong Yidong's message of "Thu, 04 Mar 2010 13:06:35 -0500")

Chong Yidong <cyd@stupidchicken.com> writes:

> <osv@javad.com> writes:
>
>> $ emacs -q --no-site-file
>> - Move cursor to the /ABSOLUTELY NO WARRANTY/ text in the splash
>>   screen
>> - M-x customize-face <ENTER> <ENTER>
>> - Change "Font Family:" to "terminus"
>> - Select "State|Set for Current Session"
>> - C-x b <ENTER> to return to splash screen, and
>>
>> /ABSOLUTELY NO WARRANTY/ looks like in the attached file.
>
> Fraid I still can't reproduce this.  One possibility I can think of is
> that the particular version of terminus you are using is buggy, and
> reports the right overhang incorrectly.  Strange...

Yeah, it's really strange. I see it on 2 different computers running
Debian stable and Debian testing. On both emacs23 gives this effect.
And the fact that emacs22 renders fine means that it's probably not font
issue, but maybe a problem of rendering library? What distribution do
you use?

In addition I've just checked that GNOME itself renders this font fine
both in its font selection dialog and in gnome-terminal, so the only
place where I can see the breakage is emacs run in X. Maybe to compile
emacs with some other options to isolate the cause of the problem?

BTW, emacs 23.1.1 only breaks rendering after I move cursor over the
text. If I, for examle, select the text (active region so it's
highlighted), the rendering becomes OK. Emacs 23.1.93 is more consistent
and always renders bad.

-- Sergei.






  reply	other threads:[~2010-03-04 19:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pr3rny7e.fsf@stupidchicken.com>
2010-03-04 14:36 ` bug#5679: Emacs 23.1.93 pretest Sergei Organov
2010-03-04 15:57   ` Chong Yidong
2010-03-04 17:43     ` osv
2010-03-04 18:06       ` Chong Yidong
2010-03-04 19:22         ` osv [this message]
2010-03-09  0:05           ` YAMAMOTO Mitsuharu
2010-03-09  9:57             ` osv
2010-03-09 11:30             ` osv
2010-03-10 11:19           ` YAMAMOTO Mitsuharu
2010-03-10 11:29             ` osv
2010-03-10 11:54               ` YAMAMOTO Mitsuharu
2010-03-10 12:12                 ` osv
2010-03-11  0:38                   ` YAMAMOTO Mitsuharu
2010-03-10  6:23         ` YAMAMOTO Mitsuharu
2010-03-10 10:05           ` osv

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=873a0f99it.fsf@osv.gnss.ru \
    --to=osv@javad.com \
    --cc=5679@debbugs.gnu.org \
    --cc=cyd@stupidchicken.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).