public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: mintty emacs-nox pseudorandom color dimming
Date: Tue, 16 Jun 2020 11:22:57 +0200	[thread overview]
Message-ID: <7a8eccfc-7456-62eb-f63f-1dc212be559d@towo.net> (raw)
In-Reply-To: <1d8e1d03-c0a2-81e8-2f5c-b0f64ab52e89@alumni.cse.ucsc.edu>

Am 15.06.2020 um 22:47 schrieb Paul Ausbeck via Cygwin:
> Dear Sirs:
>
> After recently updating my cygwin installation, emacs-nox now 
> pseudorandomly dims some characters after the cursor passes through a 
> character's position. I don't think the problem lies with emacs-nox, 
> but rather with mintty. 
To support that claim you'd need to provide a clear symptom description 
and a reproducible test case.
You could make a screen log (not shot) or a reproducible command 
sequence to reveal the effect, then describe what you see and what you'd 
expect to see.
> I say this as the color dimming happens when one is using local 
> emacs-nox within a mintty or using remote emacs-nox after sshing 
> within a mintty.
>
> After I first discovered the dimming problem I noticed a separate 
> problem with the backspace key in ssh sessions. I then noticed that 
> there was yet another more recent mintty update, so I thought that I'd 
> try that. After applying that update, the backspace problem resolved 
> itself. However, the character dimming problem remains.
>
> Regards,
>
> Paul Ausbeck
> -- 
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple


      reply	other threads:[~2020-06-16  9:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 20:47 Paul Ausbeck
2020-06-16  9:22 ` Thomas Wolff [this message]

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=7a8eccfc-7456-62eb-f63f-1dc212be559d@towo.net \
    --to=towo@towo.net \
    --cc=cygwin@cygwin.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.
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).