all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: DJC <djc@resiak.org>
Cc: 35158@debbugs.gnu.org
Subject: bug#35158: 26.1; Display bugs: odd bits wrong in shell window
Date: Fri, 05 Apr 2019 17:36:10 +0300	[thread overview]
Message-ID: <83tvfcbjtx.fsf@gnu.org> (raw)
In-Reply-To: <f6483883-e76d-885d-d63c-6121c3a40ed6@resiak.org> (message from DJC on Fri, 5 Apr 2019 16:13:24 +0200)

> From: DJC <djc@resiak.org>
> Date: Fri, 5 Apr 2019 16:13:24 +0200
> 
> In the upper window of a frame I had several hundred lines containing the 
> full paths of filenames within quotation marks -- all containing non-ASCII 
> accented European characters -- and in the lower window a Windows shell. 
>  From the shell window I used a macro to change windows, grab a file name, 
> then return to the shell window and issue
> 
>      del {filename within quotation marks}
> 
> After confirming that this was working as desired, I issued a command to 
> repeat the macro indefinitely.  As lines scrolled in the shell window I 
> remarked some errors in the display there: certain improper bits were being 
> displayed rather consistently.  When the run was finished, I grabbed a 
> screen shot of the quiescent state (attached) showing some of these. 

You mean, those stray pixels after "5" in "HS2015"?  And also the
artifacts before the backslashes in last two lines you captured?

If so, I suggest to review the settings of your display driver, and if
there are any "optimization" options there, turn them off.

Thanks.





  reply	other threads:[~2019-04-05 14:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 14:13 bug#35158: 26.1; Display bugs: odd bits wrong in shell window DJC
2019-04-05 14:36 ` Eli Zaretskii [this message]
2019-04-05 15:16   ` DJC
2019-04-05 15:30     ` Eli Zaretskii
2020-05-03 23:32       ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83tvfcbjtx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35158@debbugs.gnu.org \
    --cc=djc@resiak.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.