Easy to see problem symptom: When running xinit, the full-screen window
has a white border.
I have an older machine with an "ASUS NVIDIA GeForce GTX 770" graphics card.
The problem was either with the NVIDIA Windows display driver or some
underlying Windows update. Fixing it was
When I ran xinit, I got the following events in the Windows event log:
Display driver nvlddmkm stopped responding and has successfully
recovered.
Kernel diagnostic event:
=
Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Kepler_3D, type
Fixes: 3721a756b0d8 ("Cygwin: console: Make the console accessible from other
terminals.")
Signed-off-by: Takashi Yano
---
winsup/cygwin/fhandler/pty.cc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/winsup/cygwin/fhandler/pty.cc b/winsup/cygwin/fhandler/pty.cc
index
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
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
On Aug 7 12:43, Cedric Blancher via Cygwin wrote:
> On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen
> wrote:
> >
> > On Aug 7 11:29, Cedric Blancher via Cygwin wrote:
> > > Forwarding to cygwin@cygwin.com
> > >
> > > Honestly I find it deeply concerning that a plain, unprivileged user
> > > can
On Mon, 7 Aug 2023 at 11:55, Corinna Vinschen wrote:
>
> On Aug 7 11:29, Cedric Blancher via Cygwin wrote:
> > Forwarding to cygwin@cygwin.com
> >
> > Honestly I find it deeply concerning that a plain, unprivileged user
> > can Bluescreen a machine, and more so that it happens during normal
> >
ge -
> From: Cedric Blancher
> Date: Sun, 6 Aug 2023 at 23:56
> Subject: Kernel stack trace for Winows 10 blue screen when running Cygwin?
> To:
>
>
> Good evening!
>
> How can we get a Windows kernel stack trace for a blue screen - aka
> Windows kernel crash?
stack trace for Winows 10 blue screen when running Cygwin?
To:
Good evening!
How can we get a Windows kernel stack trace for a blue screen - aka
Windows kernel crash?
We're experiencing regular blue screens when we run Cygwin git
operations for a large repository (~6GB of text files, sort
hello,
I did a cygwin installation on my employers laptop and have issues
with cygwin/X
Xwin with xfce starts and opens a window, but without any content. It
is only light grey and does not react on any mouse clicks.
The windows task manager however shows that Xwin/xfce is running and
that
screen 4.9.0-1 is now available in Cygwin. This release includes several
bug fixes, including for a possible denial of service by a crafted UTF-8
character sequence. Everyone is urged to upgrade to this release.
See the release announcement[1] and upstream changelog[2] for more details.
Screen
screen 4.9.0-1 is now available in Cygwin. This release includes several
bug fixes, including for a possible denial of service by a crafted UTF-8
character sequence. Everyone is urged to upgrade to this release.
See the release announcement[1] and upstream changelog[2] for more details.
Screen
On Thu, 6 May 2021 18:12:38 +0900
Takashi Yano via Cygwin> wrote:
> On Wed, 5 May 2021 15:07:04 +0200 (CEST)
> Johannes Schindelin wrote:
> > Hi,
> >
> > On Fri, 30 Apr 2021, Kevin Locke wrote:
> >
> > > On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> > > > On Fri, 30 Apr 2021 08:25:12
On Wed, 5 May 2021 15:07:04 +0200 (CEST)
Johannes Schindelin wrote:
> Hi,
>
> On Fri, 30 Apr 2021, Kevin Locke wrote:
>
> > On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> > > On Fri, 30 Apr 2021 08:25:12 -0600 Kevin Locke wrote:
> > >> I'm investigating an issue in Git for Windows[^1],
Hi,
On Fri, 30 Apr 2021, Kevin Locke wrote:
> On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> > On Fri, 30 Apr 2021 08:25:12 -0600 Kevin Locke wrote:
> >> I'm investigating an issue in Git for Windows[^1], which also affects
> >> Cygwin. The issue is that, when using CMD (i.e. Command
On Fri, Apr 30, 2021 at 1:31 PM Takashi Yano via Cygwin
wrote:
> Why on earth do you want to set TERM=cygwin?
> If you don't set TERM=cygwin, TERM is automatically set to
> xterm-256color, in which the issue does not occur.
>
Might be because for the longest time, if you didn't set it to
;> SetConsoleMode(ENABLE_VIRTUAL_TERMINAL_INPUT)[^3] to behave like
> >> xterm-256color when supported[^4] (they are not supported in "Legacy
> >> Console Mode").
> >>
> >> I'm not too familiar with TTY/PTY handling, much less Cygwin on top of
> >
like
xterm-256color when supported[^4] (they are not supported in "Legacy
Console Mode").
I'm not too familiar with TTY/PTY handling, much less Cygwin on top of
CMD. It's not clear to me if the alternate screen buffer behaves
differently in CMD than xterm, whether Cygwin has any responsibil
On Fri, 2021-04-30 at 23:53 +0900, Takashi Yano wrote:
> On Fri, 30 Apr 2021 08:25:12 -0600 Kevin Locke wrote:
>> I'm investigating an issue in Git for Windows[^1], which also affects
>> Cygwin. The issue is that, when using CMD (i.e. Command Prompt) on
>> Windows 10 1703 or above with "Legacy
e(ENABLE_VIRTUAL_TERMINAL_INPUT)[^3] to behave like
> xterm-256color when supported[^4] (they are not supported in "Legacy
> Console Mode").
>
> I'm not too familiar with TTY/PTY handling, much less Cygwin on top of
> CMD. It's not clear to me if the alternate scr
not too familiar with TTY/PTY handling, much less Cygwin on top of
CMD. It's not clear to me if the alternate screen buffer behaves
differently in CMD than xterm, whether Cygwin has any responsibility, or
if the issue is in how CMD handles ANSI escape sequences. Johannes
Schindelin suggested it may ma
On 6/3/2020 9:43 PM, Takashi Yano via Cygwin-patches wrote:
- Commit c4b060e3fe3bed05b3a69ccbcc20993ad85e163d seems to be not
enough. Moreover, it does not work as expected at all in Win10
1809. This patch essentially reverts that commit and add another
fix. After all, the cause of the
- Commit c4b060e3fe3bed05b3a69ccbcc20993ad85e163d seems to be not
enough. Moreover, it does not work as expected at all in Win10
1809. This patch essentially reverts that commit and add another
fix. After all, the cause of the problem was a race issue in
switch_to_pcon_out flag. That is,
On Wed, 3 Jun 2020 18:45:11 +0900
Takashi Yano wrote:
> - Commit c4b060e3fe3bed05b3a69ccbcc20993ad85e163d seems to be not
> enough. Moreover, it does not work as expected at all in Win10
> 1809. This patch essentially reverts that commit and add another
> fix. After all, the cause of the
- Commit c4b060e3fe3bed05b3a69ccbcc20993ad85e163d seems to be not
enough. Moreover, it does not work as expected at all in Win10
1809. This patch essentially reverts that commit and add another
fix. After all, the cause of the problem was a race issue in
switch_to_pcon_out flag. That is,
On Tue, 2 Jun 2020 21:44:40 +0900
Takashi Yano wrote:
> - Commit c4b060e3fe3bed05b3a69ccbcc20993ad85e163d seems to be not
> enough. Fixed again.
This patch does not work as expected in Win10 1809.
I will submit v2 patch which is more essential shortly.
--
Takashi Yano
C[?3h or ESC[?3l which clears console screen
buffer is pushed, set need_redraw_screen to trigger redraw screen. */
@@ -1504,6 +1504,15 @@ fhandler_pty_slave::write (const void *ptr, size_t len)
reset_switch_to_pcon ();
+ bool screen_alternated_orig = get_ttyp ()->screen_alternated
On Jun 1 15:21, Takashi Yano via Cygwin-patches wrote:
> Hi Corinna,
>
> On Mon, 1 Jun 2020 15:16:18 +0900
> Takashi Yano wrote:
> > - If the output of non-cygwin apps is browsed using less, screen is
> > ocasionally distorted after less exits. This frequently
Hi Corinna,
On Mon, 1 Jun 2020 15:16:18 +0900
Takashi Yano wrote:
> - If the output of non-cygwin apps is browsed using less, screen is
> ocasionally distorted after less exits. This frequently happens
> if cmd.exe is executed after less. This patch fixes the issue.
I have
- If the output of non-cygwin apps is browsed using less, screen is
ocasionally distorted after less exits. This frequently happens
if cmd.exe is executed after less. This patch fixes the issue.
---
winsup/cygwin/fhandler_tty.cc | 19 +++
1 file changed, 11 insertions(+), 8
> On Thu, 12 Mar 2020 19:01:41 -0700
> Wayne Davison wrote:
> > In recent Cygwin versions I've had gnu screen crash if the parent ssh
> > connection closes before an explicit disconnect is performed.
Thanks for reporting. I don't have any Cygwin hosts set up as ssh server
On Thu, 12 Mar 2020 19:01:41 -0700
Wayne Davison wrote:
> In recent Cygwin versions I've had gnu screen crash if the parent ssh
> connection closes before an explicit disconnect is performed. If an
> orderly screen disconnect happens first, future closed connections
> (after
In recent Cygwin versions I've had gnu screen crash if the parent ssh
connection closes before an explicit disconnect is performed. If an
orderly screen disconnect happens first, future closed connections
(after reconnecting to the screen session) no longer crash screen.
To reproduce:
I ssh
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=b0474b704aa0b0924da9b28d6310ccc1a55de675
commit b0474b704aa0b0924da9b28d6310ccc1a55de675
Author: Takashi Yano
Date: Sun Feb 9 23:46:01 2020 +0900
Cygwin: pty: Avoid screen distortion on slave read.
- Echo back print
yp ()->fwd_done, INFINITE);
}
+void
+fhandler_pty_slave::trigger_redraw_screen (void)
+{
+ /* Forcibly redraw screen based on console screen buffer. */
+ /* The following code triggers redrawing the screen. */
+ CONSOLE_SCREEN_BUFFER_INFO sbi;
+ GetConsoleScreenBufferInfo (get
screen 4.8.0-1 is now available in Cygwin. This release includes several
bug fixes, including a fix for a memory overwrite that could be a security
vulnerability. Everyone is urged to upgrade to this release.
See the release announcement[1] and upstream changelog[2] for more details.
Screen
screen 4.8.0-1 is now available in Cygwin. This release includes several
bug fixes, including a fix for a memory overwrite that could be a security
vulnerability. Everyone is urged to upgrade to this release.
See the release announcement[1] and upstream changelog[2] for more details.
Screen
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=1626569222066ee601f6c41b29efcc95202674b7
commit 1626569222066ee601f6c41b29efcc95202674b7
Author: Takashi Yano
Date: Wed Nov 13 19:49:29 2019 +0900
Cygwin: pty: Trigger redraw screen if ESC[?3h or ESC[?3l is sent
> and ESC[?3l ESC sequences are honored or not. The default is 'false'.
> >
> > However, if you specify the c132 resource, or if you start xterm
> > with the commandline option -132, it will resize when these sequences
> > are sent. And here's the joke: The r
is 'false'.
>
> However, if you specify the c132 resource, or if you start xterm
> with the commandline option -132, it will resize when these sequences
> are sent. And here's the joke: The resize also clears the screen
> in xterm.
Thanks for the information.
> My question now is, does th
On Nov 14 10:35, Corinna Vinschen wrote:
> Hi Takashi,
>
> On Nov 13 19:49, Takashi Yano wrote:
> > - Pseudo console clears console screen buffer if ESC[?3h or ESC[?3l
> > is sent. However, xterm/vt100 does not clear screen. This cause
Btw., this is not pseudo con
Hi Takashi,
On Nov 13 19:49, Takashi Yano wrote:
> - Pseudo console clears console screen buffer if ESC[?3h or ESC[?3l
> is sent. However, xterm/vt100 does not clear screen. This cause
This is only correct if xterm hasn't been started with the c132 widget
resource set to 'true'. This re
- Pseudo console clears console screen buffer if ESC[?3h or ESC[?3l
is sent. However, xterm/vt100 does not clear screen. This cause
mismatch between real screen and console screen buffer. Therefore,
this patch triggers redraw screen in that situation so that the
synchronization is done
On Wed, 13 Nov 2019 10:18:35 +0100
Corinna Vinschen wrote:
> On Nov 12 22:00, Takashi Yano wrote:
> > - Previously, pty cleared screen at startup for synchronization
> > between the real screen and console screen buffer for pseudo
> > console. With this patch, inste
On Nov 12 22:00, Takashi Yano wrote:
> - Previously, pty cleared screen at startup for synchronization
> between the real screen and console screen buffer for pseudo
> console. With this patch, instead of clearing screen, the screen
> is redrawn when the first native program
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=7ef4290a98edca60cfbab44327384f8ad6b471da
commit 7ef4290a98edca60cfbab44327384f8ad6b471da
Author: Takashi Yano
Date: Tue Nov 12 22:00:23 2019 +0900
Cygwin: pty: Use redraw screen instead of clear screen.
- Previously, pty
- Previously, pty cleared screen at startup for synchronization
between the real screen and console screen buffer for pseudo
console. With this patch, instead of clearing screen, the screen
is redrawn when the first native program is executed after pty
is created. In other words
Hi Corinna and Michael,
On Mon, 11 Nov 2019 11:04:54 +0100
Michael Haubenwallner wrote:
> On 11/11/19 10:17 AM, Corinna Vinschen wrote:
> > I tested it and I think this is a great step forward. Dropping
> > $TERM checks and clear screen sequence is the way to go!
>
> I
Hi Takashi,
On 11/11/19 10:17 AM, Corinna Vinschen wrote:
> On Nov 8 22:42, Takashi Yano wrote:
>> I came up with another alternative. How about the attached
>> patch? This forcibly redraws screen when the first native
>> program is executed after creating new pty (pseudo
> > In mine, too. This does not occur w/o running script.
> >
> > Any news here? Why does this only occur with script? Is that something
> > about reusing (or not reusing) the existing pseudo console?
>
> This does not occur only with script. If you run
> ssh localho
reusing (or not reusing) the existing pseudo console?
This does not occur only with script. If you run
ssh localhost
instead of script in step 3), it also happens.
This is because the console screen buffer is empty when pty
(pseudo console) is started. By executing cmd.exe, screen
is redrawn bas
Hi Takashi,
On Oct 24 15:33, Corinna Vinschen wrote:
> On Oct 24 19:17, Takashi Yano wrote:
> > On Thu, 24 Oct 2019 11:38:17 +0200
> > Corinna Vinschen wrote:
> > > Well, what I see when starting cmd.exe with this patch is a short
> > > flicker in the existing output in mintty, but the cursor
On Oct 24 19:17, Takashi Yano wrote:
> On Thu, 24 Oct 2019 11:38:17 +0200
> Corinna Vinschen wrote:
> > Well, what I see when starting cmd.exe with this patch is a short
> > flicker in the existing output in mintty, but the cursor position
> > stays the same. and cmd.exe output is where you'd
On Thu, 24 Oct 2019 11:38:17 +0200
Corinna Vinschen wrote:
> Well, what I see when starting cmd.exe with this patch is a short
> flicker in the existing output in mintty, but the cursor position
> stays the same. and cmd.exe output is where you'd expect it.
I mean:
1) start mintty
2) ps
3) script
On Oct 24 10:01, Takashi Yano wrote:
> Hi Corinna,
>
> On Wed, 23 Oct 2019 14:05:42 +0200
> Corinna Vinschen wrote:
> > In my limited testing it seems to work nicely.
>
> Isn't the screen contents before opening pty cleared when cmd.exe is
> executed?
Well, what
Hi Corinna,
On Wed, 23 Oct 2019 14:05:42 +0200
Corinna Vinschen wrote:
> In my limited testing it seems to work nicely.
Isn't the screen contents before opening pty cleared when cmd.exe is
executed?
Also Michael's test case probably does not work.
https://www.cygwin.com/ml/cygwin-patches/2
some python
>>> script
>>> using multiple pty.openpty() to spawn commands inside, to allow for herding
>>> all the subprocesses started by the commands (Ctrl-C or similar).
>
>> In terms of clearing the screen at all, what's your opinion, Michael?
>
> While I do
ef85b482 100644
> --- a/winsup/cygwin/tty.h
> +++ b/winsup/cygwin/tty.h
> @@ -106,6 +106,7 @@ private:
>int num_pcon_attached_slaves;
>UINT term_code_page;
>bool need_clear_screen;
> + bool need_clear_screen_on_write;
Maybe the name should be aligned to the fact that it doesn't clear the
screen anymore?
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
signature.asc
Description: PGP signature
On Tue, 22 Oct 2019 15:40:48 +0200
Corinna Vinschen wrote:
> Am I doing something wrong? This code crashes mintty on my
> installation. At start, a string of "6n6n6n6n..." appears and then
> mintty exits.
I cannot reproduce that How about this one?
--
Takashi Yano
rote:
> > > > > I confirmed the dwSize has right screen size and dwCursorPosition
> > > > > is (0,0) just after creating pty even though the cursor position
> > > > > in real screen is not at top left.
> > > > >
> > &
strstr (term, "emacs") &&
>>> + wcsstr (myself->progname, L"\\usr\\sbin\\sshd.exe"))
>> Again, my real problem does not utilize ssh at all, but is some python script
>> using multiple pty.openpty() to spawn commands inside, to allow for her
On Tue, 22 Oct 2019 10:02:42 +0200
Corinna Vinschen wrote:
> On Oct 22 16:23, Takashi Yano wrote:
> > On Tue, 22 Oct 2019 08:55:06 +0200
> > Corinna Vinschen wrote:
> > > On Oct 22 09:09, Takashi Yano wrote:
> > > > I confirmed the dwSize has right screen size
to quickly provide
> a test case with pty.openpty() combined with all the tty settings used there.
>
> I've started to extract the important bits, but that may take a while. OTOH,
> this is an open source project if you like to try yourself: prefix.gentoo.org
>
> Thanks!
> /haubi/
In terms of clearing the screen at all, what's your opinion, Michael?
Corinna
--
Corinna Vinschen
Cygwin Maintainer
signature.asc
Description: PGP signature
On Oct 22 16:23, Takashi Yano wrote:
> On Tue, 22 Oct 2019 08:55:06 +0200
> Corinna Vinschen wrote:
> > On Oct 22 09:09, Takashi Yano wrote:
> > > I confirmed the dwSize has right screen size and dwCursorPosition
> > > is (0,0) just after creating pty even though the
fter creating the pseudo console...
>
> To do this, it is necessary to log past data written to pty and
> push them into console screen buffer when pseudo console is started.
This does not make sence because ssh session may opened from other
systems than cygwin, i.e. Linux. In this case th
On Tue, 22 Oct 2019 08:55:06 +0200
Corinna Vinschen wrote:
> On Oct 22 09:09, Takashi Yano wrote:
> > I confirmed the dwSize has right screen size and dwCursorPosition
> > is (0,0) just after creating pty even though the cursor position
> > in real screen is not at top le
Hi Takashi,
On 10/18/19 1:37 PM, Takashi Yano wrote:
> ---
> winsup/cygwin/fhandler_tty.cc | 21 -
> winsup/cygwin/tty.cc | 1 +
> winsup/cygwin/tty.h | 1 +
> 3 files changed, 22 insertions(+), 1 deletion(-)
>
> diff --git
On Oct 22 09:09, Takashi Yano wrote:
> On Mon, 21 Oct 2019 11:43:56 +0200
> Corinna Vinschen wrote:
> > So it seems cmd.exe is the only (or one of few) native CLI tools
> > actually trying to manipulate the screen buffer. And what it does is
> > not so much clearing
On Mon, 21 Oct 2019 11:43:56 +0200
Corinna Vinschen wrote:
> So it seems cmd.exe is the only (or one of few) native CLI tools
> actually trying to manipulate the screen buffer. And what it does is
> not so much clearing the screen, but to align buffer line 1 with the top
> of the
On Oct 21 19:55, Takashi Yano wrote:
> On Mon, 21 Oct 2019 11:43:56 +0200
> Corinna Vinschen wrote:
> > So it seems cmd.exe is the only (or one of few) native CLI tools
> > actually trying to manipulate the screen buffer. And what it does is
> > not so much clearing
On Mon, 21 Oct 2019 19:55:15 +0900
Takashi Yano wrote:
> netsh is even worse. The cursor position will be broken by the follwing
> steps.
> 1) env TERM=dumb script
> 2) netsh
> 3) winhttp show proxy
wmic also has the cursor position problem.
1) env TERM=dumb script
2)
On Mon, 21 Oct 2019 11:43:56 +0200
Corinna Vinschen wrote:
> So it seems cmd.exe is the only (or one of few) native CLI tools
> actually trying to manipulate the screen buffer. And what it does is
> not so much clearing the screen, but to align buffer line 1 with the top
> of the
cygwin.com/ml/cygwin/2019-10/msg00074.html
> therefore, telnetd or rshd is not targeted.
>
> > Why exactly is the clear screen necessary? You wrote something about
> > synchronizing the pseudo console and the pseudo tty content, IIRC, but
> > it still seems artificial to enforce
---
winsup/cygwin/fhandler_tty.cc | 67 ++-
winsup/cygwin/tty.cc | 1 +
winsup/cygwin/tty.h | 1 +
3 files changed, 44 insertions(+), 25 deletions(-)
diff --git a/winsup/cygwin/fhandler_tty.cc b/winsup/cygwin/fhandler_tty.cc
index
method.
Now I have come up with another implementation. Could you please
have a look at v2 patch?
As a caution, this patch is for:
https://www.cygwin.com/ml/cygwin/2019-10/msg00074.html
therefore, telnetd or rshd is not targeted.
> Why exactly is the clear screen necessary? You wrote s
into
another directory, or just an sshd in the build dir during testing?
Is this workaround really necessary at all? Even basing this on the
terminal name looks pretty fragile.
Why exactly is the clear screen necessary? You wrote something about
synchronizing the pseudo console and the pseudo tty content
---
winsup/cygwin/fhandler_tty.cc | 21 -
winsup/cygwin/tty.cc | 1 +
winsup/cygwin/tty.h | 1 +
3 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/winsup/cygwin/fhandler_tty.cc b/winsup/cygwin/fhandler_tty.cc
index da6119dfb..163f93f35 100644
On Thu, 17 Oct 2019 16:36:25 +
Ken Brown wrote:
> Thanks. I'll go ahead and push both patches. And thanks, Takashi. (Or
> should
> I be addressing you as "Yano"? I'm ignorant about Japanese names.)
Takashi is the given name and Yano is the family name.
In Japan, we usualy use the order
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=43d7f33e2cab414a9f42a03b3347bc41e029dbbc
commit 43d7f33e2cab414a9f42a03b3347bc41e029dbbc
Author: Takashi Yano
Date: Wed Oct 16 21:34:09 2019 +0900
Cygwin: pty: Change the timing of clear screen.
Diff:
---
winsup/cygwin
On 10/17/2019 12:03 PM, Michael Haubenwallner wrote:
> On 10/17/19 4:55 PM, Ken Brown wrote:
>> On 10/16/2019 8:34 AM, Takashi Yano wrote:
>>> ---
>>>winsup/cygwin/fhandler_tty.cc | 26 +-
>>>1 file changed, 13 insertions(+), 13 deletions(-)
>>>
>>> diff --git
On 10/17/19 4:55 PM, Ken Brown wrote:
> On 10/16/2019 8:34 AM, Takashi Yano wrote:
>> ---
>> winsup/cygwin/fhandler_tty.cc | 26 +-
>> 1 file changed, 13 insertions(+), 13 deletions(-)
>>
>> diff --git a/winsup/cygwin/fhandler_tty.cc b/winsup/cygwin/fhandler_tty.cc
>>
---
winsup/cygwin/fhandler_tty.cc | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/winsup/cygwin/fhandler_tty.cc b/winsup/cygwin/fhandler_tty.cc
index 1095c82eb..baf3c9794 100644
--- a/winsup/cygwin/fhandler_tty.cc
+++
screen-4.7.0-1 is now available in Cygwin. This release includes lots of
small fixes and documentation improvements. See the upstream changelog[1]
for details.
This release also includes a small change to the default /etc/screenrc,
reported to fix a screen corruption problem for some users
screen-4.7.0-1 is now available in Cygwin. This release includes lots of
small fixes and documentation improvements. See the upstream changelog[1]
for details.
This release also includes a small change to the default /etc/screenrc,
reported to fix a screen corruption problem for some users
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=244f03627d37ea5ba642fc9a4b7c7b4a1a7be11d
commit 244f03627d37ea5ba642fc9a4b7c7b4a1a7be11d
Author: Takashi Yano
Date: Sun Sep 15 13:05:53 2019 +0900
Cygwin: pty: Change the timing of clearing screen.
- The code which
- The code which clears screen is moved from reset_switch_to_pcon()
to fixup_after_exec() because it seems not too early even at this
timing.
---
winsup/cygwin/fhandler_tty.cc | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/winsup/cygwin
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=bd31b7c5d54e26d3fb02946f1a88e97fa7379e3e
commit bd31b7c5d54e26d3fb02946f1a88e97fa7379e3e
Author: Takashi Yano
Date: Sun Sep 8 22:23:23 2019 +0900
Cygwin: pty: Fix screen alternation while pseudo console switching
- If screen alternated while pseudo console switching, it sometimes
failed. This might happen when the output of the non-cygwin program
is piped to less. The problem 3 reported in
https://cygwin.com/ml/cygwin-patches/2019-q3/msg00175.html
is probably due to this. This patch fixes
- If screen alternated while pseudo console switching, it sometimes
failed. This might happen when the output of the non-cygwin program
is piped to less. This patch fixes this issue.
---
winsup/cygwin/fhandler_tty.cc | 22 ++
1 file changed, 14 insertions(+), 8 deletions
On Sep 5 09:24, 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 t
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=433c6b8e0a667f9eae41a52efadec35ac62730df
commit 433c6b8e0a667f9eae41a52efadec35ac62730df
Author: Takashi Yano
Date: Thu Sep 5 09:24:26 2019 +0900
Cygwin: pty: Disable clear screen on new pty if TERM=dumb or emacs
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
>
- 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.
---
winsup/cygwin/fhandler_tty.cc | 19
- 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.
v2:
Remove check for TERM in fixup_after_attach
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 ~
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.
>
1 - 100 of 1150 matches
Mail list logo
