unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Krovetz <bkrovetz@yahoo.com>
Cc: 24746@debbugs.gnu.org
Subject: bug#24746: parts of buffer become invisible
Date: Thu, 20 Oct 2016 22:06:57 +0300	[thread overview]
Message-ID: <83bmyeu9f2.fsf@gnu.org> (raw)
In-Reply-To: <992268478.569568.1476982654894@mail.yahoo.com> (message from Bob Krovetz on Thu, 20 Oct 2016 16:57:34 +0000 (UTC))

> Date: Thu, 20 Oct 2016 16:57:34 +0000 (UTC)
> From: Bob Krovetz <bkrovetz@yahoo.com>
> 
> I am using emacs 24.5.1 on Ubuntu 16.04. Sometimes parts of the buffer become invisible. For example, in
> the minibuffer the part that represents the command and partial argument can become invisible, such as c-x
> c-f failing to show "Find file: " and the directory string. In Perl I have found parts of the buffer that highlight
> different components such as variable names or programming language words might also become invisible,
> so the problem is not just about the minibuffer. The problem does not go away when using 'emacs -Q'. I used
> to use an older version of Ubuntu that is no longer supported, and the problem started appearing after I
> upgraded to 16.04.
> 
> Can you help me understand what is happening, and what I might do to debug it? I started looking at overlays
> and text properties, but I still don't understand them well enough. The characters can be seen when I
> backspace over them. I cannot predict when the problem will occur, and the current remedy is to exit emacs
> and start again.

Look at the settings of your video driver.  If there's some kind of
"optimization" features there, turn them off and see if that helps.





  reply	other threads:[~2016-10-20 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <992268478.569568.1476982654894.ref@mail.yahoo.com>
2016-10-20 16:57 ` bug#24746: parts of buffer become invisible Bob Krovetz
2016-10-20 19:06   ` Eli Zaretskii [this message]
2016-12-07 20:27     ` Glenn Morris

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=83bmyeu9f2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24746@debbugs.gnu.org \
    --cc=bkrovetz@yahoo.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).