unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ivor Durham" <ivor.durham@ivor.cc>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 25474@debbugs.gnu.org
Subject: bug#25474: 26.0.50; Buffer content invisible
Date: Wed, 18 Jan 2017 13:27:21 -0800	[thread overview]
Message-ID: <32012.9256732345$1505296773@news.gmane.org> (raw)
In-Reply-To: <831sw08bln.fsf@gnu.org>

Here is the output from M-X dump-glyph-matrix after invoking emacs -Q:

PT = 146, BEGV = 1. ZV = 146
Cursor x = 0, y = 54, hpos = 0, vpos = 3
=============================================
  0: (1) ''
  0: (1) ';; This buffer is for text that is not saved, and for Lisp
evaluation.[\n]'
  0: (1) ''
  1: (1) ''
  1: (1) ';; To create a file, visit it with C-x C-f and enter text in its
buffer.[\n]'
  1: (1) ''
  2: (1) ''
  2: (1) '[\n]'
  2: (1) ''
  3: (1) ''
  3: (1) '[\n]'
  3: (1) ''
  4: (1) ''
  4: (1) '[\n]'
  4: (1) ''
  5: (1) ''
  5: (1) '[\n]'
  5: (1) ''
  6: (1) ''
  6: (1) '[\n]'
  6: (1) ''
  7: (1) ''
  7: (1) '[\n]'
  7: (1) ''
  8: (1) ''
  8: (1) '[\n]'
  8: (1) ''
  9: (1) ''
  9: (1) '[\n]'
  9: (1) ''
 10: (1) ''
 10: (1) '[\n]'
 10: (1) ''
 11: (1) ''
 11: (1) '[\n]'
 11: (1) ''
 12: (1) ''
 12: (1) '[\n]'
 12: (1) ''
 13: (1) ''
 13: (1) '[\n]'
 13: (1) ''
 14: (1) ''
 14: (1) '[\n]'
 14: (1) ''
 15: (1) ''
 15: (1) '[\n]'
 15: (1) ''
 16: (1) ''
 16: (1) '[\n]'
 16: (1) ''
 17: (1) ''
 17: (1) '[\n]'
 17: (1) ''
 18: (1) ''
 18: (1) '[\n]'
 18: (1) ''
 19: (1) ''
 19: (1) '[\n]'
 19: (1) ''
 20: (1) ''
 20: (1) '[\n]'
 20: (1) ''
 21: (1) ''
 21: (1) '[\n]'
 21: (1) ''
 22: (1) ''
 22: (1) '[\n]'
 22: (1) ''
 23: (1) ''
 23: (1) '[\n]'
 23: (1) ''
 24: (1) ''
 24: (1) '[\n]'
 24: (1) ''
 25: (1) ''
 25: (1) '[\n]'
 25: (1) ''
 26: (1) ''
 26: (1) '[\n]'
 26: (1) ''
 27: (1) ''
 27: (1) '[\n]'
 27: (1) ''
 28: (1) ''
 28: (1) '[\n]'
 28: (1) ''
 29: (1) ''
 29: (1) '[\n]'
 29: (1) ''
 30: (1) ''
 30: (1) '[\n]'
 30: (1) ''
 31: (1) ''
 31: (1) '[\n]'
 31: (1) ''
 32: (1) ''
 32: (1) '[\n]'
 32: (1) ''
 33: (1) ''
 33: (1) '[\n]'
 33: (1) ''
 34: (0) ''
 34: (0) ''
 34: (0) ''
 35: (0) ''
 35: (0) ''
 35: (0) ''
 36: (0) ''
 36: (0) ''
 36: (0) ''
 37: (1) ''
 37: (1) ' U:---  *scratch*      All L4     (Lisp Interaction)
'
 37: (1) ''

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Wednesday, January 18, 2017 10:30 AM
To: Ivor Durham
Cc: 25474@debbugs.gnu.org
Subject: Re: bug#25474: 26.0.50; Buffer content invisible

> From: "Ivor Durham" <ivor.durham@ivor.cc>
> Cc: <25474@debbugs.gnu.org>
> Date: Wed, 18 Jan 2017 09:24:47 -0800
> 
> The cursor does not appear. If I click in the buffer area the cut and 
> copy icons highlight while the mouse is down.
> 
> "emacs -Q -bg blue -fg red" produces a blue background for the buffer 
> but no text appears in red when I type.
> 
> "emacs -Q -fn 8x12" reports "Font '8x12' is not defined". However, I 
> checked my .Xdefaults and it specifies "emacs*font" as "9x15". Using 
> "9x15" instead of "8x12" the window opens with the blank buffer area.

Can you reconfigure with --enable-checking='yes,glyphs', rebuild, and then
invoke "M-x dump-glyph-matrix RET" after starting Emacs from the shell
command line?  Please tell what does that show in the shell window.

Thanks.






  reply	other threads:[~2017-01-18 21:27 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01b001d27170$5730fdb0$0592f910$@durham@ivor.cc>
2017-01-18 15:33 ` bug#25474: 26.0.50; Buffer content invisible Eli Zaretskii
2017-01-18 16:04   ` Ivor Durham
     [not found]   ` <021001d271a4$9bb87ce0$d32976a0$@durham@ivor.cc>
2017-01-18 16:49     ` Eli Zaretskii
2017-01-18 17:24       ` Ivor Durham
     [not found]       ` <022401d271af$c4e0ad80$4ea20880$@durham@ivor.cc>
2017-01-18 18:30         ` Eli Zaretskii
2017-01-18 21:27           ` Ivor Durham [this message]
     [not found]           ` <004301d271d1$a802b920$f8082b60$@durham@ivor.cc>
2017-01-19  3:33             ` Eli Zaretskii
2017-01-19  5:03               ` Ivor Durham
     [not found]               ` <008301d27211$5043d940$f0cb8bc0$@durham@ivor.cc>
2017-01-19 15:51                 ` Eli Zaretskii
2017-01-19 15:57                   ` Ivor Durham
     [not found]                   ` <00ef01d2726c$cb5cb290$621617b0$@durham@ivor.cc>
2017-01-19 16:17                     ` Eli Zaretskii
2017-01-19 17:05                       ` Ivor Durham
     [not found]                       ` <00f901d27276$37170a90$a5451fb0$@durham@ivor.cc>
2017-01-20  7:51                         ` Eli Zaretskii
2017-01-20  8:02                           ` Ivor Durham
2017-01-20  9:07                           ` Daniel Colascione
2017-01-20 10:30                             ` Eli Zaretskii
2017-01-20 16:27                               ` Ivor Durham
2017-01-20 17:41                             ` martin rudalics
2017-01-20 17:42                               ` Daniel Colascione
2017-01-20 20:29                                 ` Ivor Durham
     [not found]                                 ` <024c01d2735b$dfee24b0$9fca6e10$@durham@ivor.cc>
2017-01-21 11:59                                   ` Eli Zaretskii
2017-01-21 13:20                                     ` martin rudalics
2017-01-21 15:44                                       ` Eli Zaretskii
2017-01-21 17:04                                         ` martin rudalics
2017-01-21 16:52                                       ` Ivor Durham
2017-09-02 12:49                                 ` Eli Zaretskii
2017-01-18  9:50 Ivor Durham

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='32012.9256732345$1505296773@news.gmane.org' \
    --to=ivor.durham@ivor.cc \
    --cc=25474@debbugs.gnu.org \
    --cc=eliz@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).