From: Calixte Pernot <calixte.pernot@grenoble-inp.org>
To: Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Calixte Pernot <c@lixte.email>
Subject: Re: [PATCH v3] vt: add support for smput/rmput escape codes
Date: Wed, 10 Sep 2025 09:10:46 +0200 [thread overview]
Message-ID: <aff17665-36a5-42be-87d8-ca69ac167c8a@grenoble-inp.org> (raw)
In-Reply-To: <dbb5a124-4947-491e-8903-faa18e0e5bde@kernel.org>
Yep, I don't know what went wrong here.
I didn't see the commit you sent to fix this issue, so I tried to send a
new patch that fixes the issue, but I somehow sent the wrong patch. Sorry.
Thank you for your fix.
On 9/10/25 08:43, Jiri Slaby wrote:
> On 09. 09. 25, 22:26, Calixte Pernot wrote:
>> From: Calixte Pernot <c@lixte.email>
>>
>> Support "\e[?1049h" and "\e[?1049l" escape codes.
>> This patch allows programs to enter and leave alternate screens.
>> This feature is widely available in graphical terminal emulators and
>> mostly
>> used by fullscreen terminal-based user interfaces such as text editors.
>> Most editors such as vim and nano assume this escape code in not
>> supported
>> and will not try to print the escape sequence if TERM=linux.
>> To try out this patch, run `TERM=xterm-256color vim` inside a VT.
>>
>> Signed-off-by: Calixte Pernot <calixte.pernot@grenoble-inp.org>
>> ---
>> drivers/tty/vt/vt.c | 58 ++++++++++++++++++++++++++++++++++
>> include/linux/console_struct.h | 3 ++
>> 2 files changed, 61 insertions(+)
>>
>> diff --git a/drivers/tty/vt/vt.c b/drivers/tty/vt/vt.c
>> index 62049ceb3..d9e4eb3f0 100644
>> --- a/drivers/tty/vt/vt.c
>> +++ b/drivers/tty/vt/vt.c
>> @@ -141,6 +141,7 @@ static const struct consw
>> *con_driver_map[MAX_NR_CONSOLES];
>> static int con_open(struct tty_struct *, struct file *);
>> static void vc_init(struct vc_data *vc, int do_clear);
>> static void gotoxy(struct vc_data *vc, int new_x, int new_y);
>> +static void restore_cur(struct vc_data *vc);
>> static void save_cur(struct vc_data *vc);
>> static void reset_terminal(struct vc_data *vc, int do_clear);
>> static void con_flush_chars(struct tty_struct *tty);
>> @@ -1344,6 +1345,10 @@ struct vc_data *vc_deallocate(unsigned int
>> currcons)
>> kfree(vc->vc_screenbuf);
>> vc_cons[currcons].d = NULL;
>> }
>> + if (vc->vc_saved_screen != NULL) {
>> + kfree(vc->vc_saved_screen);
>> + vc->vc_saved_screen = NULL;
>> + }
>
> Yes, that's the bug. (I am not sure why are you sending this?)
>
> thanks,
next prev parent reply other threads:[~2025-09-10 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 19:15 Colin King (gmail)
2025-09-09 20:26 ` [PATCH v3] " Calixte Pernot
2025-09-10 6:43 ` Jiri Slaby
2025-09-10 7:10 ` Calixte Pernot [this message]
2025-09-10 6:41 ` Jiri Slaby
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=aff17665-36a5-42be-87d8-ca69ac167c8a@grenoble-inp.org \
--to=calixte.pernot@grenoble-inp.org \
--cc=c@lixte.email \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®