From: Jakub Wilk <jwilk@jwilk.net>
To: Adam Borowski <kilobyte@angband.pl>
Cc: "Andrey Utkin" <andrey_utkin@fastmail.com>,
"Manuel Schölling" <manuel.schoelling@gmx.de>,
plagnioj@jcrosoft.com, tomi.valkeinen@ti.com, jslaby@suse.cz,
gregkh@linuxfoundation.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] console: Add persistent scrollback buffers for all VGA consoles
Date: Mon, 28 Nov 2016 00:30:01 +0100 [thread overview]
Message-ID: <20161127233001.aan5zndth7fmglhh@jwilk.net> (raw)
In-Reply-To: <20161127231548.GA29376@angband.pl>
* Adam Borowski <kilobyte@angband.pl>, 2016-11-28, 00:15:
>>clear(1) doesn't wipe the scrollback at all, it is still reachable, all of
>>it.
>
>It does for me on the console. The man page says:
>
># clear clears your screen if this is possible, including its scrollback
># buffer (if the extended "E3" capability is defined). clear looks in the
># environment for the terminal type and then in the terminfo database to
># determine how to clear the screen.
>
>Because of its reliance on terminfo, you need to have TERM=linux in your
>environment; also, screen/tmux obviously breaks this.
The "linux" terminfo entry didn't have E3 until very recently.
You will need ncurses >= 20160514.
--
Jakub Wilk
next prev parent reply other threads:[~2016-11-27 23:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161118005309.GC26324@dell-m4800.home>
2016-11-20 21:58 ` [PATCH v5 0/2] console: Add persistent scrollback buffers for all VGA console Manuel Schölling
2016-11-20 21:58 ` [PATCH v5 1/2] console: Move scrollback data into its own struct Manuel Schölling
2016-11-20 21:58 ` [PATCH v5 2/2] console: Add persistent scrollback buffers for all VGA consoles Manuel Schölling
2016-11-20 22:23 ` kbuild test robot
2016-11-21 20:17 ` Adam Borowski
2016-11-22 16:56 ` Manuel Schölling
2016-11-23 17:33 ` Adam Borowski
2016-11-27 16:51 ` [PATCH v7 0/3] " Manuel Schölling
2016-11-27 16:51 ` [PATCH v7 1/3] console: Move scrollback data into its own struct Manuel Schölling
2016-11-27 16:51 ` [PATCH v7 2/3] console: Add callback to flush scrollback buffer to consw struct Manuel Schölling
2016-11-27 16:51 ` [PATCH v7 3/3] console: Add persistent scrollback buffers for all VGA consoles Manuel Schölling
2016-11-27 21:37 ` [PATCH v7 0/3] " Andrey Utkin
2016-11-27 23:15 ` Adam Borowski
2016-11-27 23:30 ` Jakub Wilk [this message]
2016-11-28 0:02 ` Andrey Utkin
2016-11-28 21:28 ` Manuel Schölling
2016-11-29 10:01 ` Andrey Utkin
2016-11-29 10:44 ` Adam Borowski
2016-11-29 16:35 ` Manuel Schölling
2016-12-01 21:03 ` Manuel Schölling
2016-12-01 21:31 ` Andrey Utkin
2016-11-27 23:53 ` Adam Borowski
2016-11-28 21:23 ` Manuel Schölling
2016-11-23 17:33 ` [PATCH v5 2/2] " Manuel Schölling
2016-12-04 10:53 [PATCH v7 0/3] " Manuel Schölling
2016-12-06 10:02 ` Greg KH
2016-12-06 16:32 ` Manuel Schölling
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=20161127233001.aan5zndth7fmglhh@jwilk.net \
--to=jwilk@jwilk.net \
--cc=andrey_utkin@fastmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manuel.schoelling@gmx.de \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.com \
--subject='Re: [PATCH v7 0/3] console: Add persistent scrollback buffers for all VGA consoles' \
/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
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 NNTP newsgroup(s).