Re: gnu screen crashes on ssh disconnect

> 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 servers, so I'm not able to test

Re: gnu screen crashes on ssh disconnect

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 reconnecting to the scr

Re: Problem of login (Re: GNU screen and tmux cannot read tty input if they are started in a telnet session)

Hi Corinna, On Sat, 16 Mar 2019 16:34:41 +0100 Corinna Vinschen wrote: > Pushed and new release uploaded. I confirmed that the issue has been fixed in login 1.13-1. Thank you very much! -- Takashi Yano -- Problem reports: http://cygwin.com/problems.html FAQ: http://cyg

Re: Problem of login (Re: GNU screen and tmux cannot read tty input if they are started in a telnet session)

On Mar 16 22:06, Takashi Yano wrote: > Hi Corinna and Yaakov, > > I know you are busy, but could you please have a look? > > On Sun, 10 Mar 2019 15:05:48 +0900 Takashi Yano wrote: > > I try to clarify the title a little. > > > > On Sat, 9 Mar 2019 10:35:13 +0900 Takashi Yano wrote: > > > Hello,

Re: Problem of login (Re: GNU screen and tmux cannot read tty input if they are started in a telnet session)

Hi Corinna and Yaakov, I know you are busy, but could you please have a look? On Sun, 10 Mar 2019 15:05:48 +0900 Takashi Yano wrote: > I try to clarify the title a little. > > On Sat, 9 Mar 2019 10:35:13 +0900 Takashi Yano wrote: > > Hello, > > > > I would like to propose a patch attached for l

Problem of login (Re: GNU screen and tmux cannot read tty input if they are started in a telnet session)

I try to clarify the title a little. On Sat, 9 Mar 2019 10:35:13 +0900 Takashi Yano wrote: > Hello, > > I would like to propose a patch attached for login package. > > This fixes the issue that GNU screen and tmux cannot read tty input > if they are started in a telnet session. > > This issue i

Re: GNU screen trouble

Greetings, Andrey Repin! > # uname -a; screen --version; screen -admS mc-server-session > CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin > Screen version 4.05.01 (GNU) 25-Feb-17 > # screen -S mc-server-session -Q windows > > If I SEGV the hung child, there's a stacktrace,

Re: GNU screen trouble

Greetings, Andrey Repin! > Greetings, All! > # uname -a; screen --version; screen -admS mc-server-session > CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin > Screen version 4.05.01 (GNU) 25-Feb-17 > # screen -S mc-server-session -Q windows > Still same problem after today

Re: GNU screen trouble

Greetings, All! > # uname -a; screen --version; screen -admS mc-server-session > CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin > Screen version 4.05.01 (GNU) 25-Feb-17 > # screen -S mc-server-session -Q windows > > If I SEGV the hung child, there's a stacktrace, though I

Re: GNU screen trouble

> On Sat, May 27, 2017 at 4:27 AM, Andrey Repin wrote: > > # uname -a; screen --version; screen -admS mc-server-session > > CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin > > Screen version 4.05.01 (GNU) 25-Feb-17 > > > > # screen -S mc-server-session -Q windows > > > > I

Re: GNU screen trouble

On Sat, May 27, 2017 at 4:27 AM, Andrey Repin wrote: > # uname -a; screen --version; screen -admS mc-server-session > CYGWIN_NT-6.1 daemon2 2.8.0(0.309/5/3) 2017-04-01 20:47 x86_64 Cygwin > Screen version 4.05.01 (GNU) 25-Feb-17 > > # screen -S mc-server-session -Q windows > I see something simi

Re: GNU screen not seeing $SHELL env var?

On Wed 6/20/12 17:24 +0200 Corinna wrote: > On Jun 20 09:53, Tom Rodman wrote: > > On Wed 6/20/12 8:07 MDT Eric Blake wrote: > > > On 06/20/2012 07:20 AM, Tom Rodman wrote: > > > > > > > $ echo $SHELL > > > > /bin/bash > > > > $ bash -c 'echo SHELL: $SHELL' # does this prove SHELL is export

Re: GNU screen not seeing $SHELL env var?

On Jun 20 09:53, Tom Rodman wrote: > On Wed 6/20/12 8:07 MDT Eric Blake wrote: > > On 06/20/2012 07:20 AM, Tom Rodman wrote: > > > > > $ echo $SHELL > > > /bin/bash > > > $ bash -c 'echo SHELL: $SHELL' # does this prove SHELL is exported? > > > SHELL: /bin/bash > > > > No. And in fact,

Re: GNU screen not seeing $SHELL env var?

On Wed 6/20/12 8:07 MDT Eric Blake wrote: > On 06/20/2012 07:20 AM, Tom Rodman wrote: > > > $ echo $SHELL > > /bin/bash > > $ bash -c 'echo SHELL: $SHELL' # does this prove SHELL is exported? > > SHELL: /bin/bash > > No. And in fact, bash does not export SHELL by default, but defaults t

Re: GNU screen not seeing $SHELL env var?

On 06/20/2012 07:20 AM, Tom Rodman wrote: > $ echo $SHELL > /bin/bash > $ bash -c 'echo SHELL: $SHELL' # does this prove SHELL is exported? > SHELL: /bin/bash No. And in fact, bash does not export SHELL by default, but defaults to defining SHELL as a shell-local variable. You have to e

Re: GNU screen won't run; "chown tty: no such file or directory"

On 6/13/2011 9:03 PM, Larry Hall wrote: >On 6/13/2011 1:28 AM, Jeff Schenck wrote: > >>Hello, >> >>When trying to run screen, I get the following errors: >>"chown tty: No such file or directory" in the status bar, >>followed by "Sorry, could not find a PTY". Then it exits. >>I

Re: GNU screen not redrawing properly

> On 14 June 2011 13:12, Eric Pruitt wrote: > > Outside of screen, TERM=xterm. Inside of screen, well here is the relevant > > line from my bashrc; my screenrc doesn't have anything that would affect > > colors: > > > >    TERM=screen-256color GNU_SCREEN="active" screen -a -A -RR -T "$TERM" && \ >

Re: GNU screen not redrawing properly

On Tue, Jun 14, 2011 at 01:32:39PM +0100, Andy Koppe wrote: > Ah, this invokes screen itself with TERM=screen-256color, which tells > it to talk to the outside terminal as if that's another screen, which > is wrong. You want to be invoking it with TERM=xterm-256color instead > (which can be selecte

Re: GNU screen not redrawing properly

On 14 June 2011 13:12, Eric Pruitt wrote: > Outside of screen, TERM=xterm. Inside of screen, well here is the relevant > line from my bashrc; my screenrc doesn't have anything that would affect > colors: > >    TERM=screen-256color GNU_SCREEN="active" screen -a -A -RR -T "$TERM" && \ >        scree

Re: GNU screen not redrawing properly

On 14 June 2011 00:44, Eric Pruitt wrote: > On Mon, Jun 13, 2011 at 07:23:34PM -0400, Chris Sutcliffe wrote: >> On 13 June 2011 17:53, Eric Pruitt wrote: >> > When switching windows on GNU screen, the background on any unoccupied text >> > cells fails to be redrawn for curses applications; see >> >

Re: GNU screen won't run; "chown tty: no such file or directory"

On 6/13/2011 1:28 AM, Jeff Schenck wrote: Hello, When trying to run screen, I get the following errors: "chown tty: No such file or directory" in the status bar, followed by "Sorry, could not find a PTY". Then it exits. I get the same error in all terminal types I've tried -- rxvt-native, xter

Re: GNU screen not redrawing properly

On Mon, Jun 13, 2011 at 07:23:34PM -0400, Chris Sutcliffe wrote: > On 13 June 2011 17:53, Eric Pruitt wrote: > > When switching windows on GNU screen, the background on any unoccupied text > > cells fails to be redrawn for curses applications; see > > . I am using scre

Re: GNU screen not redrawing properly

On 13 June 2011 17:53, Eric Pruitt wrote: > When switching windows on GNU screen, the background on any unoccupied text > cells fails to be redrawn for curses applications; see > . I am using screen version 4.00.03, mutt > version 1.5.20, Vim 7.3, and mintty 0.9.9-1 on

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

> Hi Andrew and Corinna, > > Yep, something about FAT32 appears to be the problem. As Corinna correctly > notes, permissions are faked on FAT32. Doesn't matter what chmod I run, it's > all 644 or 755. Apparently, GNU screen does not like this, but apparently it > also doesn't give any error mes

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

Hi Andrew and Corinna, Yep, something about FAT32 appears to be the problem. As Corinna correctly notes, permissions are faked on FAT32. Doesn't matter what chmod I run, it's all 644 or 755. Apparently, GNU screen does not like this, but apparently it also doesn't give any error message that th

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On Wed, May 11, 2011 at 09:32:06PM +0200, Corinna Vinschen wrote: >On May 11 13:08, Edward McGuire wrote: >> On Wed, May 11, 2011 at 02:34, Corinna Vinschen wrote: >> > And you know, what have the romans ever done for us? >> >> ... apart from better sanitation and medicine and education and >> irr

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On May 11 13:08, Edward McGuire wrote: > On Wed, May 11, 2011 at 02:34, Corinna Vinschen wrote: > > And you know, what have the romans ever done for us? > > ... apart from better sanitation and medicine and education and > irrigation and public health and roads and a freshwater system and > baths

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On Wed, May 11, 2011 at 02:34, Corinna Vinschen wrote: > And you know, what have the romans ever done for us? ... apart from better sanitation and medicine and education and irrigation and public health and roads and a freshwater system and baths and public order ... -- Problem reports: htt

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

> On May 10 15:07, Andrew Schulman wrote: > > > a session that I detached on the same tty just seconds before. > > > > > > 3. chmod 666 on the socket file did not work (its permissions were > > > already 644, owned my 'morse', as shown in my original session long). > > > > No, I suggested that y

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On May 11 09:34, Corinna Vinschen wrote: > On May 10 15:07, Andrew Schulman wrote: > > > a session that I detached on the same tty just seconds before. > > > > > > 3. chmod 666 on the socket file did not work (its permissions were > > > already 644, owned my 'morse', as shown in my original sessi

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On May 10 15:07, Andrew Schulman wrote: > > a session that I detached on the same tty just seconds before. > > > > 3. chmod 666 on the socket file did not work (its permissions were > > already 644, owned my 'morse', as shown in my original session long). > > No, I suggested that you try 0600, o

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

> 1. Output of 'cygcheck -svr' appended to the end of this message. Thanks, looks okay. > 2. I have the problem whether I run GNU screen from a cmd.exe prompt or > under rxvt. I tried Peter Li's suggestion of trying to run screen under > mintty -- still no joy. It does not matter if I running

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

Hi, Andrew: Thanks for the help, and for pointing me to this cygwin list! 1. Output of 'cygcheck -svr' appended to the end of this message. 2. I have the problem whether I run GNU screen from a cmd.exe prompt or under rxvt. I tried Peter Li's suggestion of trying to run screen under mintty --

Re: Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

On 11:59 AM, Andrew Schulman wrote: * Read /usr/share/doc/screen/README.Cygwin - there are descriptions there of known problems with reattachment. But mostly it has to do with using screen in a DOS terminal. Any suggestions from other screen users? Based on my experience, I'd add mintt

Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try

Hi Doug. > Thanks so much for your efforts to port and maintain the GNU screen > program to Cygwin! I used to use screen all the in the pre-GUI days, > and now I use ssh regularly for the occasions I need to run something on > a real win32 or win64 platform. Being able to use screen again wo

Re: Re: GNU screen 4.0.3-1 -- Spawns a screen.exe cmd window when launched

The 1.7 beta works for me. Thank you. -- Joel Eidsath -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

Re: GNU screen 4.0.3-1 -- Spawns a screen.exe cmd window when launched

2009/9/14 Joel Eidsath: > When I launch screen by typing 'screen' at the basic Cygwin bash prompt, a > screen.exe cmd window launches and stays open for the entire screen session. > > I only see this behavior with Windows 7. Cygwin 1.7 has a workaround for the Windows 7 bug that causes this. It wo

Re: GNU screen hangs

On Thu, Sep 03, 2009 at 12:59:50AM -0400, Dave Steenburgh wrote: >On Wed, Sep 2, 2009 at 8:26 PM, Christopher Faylor wrote: >> On Wed, Sep 02, 2009 at 04:14:11PM -0400, Andrew Schulman wrote: >>>screen is difficult to debug, because it uses two communicating >>>processes, one in the foreground to t

Re: GNU screen hangs

On Wed, Sep 2, 2009 at 8:26 PM, Christopher Faylor wrote: > On Wed, Sep 02, 2009 at 04:14:11PM -0400, Andrew Schulman wrote: >>screen is difficult to debug, because it uses two communicating >>processes, one in the foreground to talk to your terminal, and one in >>the background to talk to the proc

Re: GNU screen hangs

On Wed, Sep 02, 2009 at 04:14:11PM -0400, Andrew Schulman wrote: >screen is difficult to debug, because it uses two communicating >processes, one in the foreground to talk to your terminal, and one in >the background to talk to the processes in each window. That's not that hard to debug. You just

Re: GNU screen hangs

> Andrew Schulman wrote: > > Personally, I much prefer PuTTYcyg. rxvt and MinTTY are also popular, but > > they both require X. You might also like Poderosa > > (http://en.poderosa.org/). > > Actually, neither rxvt nor MinTTY require X. I use them both without X > daily. I believe MinTTY is ac

Re: GNU screen hangs

Andrew Schulman wrote: > Personally, I much prefer PuTTYcyg. rxvt and MinTTY are also popular, but > they both require X. You might also like Poderosa > (http://en.poderosa.org/). Actually, neither rxvt nor MinTTY require X. I use them both without X daily. I believe MinTTY is actually based o

Re: GNU screen hangs

> I occasionally have trouble with screen as well, and as far as I can > tell, it always happens when trying to create a new screen.  (To be > clear, when I start screen the first time or when I press: ctrl-a c) > So, it may be that screen itself is not the problem in my case. > Because this occurs

Re: GNU screen hangs

On 09/02/2009 10:19 AM, Dave Steenburgh wrote: I should probably also point out that when I work with cygwin, I work almost exclusively with text-based programs. So, I rarely have a need for X, and I use a command prompt window. Is there a better terminal for those circumstances? There's alwa

Re: Sorry [Re: [OT] Re: GNU screen hangs]

On Wed, Sep 02, 2009 at 12:03:15PM +, TV wrote: >I'm feeling a bit bad how things got out of hand, and I'm sorry for it. >The etiquette of this list is unusually strict, I have never met >anything like it, and I don't understand it. The trigger-happy banning >behaviour really put me off the co

Re: Sorry [Re: [OT] Re: GNU screen hangs]

> I'm feeling a bit bad how things got out of hand, and I'm sorry > for it. Accepted. Andrew. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#un

Re: Sorry [Re: [OT] Re: GNU screen hangs]

TV wrote: > I'm feeling a bit bad how things got out of hand, and I'm sorry > for it. The etiquette of this list is unusually strict, I have > never met anything like it, and I don't understand it. The > trigger-happy banning behaviour really put me off the course. > This clearly isn't a place fo

Re: GNU screen hangs

/me returns to the original topic. I occasionally have trouble with screen as well, and as far as I can tell, it always happens when trying to create a new screen.  (To be clear, when I start screen the first time or when I press: ctrl-a c) So, it may be that screen itself is not the problem in my

Sorry [Re: [OT] Re: GNU screen hangs]

I'm feeling a bit bad how things got out of hand, and I'm sorry for it. The etiquette of this list is unusually strict, I have never met anything like it, and I don't understand it. The trigger-happy banning behaviour really put me off the course. This clearly isn't a place for me, so I'm going

Re: GNU screen hangs

Mark J. Reed wrote: Andrew DeFaria wrote: Excuse me, I'm off to the tongue tanning salon... Â ;-) Crazy Americans! Tanning one end while bleaching the other! What's going on in this country?! Here in America we treat both black and white equally! ;-) Now what was I supposed to be bleaching ag

Re: GNU screen hangs

Andrew DeFaria wrote: > Excuse me, I'm off to the tongue tanning salon...  ;-) Crazy Americans! Tanning one end while bleaching the other! What's going on in this country?! -- Mark J. Reed -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

Re: GNU screen hangs

Christopher Faylor wrote: > On Tue, Sep 01, 2009 at 07:12:51AM -0700, Andrew DeFaria wrote: >> TV wrote: >>> Oh, this is must be a cultural thing about americans and their tanned >>> tongues. >> Excuse me, I'm off to the tongue tanning salon... ;-) > > Ok. I've got to stop drinking coffee while

Re: GNU screen hangs

On Tue, Sep 01, 2009 at 07:12:51AM -0700, Andrew DeFaria wrote: >TV wrote: >>Oh, this is must be a cultural thing about americans and their tanned >>tongues. >Excuse me, I'm off to the tongue tanning salon... ;-) Ok. I've got to stop drinking coffee while reading the cygwin list... cgf -- Prob

Re: GNU screen hangs

TV wrote: Oh, this is must be a cultural thing about americans and their tanned tongues. Excuse me, I'm off to the tongue tanning salon... ;-) -- Andrew DeFaria The gene pool sure could use a little chlorine. -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: [OT] Re: GNU screen hangs

One more time wrote: > Ah, censorship. zOMG we is suppressing your freedumb of speach! O noes! Call for the WH-bulance! Seriously, that is the kind of pathetic nonsense spammers come out with. > You clearly read the messages through some anti-tuomov glasses, > as most of the FOSS herd

Re: [OT] Re: GNU screen hangs

Ah, censorship. The Official Truth will become the Truth, when the opposition is censored. On 2009-09-01, Dave Korn wrote: > Nonsense, it's got nothing to do with the way you say it, it's the content > of your message that nobody likes: self-regarding vanity, arrogance and > me-first egotism.

[OT] Re: GNU screen hangs

TV wrote: > On 2009-09-01, Dave Korn wrote: Wow. You kind of quoted my email address, but then you went and changed it into some poor innocent bystander's account. Whoever that is won't be pleased with you. < this space left blank for Tuomo to explain why that's the innocent bystander's fa

Re: GNU screen hangs

On Tue, Sep 01, 2009 at 10:23:58AM +, TV wrote: >On 2009-09-01, Dave Korn wrote: >>Don't kid yourself: it's you that's at fault, not the whole rest of the >>world. You've been rude and arrogant from your first post. > >Oh, this is must be a cultural thing about americans and their tanned >ton

Re: GNU screen hangs

On 2009-09-01, Dave Korn wrote: > Don't kid yourself: it's you that's at fault, not the whole rest of the > world. You've been rude and arrogant from your first post. Oh, this is must be a cultural thing about americans and their tanned tongues. Can't stay to the facts, have to make everyth

Re: GNU screen hangs

TV wrote: > On 2009-08-31, Christopher Faylor wrote: >> Apparently you don't know who I am. > > An even bigger pile of Don't kid yourself: it's you that's at fault, not the whole rest of the world. You've been rude and arrogant from your first post. It's certainly not just him who thinks so,

Re: GNU screen hangs

On 2009-08-31, Christopher Faylor wrote: > Apparently you don't know who I am. An even bigger pile of shit than this project. A project leader pretending to be an army sergeant with users rookies required to follow his ridiculous commands. I guess I'm going to complete my transition from Linux

Re: GNU screen hangs

On Mon, Aug 31, 2009 at 10:22:43PM +, Tuomo Valkonen wrote: >On 2009-08-31, Christopher Faylor wrote: >>It is very rude to ignore a request not to quote an email address. >>Please do not do this again. > >It's very rude to make such lame requests. What is it for? Spam? The >address is glarin

Re: GNU screen hangs

On 2009-08-31, Christopher Faylor wrote: > It is very rude to ignore a request not to quote an email address. > Please do not do this again. It's very rude to make such lame requests. What is it for? Spam? The address is glaring there bright in from-fields. Any archive software that obfuscates

Re: GNU screen hangs

On Mon, Aug 31, 2009 at 09:09:25PM +, Tuomo Valkonen wrote: >On 2009-08-31, Ken Brown wrote: >> That's an interesting response. Aren't you interested in trying to see >> if your problems are caused by BLODA? Is it too much trouble to disable >> or uninstall ZoneAlarm to see if that helps?

Re: GNU screen hangs

> On 2009-08-31, Ken Brown wrote: > > That's an interesting response. Aren't you interested in trying to see > > if your problems are caused by BLODA? Is it too much trouble to disable > > or uninstall ZoneAlarm to see if that helps? > > Don't have such a thing installed. Another firewall, th

Re: GNU screen hangs

On 2009-08-31, Ken Brown wrote: > That's an interesting response. Aren't you interested in trying to see > if your problems are caused by BLODA? Is it too much trouble to disable > or uninstall ZoneAlarm to see if that helps? Don't have such a thing installed. Another firewall, though. And I'

Re: GNU screen hangs

On 8/31/2009 2:28 PM, Tuomo Valkonen wrote: On 2009-08-31, Ken Brown wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR Have you ruled out BLODA? See All I can say is that things used to work fine until That's an interesting response. Aren't you interested in trying to see if your probl

Re: GNU screen hangs

On 2009-08-31, Tuomo Valkonen wrote: > On 2009-08-31, Ken Brown wrote: >> Have you ruled out BLODA? See > > All I can say is that things used to work fine until > a cygwin update less than a week ago, which did install > new cygwin dlls. After that I have had screen hang a > couple of times.

Re: GNU screen hangs

On 2009-08-31, Ken Brown wrote: > Have you ruled out BLODA? See All I can say is that things used to work fine until a cygwin update less than a week ago, which did install new cygwin dlls. After that I have had screen hang a couple of times. -- Tuomo -- Problem reports: http://cygw

Re: GNU screen hangs

On 8/31/2009 12:14 PM, Tuomo Valkonen wrote: Potential app conflicts: ZoneAlarm Personal Firewall Have you ruled out BLODA? See http://cygwin.com/faq/faq.using.html#faq.using.bloda Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/

Re: GNU screen hangs

On 2009-08-31, Andrew Schulman wrote: >> I don't know how to reproduce it. It just sometimes happens. > > What terminal are you using? Puttycyg, as I've already mentioned. -- Stop Gnomes and other pests! Purchase Windows today! http://iki.fi/tuomov/b/archives/2009/07/21/T17_26_09/ -- Prob

Re: GNU screen hangs

On 2009-08-31, Charles Wilson wrote: > If you can't send attachments using slrn, and this list specifically > requests that cygcheck results be sent as attachments, you had two choices: > > 1) deliberately send inline, ignoring list policy > 2) use a different email program for this one messag

Re: GNU screen hangs

Tuomo Valkonen wrote: > There. (No attachments: using slrn.) Great! Now, every time someone searches the cygwin archives for 'xrdb', they'll find your message. I'm sure that will be quite helpful. If you can't send attachments using slrn, and this list specifically requests that cygcheck results

Re: GNU screen hangs

> I don't know how to reproduce it. It just sometimes happens. What terminal are you using? Not DOS by any chance? /usr/share/doc/screen/README.Cygwin warns that if you're using a DOS terminal, you must set CYGWIN=tty before starting your terminal, or you'll have problems resuming screen sessions

Re: GNU screen hangs

On 2009-08-31, Andrew Schulman wrote: >> Cygwin (1.7 -- 1.5 is useless due to non-existent >> locale/UTF-8 support, although 1.7 doesn't shine in >> that either) was up to just a few weeks ago in a completely >> unusable state, because fg was broken, in addition to the >> X server, which has been

Re: GNU screen hangs

> Cygwin (1.7 -- 1.5 is useless due to non-existent > locale/UTF-8 support, although 1.7 doesn't shine in > that either) was up to just a few weeks ago in a completely > unusable state, because fg was broken, in addition to the > X server, which has been unreliable for a couple of months > now, cr

Re: default encoding (was: Re: GNU screen hangs)

Tuomo Valkonen: > I have LC_CTYPE=en_US.UTF-8, of course. And still Xlib fails. Oh well. Someone more knowledgeable about X will need to step in here. > I think the Python interpreter should call setlocale, > instead of having Python programs themselves do it, > because it is half-an-OS and does

Re: default encoding (was: Re: GNU screen hangs)

On 2009-08-30, Andy Koppe wrote: > If a locale is specified without an encoding, Cygwin 1.7 uses the > Windows system's default "ANSI" codepage, i.e. CP1252 or such like. > > Presumably X implements the encodings itself rather than use > setlocale(LC_CTYPE, "") and rely on the standard conversion

default encoding (was: Re: GNU screen hangs)

Tuomo Valkonen: > Firstly Xlib/libc communication seems to be > broken/unimplemented. This has frequently been a > problem on Linux too, Xlib not being aware of libc > locales. (Xlib usually won't work without the .encoding > part in LC_CTYPE, which frequently isn't there, as > libc seemingly can g

Re: GNU screen hangs

On 2009-08-29, Andy Koppe wrote: > 2009/8/29 Tuomo Valkonen: >> Cygwin (1.7 -- 1.5 is useless due to non-existent >> locale/UTF-8 support, although 1.7 doesn't shine in >> that either) > > Any specific problems regarding the latter? A couple. Firstly Xlib/libc communication seems to be broken/un

Re: GNU screen hangs

2009/8/29 Tuomo Valkonen: > Cygwin (1.7 -- 1.5 is useless due to non-existent > locale/UTF-8 support, although 1.7 doesn't shine in > that either) Any specific problems regarding the latter? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/f

Re: GNU screen doesn't initialize

> Since several days I try to debug GNU screen within Windows XP's cygwin > environment - without any success. I see the start screen, which reminds > me of the license stoff, skip that, and the Terminal-screen stays black. Marius, did you ever solve this problem? What terminal are you using: DO

Re: GNU screen doesn't initialize

> >> Since several days I try to debug GNU screen within Windows XP's cygwin > >> environment - without any success. I see the start screen, which reminds > >> me of the license stoff, skip that, and the Terminal-screen stays black. > > > > You mean completely black? No command prompt? Without a

Re: GNU screen doesn't initialize

Andrew Schulman wrote: >> Since several days I try to debug GNU screen within Windows XP's cygwin >> environment - without any success. I see the start screen, which reminds >> me of the license stoff, skip that, and the Terminal-screen stays black. > > You mean completely black? No command prom

Re: GNU screen doesn't initialize

> Since several days I try to debug GNU screen within Windows XP's cygwin > environment - without any success. I see the start screen, which reminds > me of the license stoff, skip that, and the Terminal-screen stays black. You mean completely black? No command prompt? Without any customization

Re: GNU screen doesn't initialize

* wishi (Thu, 02 Apr 2009 11:10:41 +0200) > Since several days I try to debug GNU screen within Windows XP's > cygwin environment - without any success. I see the start screen, > which reminds me of the license stoff, skip that, and the > Terminal-screen stays black. Yes, sure what do you expect?

Re: Gnu Screen

Antony Baxter wrote: > However, I just got back from holiday to discover that > the Screen > mailing list has closed down, with no explanation of > why that I could > find, and along with it the list archives have > vanished. Does anyone > know why, and/or where its replacement might be found? > A

Re: Gnu Screen

* Antony Baxter (2004-04-27 12:20 +0100) > Hello, > > Sorry if this is slightly off-topic for this mailing > list, but I've been > following with interest the progress of getting Gnu > Screen (1) to work > 100% under Cygwin, on the Screen mailing list (2). > When I last tried it, > everything w

Re: GNU Screen

I wrote: > 1- Midnight Commander won't run the subshell: > http://mail.gnome.org/archives/mc/2003-January/msg00071.html > 2- caption always / sorendition corrupt the colors you set > for the terminal. I use black on white. I can reproduce it > setting caption always "%Y%m%d (%D) %0c:%s". See > ht

Re: GNU Screen

I wrote: > 2- caption always / sorendition corrupt the colors you set > for the terminal. I use black on white. I can reproduce it > setting caption always "%Y%m%d (%D) %0c:%s". See > http://www.pervalidus.net/screen-cygwin-caption.png I don't even need to use caption always / sorendition. The co

Re: GNU Screen

Igor Pechtchanski wrote: > I've been able to compile screen-3.9.13 before with the > attached patch. Me too, with the same options I use on Linux: --enable-locale --enable-telnet --enable-colors256 --enable-rxvt_osc --with-sys-screenrc=/etc/screenrc and found 2 problems. 1- Midnight Commander w

Re: GNU Screen

Jurgen, I've been able to compile screen-3.9.13 before with the attached patch. I didn't test the resulting binary too much, though. Just compiled the whole thing again today (with gcc 3.2) by untarring the source tarball, then $ patch -p0 < screen-3.9.13-cygwin.patch $ autoconf $ configure $ ma

Re: GNU Screen

Hello, Brian and list, I am running screen 3.9.8. It seems that I was able to compile it under a previous version of Cygwin, but alas since 1.3.12 not anymore. I am still using this previously compiled binary. FWIW, I just tried to compile screen and I get the following error in the screen source