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 capable of disp
I'm trying to compile screen on the latest macOS Monterey, but the
`./configure` step fails with the following error:
configure: checking select...
configure: checking select with -lnet -lnsl...
configure: error: !!! no select - no screen
Does anyone know how to fix this?
Incidentally, my prima
Bob Proulx wrote:
> sleep 100 >/dev/null 2>&1 /dev/null`, but they
were still hanging the screen window, until adding the stdin
redirection per your suggestion eliminated the problem.
It's still a mystery as to why it's happening. I tried to reduce the
`zombie_timeout` to small values like 0 an
This problem has been plaguing me for years now, and still now with
the recent 4.6.2 release.
Steps to reproduce:
1. Start a new screen session.
2. Create a new window.
3. Hit Ctrl-D. Window closes instantly.
4. Start another windows.
5. Run the following bash command: sleep 100 &
6. Hit Ctrl-D. W
3
It seems that other terminal emulators, including xterm and urxvt,
have the same or similar sets of default bindings, e.g. Ctrl-3 to ^[
and Ctrl-4 to \^
On Wed, Jun 13, 2018 at 3:32 PM, David Woodfall wrote:
> On Wednesday 13 June 2018 14:21,
> Dun Peal put forth the proposition:
>&g
The problem is that my terminal maps Ctrl-n, for certain values of n,
to various escape sequences.
For example,Ctrl-3 generates ^[ (escape), so it enters Copy Mode
instead of switching to window 3.
Ctrl-4 genertes \^ (FS, which is interpreted as SIGQUIT).
Etc.
Is there a way to "unmap" combinat
Thanks! I filled out the list. Note that in some places I verified
with `od -tx1 -An`, because just using Ctrl+v printed
nothing visible on screen.
On Thu, May 31, 2018 at 10:50 AM, Amadeusz Sławiński wrote:
> On Thu, 31 May 2018 10:33:47 -0500
> Dun Peal wrote:
>
>> Hi Amad
^v or od)
On Fri, Jun 1, 2018 at 10:26 AM, Dun Peal wrote:
> Thanks! I filled out the list. Note that in some places I verified
> with `od -tx1 -An`, because just using Ctrl+v printed
> nothing visible on screen.
>
> On Thu, May 31, 2018 at 10:50 AM, Amadeusz Sławiński wrote:
&g
).
I can already tell you my terminal behaves slightly differently than
yours - by contrast to you, my 0 doesn't work, whereas 2 and 8 do
work, in addition to 1 and 9 that worked for you.
On Thu, May 31, 2018 at 7:03 AM, Amadeusz Sławiński wrote:
> On Tue, 29 May 2018 10:11:12 -0500
>
I make it work again?
On Tue, May 29, 2018 at 10:11 AM, Dun Peal wrote:
> Hi folks,
>
> I just upgraded to Ubuntu 18.04 from 16.04, and noticing an odd
> behavior with the key combinations that used to switch windows by
> number.
>
> In 16.04, if I held Ctrl and hit the esca
Hi folks,
I just upgraded to Ubuntu 18.04 from 16.04, and noticing an odd
behavior with the key combinations that used to switch windows by
number.
In 16.04, if I held Ctrl and hit the escape key, and immediate after
it a number key (without releasing the Ctrl), I was switched to that
window numb
Fri, 25 May 2018 09:58:47 -0500
> Dun Peal wrote:
>
>> Hi folks,
>>
>> I used to #define TOPSTAT in config.h to set the status line to render
>> on the first line of the terminal rather than the last.
>>
>> It seems this incantation no longer works at least
Actually, I still see a few minor errors after installing
`ncurses-term`. For example:
"TERMCAP", line 20, col 1, terminal 'SC': Missing separator
On Thu, May 24, 2018 at 6:46 PM, Dun Peal wrote:
> Thanks, Axel. Installing ncurses-term (with `apt install ncurses-term`
Hi folks,
I used to #define TOPSTAT in config.h to set the status line to render
on the first line of the terminal rather than the last.
It seems this incantation no longer works at least as of v.4.6.2.
Is there an alternative new way to set the same configuration?
Thanks, D.
_
Thanks, Axel. Installing ncurses-term (with `apt install ncurses-term`
on Ubuntu) fixed the issue immediately.
Best, D.
On Thu, May 24, 2018 at 6:39 PM, Axel Beckert wrote:
> Hi,
>
> On Thu, May 24, 2018 at 04:53:32PM -0500, Dun Peal wrote:
>> I recently upgraded to latest stabl
Hi there,
I recently upgraded to latest stable Ubuntu (18.04 LTS).
Unfortunately, after building screen from source, 256 mode no longer
seems to work. For example, if I launch vim, it reverts to the 8 color
color scheme.
This was a problem with both the 4.6.2 release (which appears to be
the late
On Tue, Jul 5, 2016 at 12:33 AM, Clark Wang wrote:
> For a detached session I think `screen -r' and `screen -x' are doing the
> same thing.
>
If that's the case, I'll just use `screen -x` always. This is because of
my use-case:
I am using this for a multiple display setup, where each display h
x, since it attaches to the session
whether it's detached or not.
Hope my question is clear... D.
On Mon, Jul 4, 2016 at 6:23 PM, Andrew Savchenko wrote:
> Hi,
>
> On Mon, 4 Jul 2016 18:15:50 -0400 Dun Peal wrote:
> > Looking for a command that would attach to a screen session
Looking for a command that would attach to a screen session "foo", wether
it is detached or not. It seems like `screen -x foo` would do it - it
attaches to "foo" in both cases.
But is it really the same? Or is there any difference between `screen -x
foo` and `screen -r foo` when "foo" is detached
> Hey,
>
> adding screen-users@gnu.org back to CC, because I lost it in last reply
>
> On Tue, 5 Apr 2016 14:36:44 -0400
> Dun Peal wrote:
>
> > This did fix the issue. I then got an error:
> >
> > pty.c:42:10: error: 'pty.h' file not found with inclu
r '_NSIG'
for (sig = 1; sig < _NSIG - 1; sig++)
^
attacher.c:467:22: error: use of undeclared identifier '_NSIG'
for (sig = 1; sig < - 1; sig++) {
^
3 errors generated.
make: *** [attacher.o] Error
I'm trying to build Git HEAD of screen on OS X El Capital (latest
version: 10.11.4) and getting the following error output - help
appreciated:
$ make
AWK=gawk srcdir=. sh ./term.sh
AWK=gawk CC="gcc -g -O2 -Wall -Wextra -std=c11" srcdir=. sh ./comm.sh
gcc -c -iquote. -DETCSCREENRC='"/usr/local/etc
27;
u->ut_exit.e_termination = 0;
~ ^
utmp.c:385:5: error: no member named 'ut_exit' in 'struct utmpx'
u->ut_exit.e_exit = 0;
~ ^
utmp.c:406:9: warning: incompatible pointer to integer conversion returning
'char *' from a function
Hi,
I'm trying to build Git HEAD of screen on OS X El Capital (latest
version: 10.11.4) and getting the following error output - help
appreciated:
$ make
AWK=awk srcdir=. sh ./term.sh
AWK=awk CC="gcc -g -O2 -Wall -Wextra -std=c11" srcdir=. sh ./comm.sh
gcc -c -iquote. -DETCSCREENRC='"/usr/local/
gt; And hit enter to execute. The command is actually a screen script stored
>> at
>> that location. So adding new commands is matter just of adding new script
>> files.
>>
>> Here's the actual binding:
>> bind ^L eval 'register z ":source /home/user/
Folks,
There's a sequence of screen operations that I execute every once in a
while. I can use `bind` and `eval` to execute it by keystroke, but it
is not used commonly enough to justify a keystroke binding.
Is there a way to define it such that I can execute it by running a
custom command on the
Some digging on my own revealed the following chunk of code in `config.h`:
/*
* If you'd rather see the status line on the first line of your
* terminal rather than the last, define TOPSTAT.
*/
/* #undef TOPSTAT */ct
It moves both the hardstatus and the messages to the firs
On Fri, May 6, 2011 at 2:16 PM, Artur Skonecki wrote:
> Currently, it is not possible to put hardstatus anywhere else than last
Thanks. Since I can't move the hardstatus line, I'm now trying to
prevent the clash by moving the message line to the top. The manpage
says about it:
While this lin
Hi there,
I currently use a nice configuration[1] that shows the permanent
hardstatus in the xterm window titlebar, while messages are rendered
on the last line.
Unfortunately, that's not portable to pure console servers without X.
When I move the hardstatus to the "message" area, it gets overwri
Hi,
I'd like to be able to run executables or (bash) shell-commands in
their own detached screen sessions, so I can naturally interact with
all their IO streams: read stdout and stderr, write to stdin.
What's the best way to do that?
Ideally it would be something like `git -dmS foo-interaction f
Thanks, that solved my problem, and that FAQ was incredibly
informative; bookmarked!
.D
On Wed, Jan 26, 2011 at 10:36 AM, Phil! Gold wrote:
> * Dun Peal [2011-01-24 13:35 -0600]:
>> I have the following line in my .screenrc:
>>
>> termcapinfo xterm*|rxvt*|kterm*|Eterm*
Hi!
I have the following line in my .screenrc:
termcapinfo xterm*|rxvt*|kterm*|Eterm* 'hs:ts=\E]0;:fs=\007:ds=\E]0;\007'
This line makes screen display the permanent hardstatus in my terminal
emulator's (Gnome Terminal) title bar. This is great since I always
need to be able to see at a glance
Hi!
I have the following line in my .screenrc:
termcapinfo xterm*|rxvt*|kterm*|Eterm* 'hs:ts=\E]0;:fs=\007:ds=\E]0;\007'
This line makes screen display the permanent hardstatus in my terminal
emulator's (Gnome Terminal) title bar. This is great since I always
need to be able to see at a glance
33 matches
Mail list logo
