Is there some reason why setup-1.7 has to blow up to full-screen when
the Select Packages screen comes up? I prefer the friendlier 1.5
version.
- Jim
--
Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us
--
Problem reports: http://cygwin.com/problems.html
FAQ
On Thu, Sep 17, 2009 at 4:42 PM, Jim Reisert AD1C
jjreis...@alum.mit.edu wrote:
Is there some reason why setup-1.7 has to blow up to full-screen when
the Select Packages screen comes up? I prefer the friendlier 1.5
version.
I forgot to mention, that the back/cancel etc. icons at the bottom
On 09/17/2009 06:42 PM, Jim Reisert AD1C wrote:
Is there some reason why setup-1.7 has to blow up to full-screen when
the Select Packages screen comes up? I prefer the friendlier 1.5
version.
Yes, it was changed so that you could easily see all the information in
the packages listed
On Thu, Sep 17, 2009 at 5:18 PM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
On 09/17/2009 06:42 PM, Jim Reisert AD1C wrote:
Is there some reason why setup-1.7 has to blow up to full-screen when
the Select Packages screen comes up? I prefer the friendlier 1.5
version.
Yes
On Thu, Sep 17, 2009 at 06:50:39PM -0600, Jim Reisert AD1C wrote:
On Thu, Sep 17, 2009 at 5:18 PM, Larry Hall (Cygwin)
reply-to-list-only...@cygwin.com wrote:
On 09/17/2009 06:42 PM, Jim Reisert AD1C wrote:
Is there some reason why setup-1.7 has to blow up to full-screen when
the Select Packages
Anyone who's been trying out the 256-color support in the current test
release of screen, please let me know how that's working for you. Please
report what terminal you're using (Cygwin, xterm, rxvt, MinTTY, PuTTYcyg,
others?), whether you're able to get 256 colors, and whether there are any
new
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.
--
Joel Eidsath
--
Problem reports: http://cygwin.com/problems.html
FAQ
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
won't
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
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 talk
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
/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
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 for
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:
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
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
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
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 on
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
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
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 processes
On 2009-08-31, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com
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
TV wrote:
On 2009-08-31, Christopher Faylor
cgf-use-the-mailinglist-ple...@cygwin.com 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
On 2009-09-01, Dave Korn da...@googlemail.com 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,
On Tue, Sep 01, 2009 at 10:23:58AM +, TV wrote:
On 2009-09-01, Dave Korn da...@googlemail.com 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
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
Ah, censorship. The Official Truth will become the Truth,
when the opposition is censored.
On 2009-09-01, Dave Korn davek.spamt...@googlemail.com 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,
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
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 http://defaria.com
The gene pool sure could use a little chlorine.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
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
--
Problem
Andy Koppe andy.koppe at gmail.com writes:
Andrew Schulman:
Instructions for starting screen with 256 color support are in
/usr/share/doc/screen/README.Cygwin. In brief, you have to invoke screen
as
TERM=screen-256color screen
I don't think that's quite right. Screen needs
TERM=xterm-256color screen -T screen-256color
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put this command
Andrew Schulman:
TERM=xterm-256color screen -T screen-256color
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put
Andrew Schulman:
TERM=xterm-256color screen -T screen-256color
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put
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 reading the
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 markjr...@gmail.com
--
Problem reports: http://cygwin.com/problems.html
FAQ:
Andrew Schulman:
Instead of specifying -T screen-256color every time, one can just put
'term screen-256color' into .screenrc. I'll update the docs to show this
when I make the release current.
Is there any reason that I shouldn't put this command into the default
/etc/screenrc file
You're talking about setting e.g. TERM=xterm-256color in the environment by
default, but I was asking whether it would cause any harm to put 'term
screen-256color' into the default /etc/screenrc. Know any reason that I
shouldn't?
Well, yes. 'term screen-256color' sets TERM=screen
'term screen-256color' sets TERM=screen-256color in the
environment of programs running inside screen, hence any program or
script that recognises screen but not screen-256color will no
longer work as expected.
Btw, a different approach to enabling 256 colour support by default,
which doesn't
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
Ping. Thanks, Andrew.
# 1.5
B=http://home.comcast.net/~andrex2/cygwin/1.5/screen/
wget \
${B}/setup.hint \
${B}/screen-4.0.3-3.tar.bz2 \
${B}/screen-4.0.3-3-src.tar.bz2
# 1.7
B=http://home.comcast.net/~andrex2/cygwin/screen/
wget \
${B}/setup.hint \
${B}/screen-4.0.3-4.tar.bz2
On 25/08/2009 15:29, Andrew Schulman wrote:
I have a new release of screen, that supports 256-color terminals. The 256
color support hasn't been well tested yet, so I'm providing this as a test
release in order to get reports from users. So, the setup.hint file will
need to be updated.
Your
. I did warn on the
cygwin list that this is a test release, especially for 1.5, and that I'll
need to see positive test reports before I move it to current.
I believe that the screen executable in the 1.5 package was compiled
against libncurses8, and I don't have a way to recompile it now, so let's
that this is a test release, especially for 1.5, and that I'll
need to see positive test reports before I move it to current.
I believe that the screen executable in the 1.5 package was compiled
against libncurses8, and I don't have a way to recompile it now, so let's
leave the setup.hint as is. To me
... but GNU screen had been broken, making
Cygwin again completely unusable, because screen is necessary
with the primitive Windows window management. (Tabbed putty
would help.)
The more specific problem is that GNU screen has started
having random hangs, locking up the entire terminal
available, including some to X, so of course I tried them.
X wasn't fixed... but GNU screen had been broken, making
Cygwin again completely unusable, because screen is necessary
with the primitive Windows window management. (Tabbed putty
would help.)
The more specific problem is that GNU screen
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
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
On 2009-08-31, Charles Wilson cyg...@cwilson.fastmail.fm 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
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:
On 2009-08-31, Ken Brown kbr...@cornell.edu 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
On 2009-08-31, Andrew Schulman schulman.and...@epamail.epa.gov 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!
On 2009-08-31, Tuomo Valkonen tuo...@iki.fi wrote:
On 2009-08-31, Ken Brown kbr...@cornell.edu 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
On 8/31/2009 2:28 PM, Tuomo Valkonen wrote:
On 2009-08-31, Ken Brown x...@xxx.xxx 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
On 2009-08-31, Ken Brown kbr...@cornell.edu 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
On 2009-08-31, Ken Brown kbr...@cornell.edu 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
A new version of the screen package (4.0.3-3 for Cygwin 1.5, 4.0.3-4 for
Cygwin 1.7) is now available in the Cygwin distribution.
screen is a terminal multiplexer and window manager that runs several
separate 'screens' on a single physical character-based terminal. Each
virtual terminal emulates
On Mon, Aug 31, 2009 at 09:09:25PM +, Tuomo Valkonen wrote:
On 2009-08-31, Ken Brown x...@xxx.xxx 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
On 2009-08-31, Christopher Faylor cgf-use-the-mailinglist-ple...@cygwin.com
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
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 glaring there
Andrew Schulman:
Instructions for starting screen with 256 color support are in
/usr/share/doc/screen/README.Cygwin. In brief, you have to invoke screen
as
TERM=screen-256color screen
I don't think that's quite right. Screen needs to be told what
terminal it is itself running in. This means
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 get
On 2009-08-30, Andy Koppe andy.ko...@gmail.com 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
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
screen had been broken, making
Cygwin again completely unusable, because screen is necessary
with the primitive Windows window management. (Tabbed putty
would help.)
The more specific problem is that GNU screen has started
having random hangs, locking up the entire terminal.
The hung screen
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:
On 2009-08-29, Andy Koppe andy.ko...@gmail.com 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
I have a new release of screen, that supports 256-color terminals. The 256
color support hasn't been well tested yet, so I'm providing this as a test
release in order to get reports from users. So, the setup.hint file will
need to be updated.
Please upload, for 1.5 and 1.7. Thanks, Andrew
for screen? Did that ever get
pushed
into the main cygwin? I can't get 256 colors working under screen and
I'm also having trouble compiling my own (and it looks like the old
links in that email are no longer around, either).
Sorry it took me a while to get back to this. No, I got hung up
miniature X servers that can tunnel
over SSH... I was thinking maybe make a local xorg.conf on the Windows box and
set up two screens with Xinerama or something like that.
This is the closest I got with Xming...
xming :0 -query 10.60.20.165 -clipboard -screen 0 @1 -screen 1 @2
This makes two seperate
with Xming...
xming :0 -query 10.60.20.165 -clipboard -screen 0 @1 -screen 1 @2
This makes two seperate screens (like if Xinerama is turned off, and you get two
GNOME panels)... and they arn't full screen either just maximized (can't seem to
use the option -fullscreen when specifying two screens
Hi,
I saw the recent thread about the unwanted console windows appearing
with MinTTY on Win7.
I just wanted to mention that I see a similar issue with screen in the
same environment (Win7 RC 64-bit, Cygwin 1.7, screen 4.0.3-1): Each new
screen window that is opened creates a persistent
On Sun, Jul 05, 2009 at 06:15:51PM +0200, Sylvain Pasche wrote:
I saw the recent thread about the unwanted console windows appearing
with MinTTY on Win7.
I just wanted to mention that I see a similar issue with screen in the
same environment (Win7 RC 64-bit, Cygwin 1.7, screen 4.0.3-1): Each new
On 7/5/2009 7:37 PM, Christopher Faylor wrote:
I'd appreciate it if you would test this and let everyone know. You
have the power:
http://cygwin.com/snapshots/
Tried with the 2009-07-04 snapshot, and the issue is gone :-). No more
console windows are opened when launching screen and I
2009/7/5 Sylvain Pasche:
(by the way, I recently discovered MinTTY and I'm pretty impressed. MinTTY +
screen offers a very nice multiple-tab environment on Cygwin).
Thanks!
Btw, you can enable browser-style tab switching with (Shift+)Ctrl+Tab
by mapping MinTTY's keycodes for those in .screenrc
setup.exe's current local directory screen doesn't accurately describe
the purpose of the local directory when the user is installing from a
local mirror (rather than downloading or download-and-installing), which
can be confusing. The attached patch changes the description based on
what
On Mon, May 11, 2009 at 10:50:41AM -0500, Thrall, Bryan wrote:
2009-05-11 Bryan Thrall bryan.thr...@flightsafety.com
* localdir.cc (load_dialog): Choose description string based on install
type.
* res.rc (IDD_LOCAL_DIR): Replace static description text with
IDC_LOCAL_DIR_DESC.
of
screen. As far as I can see, recreating the raw output from the cooked
one isn't possible in general.
This article has more on this:
http://homepages.tesco.net/~J.deBoynePollard/FGA/capture-console-win32.html
Andy
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports
need to be sent to the pty to be displayed by the likes of
screen.
If you can get the character cell contents and attributes and you can
push data into the consoles input buffer then, AFAIK, that's really all
you need to create a pty. You can see that Console is doing something
like that because
as it came from the console app
would need to be sent to the pty to be displayed by the likes of
screen. As far as I can see, recreating the raw output from the cooked
one isn't possible in general.
You could intercept the calls to the console APIs by finding out where
the imports resolve to using
2009/5/1 Barry Kelly:
ReadConsoleOutput() on the hidden console only
gives you the cooked output in terms of character cell contents and
attributes, whereas the raw output as it came from the console app
would need to be sent to the pty to be displayed by the likes of
screen. As far as I can
I could
imagine some kind of a DOS-to-Unix terminal wrapper program, but I've never
seen
one and have no idea how it would work.
...and if one was possible why wouldn't the techniques that it incorporates be
part of cygwin?
Laziness on your part?
hahahahahaha
--
Unsubscribe info:
On Tue, Apr 21, 2009 at 06:39:27AM -0400, Andrew Schulman wrote:
I could imagine some kind of a DOS-to-Unix terminal wrapper program,
but I've never seen one and have no idea how it would work.
...and if one was possible why wouldn't the techniques that it
incorporates be part of cygwin?
Maybe someone knows a solution to this, but I don't. Although I maintain
screen
for Cygwin, I know almost nothing of the details of how terminals work. I
could
imagine some kind of a DOS-to-Unix terminal wrapper program, but I've never
seen one and have no idea how it would work
Andrew Schulman wrote:
In general, non-cygwin programs can't be run reliably inside of an
application that uses cygwin PTYs, including xterm, rxvt, and screen.
Maybe someone knows a solution to this, but I don't. Although I maintain
screen
for Cygwin, I know almost nothing
On Tue, Apr 21, 2009 at 06:46:05PM +0100, Andy Koppe wrote:
Andrew Schulman wrote:
Maybe someone knows a solution to this, but I don't. ?Although I
maintain screen for Cygwin, I know almost nothing of the details of how
terminals work. ?I could imagine some kind of a DOS-to-Unix terminal
wrapper
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: DOS
wondering, we are running a server program that has a DOS
interface. It does not work under screen. This program is very similar
to the DOS edit program which also does NOT work under screen. So, my
question would be, what is required to fix screen so it will work with
the DOS edit program
. Do you know where I might direct the request?
In case your wondering, we are running a server program that has a DOS
interface. It does not work under screen. This program is very similar
to the DOS edit program which also does NOT work under screen. So, my
question would be, what
We need to run a DOS program as a service. The program provides
valuable information in the DOS window in an interactive ASCII color
interface but does not provide any method to connect to this interface
if started as a service.
One solution is to run this program under screen. Unfortunately
:
We need to run a DOS program as a service. The program provides
valuable information in the DOS window in an interactive ASCII color
interface but does not provide any method to connect to this interface
if started as a service.
One solution is to run this program under screen. Unfortunately
need edit to work. I'm just trying to provide a
program that can be used to test the DOS graphical interface under
screen. edit re-sizes the DOS window. The server does not do this.
You may know of another DOS interface that could be used to test this.
-Original Message-
From: William
else. The session is hung and I can not see the interface.
I don't actually need edit to work. I'm just trying to provide a
program that can be used to test the DOS graphical interface under
screen. edit re-sizes the DOS window. The server does not do this.
You may know of another DOS
Hi!
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.
It seems the build the cygwin setup uses is broken? I tryed three times
* 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
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
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 prompt
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
Hello Andrew
I just did a quick test so far but it doesn't seem to work correctly.
The behaviour changed to the following:
I open a screen session - and disconnect (not detach!) from the ssh session.
I come back with screen -DRR and I get my old screen.
That's *good* and how I want
screen hangs when attempting to reattach to a session that wasn't manually
detached but instead the ssh connection to the server where screen is running
was closed.
i can neither
screen -list
nor
screen -D -RR
to get back into the session. for both calls screen will wait forever
601 - 700 of 1151 matches
Mail list logo
