> I'm wondering what the proper value of $TERM would be for screen
> running in a terminal which initially has its $TERM variable equal to
> "xterm-256color". Once I launch screen, $TERM becomes "screen", which
> seems to lack many capabilities, notably: applications don't consider
> it to be capab
> I am currently running mc 4.8.27 and GNU Screen 4.09.00.
>
> I am having trouble getting 256 colors to display in Midnight Commander when
> it is running within GNU Screen. ?I can confirm that MC 256-color themes
> display correctly when it is run in the terminal outside of Screen (in
> xfce4
> > * Migrate from fifos to sockets
>
> In Cygwin I get a socket error when I try to start screen 4.6.0:
>
> $ screen -AURD
> shadow socket open: No such device or address
>
> Any ideas? I looked in the configure script for an option to force use of
> fifos instead of sockets, but I didn't see
> * Migrate from fifos to sockets
In Cygwin I get a socket error when I try to start screen 4.6.0:
$ screen -AURD
shadow socket open: No such device or address
Any ideas? I looked in the configure script for an option to force use of
fifos instead of sockets, but I didn't see one.
Thanks,
And
Subject says it. Build log excerpt:
gcc -c -I.
-I/home/andrex/dev/cygwin/screen/screen-4.3.1-1.x86_64/src/screen-4.3.1
-DETCSCREENRC='"/etc/screenrc"'
-DSCREENENCODINGS='"/usr/share/screen/utf8encodings"' -DHAVE_CONFIG_H
-DGIT_REV=\""`git describe --always 2>/dev/null`"\" \
-ggdb -O2 -pipe -
> Hi,
>
> I'm having a problem with the hardstatus in the window title disappearing
> using screen version 4.2.1.
>
> The only 2 lines in my ~/.screenrc are:
>
>
> termcapinfo xterm* 'hs:ts=\E]2;:fs=\007:ds=\E]2;screen\007'
> hardstatus string "%h [screen %n%?: %t%?]"
>
>
> In GNU screen vers
> The current git master is solid enough for a new release and it
> sure will be better than no release in so many years. As I said
> screen is still way better suited for many users including me and
> tmux is not a suitable replacement. Distros using random git master
> revisions should be reason
> Regarding the subject, just wanted to know this because I am trying to
> decide whether to go with Screen or Tmux. So far in my experience,
> Screen seems more mature (but I might not be qualified enough to say
> this :-) ) .
Tmux won't run under Cygwin, in case that matters to you [1]. scree
> I would highly encourage using as much from the git repository on
> savannah.gnu.org as possible. There have been various fixes related to
> vertical splits, especially related to scrolling performance with
> vertical splits. Unfortunately, it is difficult to isolate the commits
> that deal with
Hi all. I'm the maintainer of screen in Cygwin. We currently have version
4.0.3, with some Cygwin-specific patches and 256-color support.
I'm looking for the famous vertical split patch. I see the version linked
from http://fungi.yuggoth.org/vsp4s/, but that version seems to be
outdated. I tri
> Hi all. I'm running GNU Screen on Cygwin on one laptop, and on Debian Linux
> on
> another. (I may switch to tmux one day, as it works much like screen but is
> newer. But I don't think Cygwin ships tmux binaries.)
>
> I want to use a single-keystroke escape key in Screen. Because I almost
> > > Similarly, I get warnings about incompatible implicit declarations of
> > > strlen, strcpy, and strncpy, e.g.
> > >
> > > screen.c: In function 'main':
> > > screen.c:473: warning: incompatible implicit declaration of built-in
> > > function 'strcpy'
> > > screen.c:642: warning: incompatible
> (1) The build fails with
>
> extern.h:149: error: conflicting types for 'execvpe'
>
> Indeed Cygwin's /usr/include/unistd.h has
>
> int _EXFUN(execvpe, (const char *__file, char * const __argv[], char *const
> __envp[] ));
>
> while extern.h has
>
> extern void execvpe __P((char *, char **,
begin 644 execvpe.patch
M9&EF9B`M=7).('-C'1E'1E'1EFUO9&5M7V%B;W)T(%]?4"@Hhttp://lists.gnu.org/mailman/listinfo/screen-users
Hi. I've been building screen 4.0.3 for Cygwin 1.5 for several years now.
Now Cygwin 1.7 is out, and it appears that the Cygwin API has changed,
because I'm getting some build errors.
Can someone please advise what's the simplest or best way to correct for
these?
(1) The build fails with
extern
> As an aside, with the proliferation of version control & source
> management software, it's becoming difficult to keep up.
>
> I spent over an hour playing with git and not getting anywhere, and less
> than ten minutes building & testing the new version.
OT, but no kidding, what a pain in the
> Hello everyone. Are there any screen packagers on this list? I am
> contemplating a sort of a beta-release somewhat soon-ish (still
> non-trivial amount of work to do, though, so no ETA yet), and was
> thinking if this list is the best place to reach the packagers.
Hi. I maintain screen in Cygw
> Micah Cowan wrote:
> > Our beloved maintainer Sadrul Chowdhury has apparently been missing
> > since mid-July.
>
> And has since returned. Looks like he's well, and back, sorry for the
> alarm. :)
Whew, that's a relief.
___
screen-users mailing lis
> On Thu, Jan 15, 2009 at 07:58:42AM -0800, Micah Cowan wrote:
> > Grigorios Bouzakis wrote:
> > > On Sun, Jan 11, 2009 at 12:55:19AM -0800, moueza wrote:
> > >> Ctl-A AltGr-| makes nothing
> > >>
> > > GNU screen cant split vertically by default.
> > > Theres a patch for it though: http://fungi.y
>autossh -M 0 -t RemotePC "screen -e^Yy -D -R -S `uname -n`2RemotePC-$NEXT"
> What I would like to be able to do is to attach to this screen from a
> new shell in RemotePC, or a new screen launched from MyPC, such that
> the deattached screen now becomes attached AND the new shell or screen
>
> How to show the permanent list of opened windows (key binding C-a w)?
I like this:
caption always '%-Lw%{.kG} %n%f %t %{-}%+Lw'
HTH
Andrew
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/listinfo/screen-users
screen 4.0.3 is now available in the Cygwin distribution. You can find it
in the Cygwin installer in the "Utils" category.
All of screen's known bugs in Cygwin have been fixed. It works fine inside
an rxvt, xterm, or PuTTYcyg terminal. Inside a DOS console, screen works,
but in order to be able
> Finally I ran an strace -p on the parent SCREEN process, and suddenly
> everything just began magically working again!
>
> Does anyone know what exactly happened here?
I don't know what happened, but I appreciate the report of a possible
workaround. Hanging sessions and inability to reattach
> I'm using it right now. Works great. Awesome for running an ssh
> SOCKS proxy on my desktop and then detaching screen...
OK, good. However, if what you want is to set up permanent port forwarding
or proxying via ssh, you may want to have a look at autossh, which is built
to maintain an ssh co
screen 4.0.3 is now available in the Cygwin distribution. Cygwin users can
install it using the setup utility; screen is in the "Utils" category.
Questions or bug reports about screen in Cygwin should be directed to the
Cygwin list, cygwin at cygwin dot com.
Andrew.
__
> I have a Linux notebook that connects to a Linux server by ssh. The
> notebook can be suspended to disk at any time, while ssh sessions to
> the server are still running. How can screen be used so that, when the
> notebook is brought back from its dormant state, whatever ssh sessions
> it had a
>I would need to be able to open several, independent screen
> sessions on different windows, and automatically reattach to each of
> them correctly and separately after bringing the notebook back online
> again. Is this possible with a combination of autossh and screen?
man screen, and look a
> JCA wrote:
>>Is it not the case that this would reconnect, but spawning a new
>> shell? I would like to reconnect to the same shell, which might be
>> running other applications.
>
> This is the typical way to use screen:
>
> - Turn on your laptop, open ssh connection to the server
> - On
28 matches
Mail list logo
