On Wed, 4 Sep 2019 21:36:28 -0600
Brian Inglis wrote:
> So how do you tell the pseudo-console to generate only text not escape
> sequences
> the recipient may not be prepared to deal with?
Unfortunately, no idea.
--
Takashi Yano
On 2019-09-04 19:13, Takashi Yano wrote:
> On Wed, 4 Sep 2019 11:22:42 -0600
> Brian Inglis wrote:
>> That output seems to be generated by a shell or program running in the pty.
>> If the recipient can not handle escape sequences, then the shell or program
>> in
>> the pty should be configured by
On Wed, 4 Sep 2019 11:22:42 -0600
Brian Inglis wrote:
> That output seems to be generated by a shell or program running in the pty.
> If the recipient can not handle escape sequences, then the shell or program in
> the pty should be configured by setting e.g. TERM=dumb when launching the
>
On 2019-09-03 21:45, Takashi Yano wrote:
> On Wed, 4 Sep 2019 12:34:31 +0900
> Takashi Yano wrote:
>> Attached is the raw output from pseudo console when the screen shows
>> the simple text below.
>>
>> from here
>> [yano@Express5800-S70 ~]$ cmd
>> Microsoft Windows [Version
On Wed, 4 Sep 2019 17:19:05 +0200
Corinna Vinschen wrote:
> > But the first check (the one in fixup_after_attach()) could be dropped,
> > couldn't it?
>
> IIUC the second test first checks for need_clear_screen but then the
> TERM might have changed in the meantime which in turn requires to
On Sep 4 15:11, Ken Brown wrote:
> On 9/4/2019 10:42 AM, Takashi Yano wrote:
> > On Wed, 4 Sep 2019 15:55:03 +0200
> > Corinna Vinschen wrote:
> >> The code in fixup_after_attach() is the only code snippet setting
> >> need_clear_screen = true. And that code also requires term != "dump" &&
> >>
On 9/4/2019 10:42 AM, Takashi Yano wrote:
> On Wed, 4 Sep 2019 15:55:03 +0200
> Corinna Vinschen wrote:
>> The code in fixup_after_attach() is the only code snippet setting
>> need_clear_screen = true. And that code also requires term != "dump" &&
>> term == "*emacs*" to set need_clear_screen.
>
On Wed, 4 Sep 2019 15:55:03 +0200
Corinna Vinschen wrote:
> The code in fixup_after_attach() is the only code snippet setting
> need_clear_screen = true. And that code also requires term != "dump" &&
> term == "*emacs*" to set need_clear_screen.
term != "*emacs*"
> The code in
On Sep 4 21:49, Takashi Yano wrote:
> On Wed, 4 Sep 2019 12:47:38 +0200
> Corinna Vinschen wrote:
> > Why do you check the TERMs again here? After all, need_clear_screen
> > is only true if one of these terms are used.
>
> Because, emacs seems to set environment TERM after fixup_after_exec()
>
On Wed, 4 Sep 2019 12:47:38 +0200
Corinna Vinschen wrote:
> Why do you check the TERMs again here? After all, need_clear_screen
> is only true if one of these terms are used.
Because, emacs seems to set environment TERM after fixup_after_exec()
is called. At the first check, TERM has the value
On Sep 4 10:46, Takashi Yano wrote:
> - Pseudo console support introduced by commit
> 169d65a5774acc76ce3f3feeedcbae7405aa9b57 shows garbage ^[[H^[[J in
> some of emacs screens. These screens do not handle ANSI escape
> sequences. Therefore, clear screen is disabled on these screens.
> ---
On Wed, 4 Sep 2019 12:34:31 +0900
Takashi Yano wrote:
> Attached is the raw output from pseudo console when the screen shows
> the simple text below.
>
> from here
> [yano@Express5800-S70 ~]$ cmd
> Microsoft Windows [Version 10.0.18362.329]
> (c) 2019 Microsoft Corporation. All rights
Hi Brian,
On Tue, 3 Sep 2019 20:47:14 -0600
Brian Inglis wrote:
> On 2019-09-03 19:46, Takashi Yano wrote:
> > - Pseudo console support introduced by commit
> > 169d65a5774acc76ce3f3feeedcbae7405aa9b57 shows garbage ^[[H^[[J in
> > some of emacs screens. These screens do not handle ANSI
On 2019-09-03 19:46, Takashi Yano wrote:
> - Pseudo console support introduced by commit
> 169d65a5774acc76ce3f3feeedcbae7405aa9b57 shows garbage ^[[H^[[J in
> some of emacs screens. These screens do not handle ANSI escape
> sequences. Therefore, clear screen is disabled on these screens.
14 matches
Mail list logo
