public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: Missing announcements for screen?
Date: Wed, 03 May 2017 03:23:00 -0000	[thread overview]
Message-ID: <4356c008-a378-12d0-7367-485f1a350c89@shaddybaddah.name> (raw)

Hi,

So I noticed my recent fresh install of Cygwin has screen 4.5.1-1
installed. And the most recent release is 4.5.2-1.

I've been afflicted by a screen bug that popped up some releases ago
say about 1.5 year ago. Basically, after detach, the restored screen
buffer is mildly corrupted. And the cursor ends up a line or two above
where it was (so it is in the middle of previous screen buffer output,
thus the corruption).

Previously, I tracked a problem with screen 
(https://sourceware.org/ml/cygwin/2014-05/msg00331.html)
and sadly I know how involved it is to track down issues, so I've been
just checking each new update to see if it resolves the issue described.

In any case, I didn't recall the updates for screen hitting my Inbox.
Looking at the mailing list, it appears to me that announcements have
not been forthcoming for screen, and perhaps other packages, for a
while:

https://sourceware.org/cgi-bin/search.cgi?cmd=Search!&fmt=long&form=extended&GroupBySite=no&m=all&ps=10&q=screen&sp=1&sy=1&type=&ul=/ml/cygwin-announce/%25&wf=0020&wm=wrd&s=DRP

Can someone confirm that? Is there a list of what's been fixed in each
release that I can look at ahead of installation?

-- 
Thanks in advance,
Shaddy

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2017-05-03  3:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03  3:23 Shaddy Baddah [this message]
2017-05-03  5:43 ` Marco Atzeri
2017-05-03 10:35 ` Andrew Schulman
2017-05-03 15:45   ` Nellis, Kenneth (Conduent)
2017-05-03 21:41     ` Erik Soderquist
2017-05-04 16:47       ` Andrew Schulman

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=4356c008-a378-12d0-7367-485f1a350c89@shaddybaddah.name \
    --to=lithium-cygwin@shaddybaddah.name \
    --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).