From: Eli Zaretskii <eliz@gnu.org>
To: "Ivor Durham" <ivor.durham@ivor.cc>
Cc: 25474@debbugs.gnu.org
Subject: bug#25474: 26.0.50; Buffer content invisible
Date: Wed, 18 Jan 2017 17:33:01 +0200 [thread overview]
Message-ID: <83inpc8jte.fsf@gnu.org> (raw)
In-Reply-To: <01b001d27170$5730fdb0$0592f910$@durham@ivor.cc> (ivor.durham@ivor.cc)
> From: "Ivor Durham" <ivor.durham@ivor.cc>
> Date: Wed, 18 Jan 2017 01:50:45 -0800
>
> After a fresh "git clone; autoconfig.sh; autoconfig.sh git; configure; make" sequence I have an Emacs that
> displays a menu bar and right-hand scroll bar but the actual buffer content is invisible. (See attached
> screenshot after opening my .bashrc file.) If I use the “-nw” option to avoid the window system, the buffer
> content is visible. I’m connecting to my Linux system via SecureCRT from my Windows 10 laptop which has
> VcXsrv running locally.
>
> The officially installed Emacs 25.1.1 displays the buffer content correctly which this new 26.0.50 build does
> not with the same Windows client connection.
Does Emacs respond to input? For example, if you move the mouse
pointer to hover above one of the tool-bar buttons and wait for a
second, does a tooltip pop up describing the button? And if you click
on a menu-bar item, do you see a menu drop down?
If the above produce no response, can you see if Emacs is consuming
CPU cycles?
Thanks.
next parent reply other threads:[~2017-01-18 15:33 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 ` Eli Zaretskii [this message]
2017-01-18 16:04 ` bug#25474: 26.0.50; Buffer content invisible 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
[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=83inpc8jte.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25474@debbugs.gnu.org \
--cc=ivor.durham@ivor.cc \
/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).