From: Andrew Schulman via Cygwin-announce <cygwin-announce@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] screen 4.9.1-1
Date: Sun, 27 Aug 2023 12:52:10 -0400 [thread overview]
Message-ID: <announce.CAJOCpN3SqQgrXy1w8BzZSugs1Apds1vc3p3TpEtjHkxTdYwVbw@mail.gmail.com> (raw)
screen 4.9.1-1 is now available in Cygwin. This release includes bug fixes
and documentation updates. See the release announcement[1] and upstream
changelog[2] for more details.
Screen is a full-screen window manager that multiplexes a physical terminal
between several processes, typically interactive shells. Each virtual
terminal provides the functions of the DEC VT100 terminal and, in addition,
several control functions from the ANSI X3.64 (ISO 6429) and ISO 2022
standards (e.g., insert/delete line and support for multiple character
sets). There is a scrollback history buffer for each virtual terminal and a
copy-and-paste mechanism that allows the user to move text regions between
windows. When screen is called, it creates a single window with a shell in
it (or the specified command) and then gets out of your way so that you can
use the program as you normally would. Then, at any time, you can create
new (full-screen) windows with other programs in them (including more
shells), kill the current window, view a list of the active windows, turn
output logging on and off, copy text between windows, view the scrollback
history, switch between windows, etc. All windows run their programs
completely independent of each other. Programs continue to run when their
window is currently not visible and even when the whole screen session is
detached from the user's terminal.
Andrew E. Schulman
[1] https://savannah.gnu.org/news/?id=10500
[2] https://git.savannah.gnu.org/cgit/screen.git/log/?h=v.4.9.1
reply other threads:[~2023-08-27 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=announce.CAJOCpN3SqQgrXy1w8BzZSugs1Apds1vc3p3TpEtjHkxTdYwVbw@mail.gmail.com \
--to=cygwin-announce@cygwin.com \
--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).