Resending; meant to send this to the list, not privately.
On Sun, Aug 14, 2016 at 7:11 AM, Aleksey Tsalolikhin
wrote:
>
> Lovely, thank you very much Axel and Pieter!
>
> Why does pressing ctrl-1 make 1, and pressing ctrl-3 make ^[ ? Pressing
> ctrl-8 makes nothing, like Pieter said (you can't
On Thu, Aug 27, 2015 at 2:33 AM, Gheorghe Lisca wrote:
> Hi everyone,
>
> I just start using GNU Screen and I want to set up my configuration file.
> More precisely I am trying to bind the navigation commands
> "focus left" to "Ctrl + j"
> "focus down" to "Ctrl + k"
> "focus up" to "Ctrl + l" and
Features screen. :D
http://xkcd.com/686/
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
Maintainer of GNU Wget and GNU Teseq
http://micah.cowan.name/
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mail
SMaddox wrote:
> I apologise if this is a stupid question, but I have been searching for
> the past hour and am going crazy because I can't find the answer.
>
> How do you pass function keys (F1,F2,etc) on to htop through screen?
> Neither 'F3' nor 'C-a F3' brings up search in htop as it should.
Joahnn Gile wrote:
> So what's wrong here, is termcapinfo not modifying the terminfo entry?
You seem to be misunderstanding the purpose of termcapinfo. Its purpose
is not to modify actual termcap or terminfo entries, in particular the
ones that other applications might see and modify behavior for.
Danny Colligan wrote:
> Hello,
>
> Is there any way to do a case-insensitive search in screen's copy
> mode? The / and ? commands only seem to do case-sensitive searches.
> (Or, for bonus points, is there any way to use regular expressions to
> search in copy mode?)
There's an "ignorecase on" sc
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. :)
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
Maintainer of GNU Wget an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Our beloved maintainer Sadrul Chowdhury has apparently been missing
since mid-July. This was brought to my attention when it became clear
that he was about to miss the deadline for submitting a final evaluation
for the Google Summer-of-Code student who
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Jones wrote:
> I was evaluating tmux over the weekend and though I'm not prepared to
> switch any time soon, I couldn't help but notice that tmux's scrolling
> in vertical split screen mode is both very fast and devoid of the
> annoying artifacts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Please keep it on the list)
Tales Macedo wrote:
> Thanks for answer me
>
>Initially excuse my english.
>When I try to run the command $ who am i on screen session, it does
> not show anything. Type:
>
> $ screen
>
> (on screen ses
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tales Macedo wrote:
> Good Afternoon Friends,
>
>Why the command who am i don't work on screen ?
That's very unlikely. Why don't you tell us exactly what you're trying,
what you're seeing, and what you expected it to do that differs from the
actu
Rainhard wrote:
> Hi everyone,
>
> I have a problem to kill screen and its childs.
> I'm starting a program through rc.d scripts with
> screen -dmS --
> So far everything works great, but if I make a kill on screen,
> the child survives.
> Anyway, if I'm starting the program with screen -mS ...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dwight wrote:
> I am new to screen, and am having this same issue with multiuser mode on
> AIX. I saw Bug #15003 was opened for this problem, but was closed for
> lack of info. I'm a sysadmin, not a developer, but I'd be
> glad to provide more info f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wang, Roger wrote (way back in April):
> Hi Michael,
>
> I used the attached patch so the utf8 hardstatus would display
> correctly in my xterm titlebar. Is it ok or how could I improve it?
Hi Roger, sorry this response is so long past your original
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Ackersviller wrote:
> I've recently started displaying load averages in screen's harstatus line,
> and notice something strange on one particular system. The numbers are
> approximately four times the ones shown by the HP-UX uptime program.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, as the documentation seems to be one of the biggest remaining
obstacles to a 4.1.0 release of GNU Screen, and as it's been this way a
very long time, I've taken one step towards trying to ease the prospect
of getting this work done.
I've gone thro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
oreng wrote:
> I am planning to do a 10 minutes presentation about this topic.
> Please watch my screencast and provide me any feedback/corrections you want.
> http://www.youtube.com/watch?v=IFClpADY7Tc
>
> Also I have the following questions:
> 1. Wh
Nelgin wrote:
> Now, say I want to stuff a command..
>
> screen -S machine1 -X stuff "who^J"
>
> This works. However if I put it in for a for look
>
> for i in `cat serverlist`
> do
> screen -S $i -X stuff "who^J"
> done
The most obvious explanation is that your for-loop isn't doing what you
th
I'm afraid I really don't know what you're asking for. Details?
Tales Macedo wrote:
> Good Evening,
>
>How Can I Disable Ctrl + a,b,c,d key functions on Screen ?
___
screen-users mailing list
screen-users@gnu.org
http://lists.gnu.org/mailman/lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
clemens fischer wrote:
> (sorry for being late)
>
> On Wed-2009/05/13-16:44 tianlijian wrote:
>
>> When i use the `Shift+PgUp' to scroll back to the bash history, it
>> will scroll down automatically in few seconds. What can i do to
>> prevent it?
I
David Chanters wrote:
Hi all,
I like the feature of multi-user screen. I often do this via:
screen -x -S somesessionname
And it works great -- until, that is, I change windows in screen (via
^a a, or ^a 1 -- where "1" could be any number depending on the number
of windows in screen). As soon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
clemens fischer wrote:
> clemens fischer wrote:
>
>> is there a way to evaluate this register as screen commands?
>
> Thank you very much, Gerald Young and Micah Cowan! Looking at my older,
> unanswered article I think I had a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
clemens fischer wrote:
> On Thu-2009/04/30-16:47 clemens fischer wrote:
>
>> Recently I needed a screen command sequence more complex than the
>> usual key "bind" or "stuff". I turned to "process [key]", as the man
>> page said: "command can be used
Pau wrote:
> Hello,
>
> sometimes, when I am on a window, say window 3, and I forget about it
> and try to move to the next one, I assume it's 3 and then screen
> complains saying
>
> "This IS window 3 (zsh)."
>
> for some 20 (!) seconds.
>
> How can I disable that? Half a second would suffice.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, the email address with under I was subscribed to the screen lists
expired without my noticing. It was an email address I'd received for
being a member of a group, and that membership had expired.
I had not realized that this would mean I would no l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://log.or.cz/?p=39
I would have opted for proxying instead of library call hijacking, but
anything's better than nothing. Worth looking at.
- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
Maintainer of GNU Wget and GNU Te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Terry wrote:
> I'm confused. I read online that vertically splitting a window was
> available as of 4.00.03, which is what my screen version claims to be,
> yet when I type ctrl-a | (which means hold down ctrl and a, then
> release and press sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Nitsche wrote:
> Hello list!
>
> I'm new to this list and here's my first question.
>
> I'd like to know which security issues are important when I'm setting
> screen setuid root.
> I tried that on one maschine to use the multiuser feature of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kazuo Teramoto wrote:
> Hi, recent (git) version of screen changed my End key from ^[[4~ to
> ^[[8~ now End key dont work on zsh and vim. I can remap ^[[8~ on zsh
> and vim to End key, but I dont think this is the correct solution
> someone have the te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JuanPablo wrote:
> hi,
> I try make a backtick with automatic change of colors
> example
> #!/bin/bash
> #file name sbacktick
> cadena="Bright red on white"
> echo -e "\033[47m\033[1;31m $cadena \033[0m"
>
> in screenrc
> backtick 1 60 60 $HOME/bin/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Langella Raphael wrote:
> Hi, I'm running GNU Screen 4.00.02 under Linux RHEL 4u5. vim works
> fine under Linux, but if I ssh to a Solaris machine from within
> screen, then I've got some problem with vim. When I edit a file, I've
> got some garbage af
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ZelluX wrote:
> Hi, all
>
> I'm trying to write a test script for xen hypervisor, it works like this:
> 1. Run screen with two windows open
> 2. On the second window, run _sudo xm create my-domU.conf_, and then run
> _sudo xm console 2_ to attach to t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lehe wrote:
> Hi,
> Two questions about screen:
>
> 1. I was trying to switch from scroll back mode to command line mode by "C-a
> :". However instead a ":" is at prompt and seems ready to recieve what I'll
> type. So which mode did I enter actually a
)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknOogYACgkQ7M8hyUobTrGhQgCcCJMmBCivjAwZVsO3uFu9Cu2q
0O0AoIedicwNOFwLLxEQc8WYTgO6fmsd
=99jc
-END PGP SIGNATURE-----
commit 2cc00bf4d858ce36ff80b51560a795fb48303228
Author: Micah Cowan
Date: Thu Aug 7 22:10:08 2008 -0700
Proper 2-arg/3-arg seten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ssiza...@gmail.com wrote:
> On Thu, Mar 12, 2009 at 17:42, Micah Cowan wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> ssiza...@gmail.com wrote:
>>> I've been playing around with screen for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ssiza...@gmail.com wrote:
> I've been playing around with screen for the last two days and like it so far.
>
> But there is one thing that bothers me: When I start mutt from my
> shell (bash, with gnome-terminal), the terminal title changes to mutt:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Iowan wrote:
>> GNU ncurses has a specific entry for putty, so you might want to "tic"
>> the latest terminfo definitions from ncurses (it's in a file named
>> misc/terminfo.src, IIRC). And then, of course, have PuTTY set TERM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Florian Bender wrote:
>> Chris Lieb wrote:
>>> I have run into two issues getting screen to work with the Linux kernel
>>> configuration utility (make config).
>>>
>>> First, in PuTTY, the display is garbled when the config utility
I don't know what you mean by "is working perfectly", but just because
you place your screen sockets directory in a persistent location doesn't
mean that your screen sessions will persist across a reboot: they simply
cannot.
-mjc
Pau wrote:
> no, actually the
>
> --with-socket-dir option
>
> is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> Try adding the line:
>
>> terminfocap screen* ks@:ke@
>
>> to your final destination host's ~/.screenrc or /etc/screenrc, and see
>> if that makes a difference in (fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> The \E[?1 sets "cursor key mode", and the \E= sets "application mode".
>> You may possibly want to keep \E= if it doesn't screw things up, so now
>> try changing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> Try adding the line:
>
>> terminfocap screen* ks@:ke@
>
>> to your final destination host's ~/.screenrc or /etc/screenrc, and see
>> if that makes a difference in (fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> Micah Cowan wrote:
>> Chris Lieb wrote:
>>> I am a new screen user and have run into a problem.
>>> When I ssh into a server, screen automatically starts, just as I want.
>>> The number pad w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asif Iqbal wrote:
> On Wed, Mar 4, 2009 at 12:49 PM, Micah Cowan wrote:
> Perhaps the easiest way to deal with it (for screen only), is to add the
> following line to your ~/.screenrc or /etc/screenrc:
>
> termcapinfo xterm* k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asif Iqbal wrote:
> On Wed, Mar 4, 2009 at 3:39 AM, Micah Cowan wrote:
> - What is the output of the "infocmp" command
>
>> # Reconstructed via infocmp from file: /usr/share/lib/terminfo/x/xterm
>> xterm|vs100|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> Pau wrote:
>> Hello,
>
>> I was wondering whether it is possible to change the location of
>> uscreens from /tmp to some other place, because it gets deleted
>> everytime the computer boots, which i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Asif Iqbal wrote:
> Hi
>
> from my screen window I tried to bind the pgup key to scrollback like this
>
> :bindkey -k kP copy
>
> After that I hit `pgup' button and I get a `~' instead of expected
> scollback behavior.
Most likely the terminfo/te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pau wrote:
> Hello,
>
> I was wondering whether it is possible to change the location of
> uscreens from /tmp to some other place, because it gets deleted
> everytime the computer boots, which it does, because it is a laptop.
> It would be very useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Lieb wrote:
> I am a new screen user and have run into a problem.
>
> When I ssh into a server, screen automatically starts, just as I want.
> The number pad works without issue. I then ssh into another server,
> where screen also automatically
Marc Lanctot wrote:
> Typically I run commands on servers and let them run for some time..
> when I'm done I kill all the processes with one command.
>
> I would like to be able to kill all my screens in one command as well,
> so I thought of parsing screen -r and sending a "kill command" to each
Bruce Edge wrote:
> I caught this off the "ssh in new screen window (Chris Henderson)"
> thread and it showed me how to add more formatting to the window list,
> but I don't understand the syntax completely.
>
> Where is in the docs?
>
> windowlist string "(%3n) %{..g}[%{..Y}%t%{..g}]%{..g}%=%f"
Micah Cowan wrote:
> I find the index of commands from the texinfo-based docs to be
> _particularly_ handy. You might want to bookmark that page:
> http://www.gnu.org/software/screen/manual/html_node/Command-Summary.html
Hm, guess I actually meant this one:
http://www.gnu.org/softwa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron Davies wrote:
> btw, the note in the manual
>
> _Caution_: The `$STY' environment variable still reflects the old
> name. This may result in confusion. The default is constructed
> from the tty and host names.
>
> could be a lit
Aaron Davies wrote:
> is it possible to change the socket name of an existing screen?
C-a : sessionname newname
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
___
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Jones wrote:
> On Sat, Feb 21, 2009 at 09:42:41PM EST, Micah Cowan wrote:
>> The screen documentation is now available online at
>> http://www.gnu.org/software/screen/manual/
>
> What's the story behind this docume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm pleased to announce that Sadrul Habib Chowdhury is now a
co-maintainer for GNU Screen, and will be taking my place as I will be
stepping down from the official title.
I do plan on continuing to do more-or-less exactly what I do, continuing
with an
The screen documentation is now available online at
http://www.gnu.org/software/screen/manual/
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
___
screen-users mailing
Andy,
Does xterm have an entry in your /etc/termcap? Please provide that.
What do you get for "ldd screen"?
The thing that bothers me about this, is that the failure point must be
at screen, rather than the programs running under it, since the kend/kH
is failing to be translated from \EOF to scr
Well, my primary system is toast now, so my activity level may drop
dramatically (which is perhaps saying something :) ) for the next couple
of weeks. Sorry!
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jae Norment wrote:
> I use screen to log sessions where I patch Debian servers. Screen
> captures ANSI control codes (like positioning and color changes), which
> is probably appropriate, however, I want a version of the logs without
> those codes so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Pursell wrote:
> William Pursell wrote:
>> Aaron Davies wrote:
>>
>>> ok, here's a patch (i can't get github to work so this is against the
>>> tarball http://www.wpursell.net/screen-4.1.0w.110-349d.tar.gz)
>> the github address I gave is wrong
JuanPablo wrote:
> Micah,
> many thanks for you reply.
> is posible capture of similarly the alerm messages of screen ?
Unfortunately, I don't know of a practical way to do this. Perhaps
someone more clever than I will think of something.
--
Micah J. Cowan
Programmer, musician, typesetting ent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
JuanPablo wrote:
> hi,
> is posible capture the bell of screen in other program?
> example:
> if screen launch a bell, the dialog program is called
> dialog --msgbox "hello world" 6 25
>
> thanks
> JuanPablos
Try C-a : exec :.. /path/to/filter.pl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've slightly rearranged the order of your text somewhat, for my own
convenience in responding.
I apologize for taking so long to respond to your steady sets of patches
and notices on this. And particularly, for promising to set up a hosted
repository
Leslie P. Polzer wrote:
> I could only observe this problem with screen and long-running
> (or often typed-into) sessions of SBCL. But I hardly run any
> other program in Screen...
Didn't you say you could reproduce it in other apps as well, thus ruling
out the app?
--
Micah J. Cowan
Programmer,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leslie P. Polzer wrote:
>> I don't know of any screen commands that do this. I would expect it to
>> be a property of the terminal; a setting of stty. See what stty says
>> about the ocrnl or similar options when you do "stty -a".
>
> I can't. How wil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leslie P. Polzer wrote:
> Hi,
>
> it seems that some random screen command* switches Screen into
> sending ^M instead of a proper newline.
>
> Does anyone here know of a command that switches things
> like this?
I don't know of any screen commands t
Michael wrote:
> How can I move the caption line at the top of window?
I'm afraid that's not currently possible. :(
--
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
_
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.yuggoth.org/vsp4s/
The current git sources at Savannah can. And it's a different
implem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trent W. Buck wrote:
> Micah Cowan writes:
>
>> Yeah, screen doesn't allow split lines (or lines whose lengths are
>> greater than 2048 bytes).
>
> Don't the GNU Coding Conventions have something to say abou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
broz wrote:
> On Thu, 04 Dec 2008 10:02:31 -0800
> Micah Cowan wrote:
>
> broz wrote:
>>>> Hi,
>>>>i have a question about gnuscreen which I think is great
>>>> btw. I may have a hard time c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Grant wrote:
> On Sun, Jan 4, 2009 at 12:16 PM, Michael Grant wrote:
>> I have both a linux box and a freebsd box. I have just started using
>> screen on the linux box. There seems to be some very definite
>> differences in behavior between
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Jones wrote:
> Couldn't find anything in the usual repositories.
>
> Here's my current hardstatus line (length=190):
>
> hardstatus alwayslastline "%{+r wk}%H %{+b yk}%0` %{+b wk} %1` | %2` %3` |%4`
> %{+b wk}| %{+b wk}%l%{+b wk} |%{+b gk} %n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Wood wrote:
> On (16:32 19/12/08), Dave Wood put forth the
> proposition:
>> On (18:54 18/12/08), Dave Wood put forth the
>> proposition:
>>> I find after switching screens a few times that I get either
>>> ';screen' or
>>> ';xterm-xf86-v40' pri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave Wood wrote:
> I have a flashing block cursor set up because I find it very hard to see
> the normal _ underline cursor - expecially when searching through man
> pages etc.
>
> The problem comes when I run ncurses programs in screen. The cursor ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erik Osheim wrote:
> I sent this to [EMAIL PROTECTED] awhile ago (which I think I'm
> subscribed to) but still haven't seen it. So, I figure I'll send it to
> this list (which seems pretty active).
Are you sure you're subscribed? I saw it, and respond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> On Sat, 6 Dec 2008, Micah Cowan wrote:
>
>> As to FAQs, there's one on the wiki page that someone set up for the IRC
>> channel (apparently?). I should put a link to that on the gn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trent W. Buck wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>> screen sh -c "vim `find . -name '*.c' -o -name '*.cpp'`"
>> title vim
>
> FWIW, sh -c 'vim find . -name \*.c -o -name \*.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> Which reminds me -- in looking for docu on this subject and others, I
> found the gnu.org screen page, and the only thing there is links to the
> mailing list. Are there no official web-docs? FAQs? Or are they all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> Is it possible to define "viewer" commands in Alpine that would do
> either of the following:
>
> 1) Launch in a separate window and/or
> 2) set the title correctly?
>
> Right now, my shell seems to step in and want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zaphod wrote:
> Hi
>
> 1st of all, i am using screen for number of years now and like it very
> much.
> lately decided to upgrade my environment. So my question is.
>
> Using .screenrc file where wants to open window with vim. The vim should
> also
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(sorry, accidentally hit "Reply" instead of "Reply All")
Micah Cowan wrote:
> broz wrote:
>> Hi,
>> i have a question about gnuscreen which I think is great btw. I
>> may have a hard time conveying wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Lloyd wrote:
> The -X option seems like it's intended for this purpose, but it seems
> to be a no-op. The man page says "Note that this command doesn't work
> if the session is password protected." To my knowledge the session is
> not password prot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> All,
>
> I apologize if I've argued a bit fervently in the past for what I felt
> was a simple feature (i.e. support for screen to also use the "attach"
> password as a "lock" password on systems that do not support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sheepa.org wrote:
> * Since the playlist never gets cut when im writing in manually I'm
> thinking this is some kind of screen -X stuff problem? *
> * *
It's unlikely to be related to the actual "screen -X stuff" command.
It's possible that there's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
head0r wrote:
> Hi,
>
> i tried putting screen in a chrooted environment. I copied the
> /etc/passwd and the libs listed by "ldd /usr/bin/screen".
> But when i try starting the screen in the chroot, i get the following
> error message:
>
> getpwuid()
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Benoit ROUSSELLE wrote:
> but i was not able to have these commands to work:
> layout name "foo"
> layout load "name"
layout save "foo"
layout select "foo" :)
layout title "foo" <-- to change the name of the current layout.
See /case RC_LAYOUT:/ in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pia Mikeal wrote:
> Greetings,
>
> I am not sure if this is a bug in screen or something else, but
> screen seems to be a package I can take out of the equation and the
> problem goes away. Here is my issue, at the commandline, my virtual
> termi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> On Thu, 13 Nov 2008, Trent W. Buck wrote:
>
>> Micah Cowan <[EMAIL PROTECTED]> writes:
>>
>>> Dan Mahoney, System Admin wrote:
>>>> According to the manpage, screen call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trent W. Buck wrote:
> Are there any lurkers on the list that would care to chime in with
> useful examples on how they use LOCKPRG?
>
> A while back, what I wanted was the ability to blank the screen after
> two minutes of inactivity, and then *lock*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> According to the manpage, screen calls /bin/lock or whatnot -- there's
> no way through .screenrc to change this (why?)...and yet the output of a
> locked screen looks significantly different from when I use lock alon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Mahoney, System Admin wrote:
> hey, is there a way to customize the message displayed on the "lock",
> for example:
>
> Whether it was locked by time, or idle?
> What time it was locked?
> What HOST it's running on?
These could all be managed now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gorsuch, Ryan wrote:
>
> The manual indicates that I can bind several commands to a key using the
> "process" command but no examples or syntax are given.
>
> What I'd like to do is bind the sequence: "C-a s 1" to the commands:
> "split, focus, selec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Elliot wrote:
> Thanks for the help.
>
> Would this be correct?
>
> while true; do screen -S 19268 -X stuff "signon"\012; sleep 1m; done
Ah; actually, I don't believe octals are interpreted from the
commandline (a shortcoming, IMO). Anyway,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Elliot wrote:
> Hello,
>
> I am trying to send a remote command to an existing screen session:
>
> while true; do screen -S 19268 -X stuff "signon"; sleep 1m; done
>
> However, I need to send a new line (CRLF) after the command "signon".
Ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henry S. Thompson wrote:
> Micah Cowan writes:
>
>> Oh, is that the problem?
>
>> Screen has its own built-in "alternate screen buffers"; just add the
>> "altscreen" command to your ~/.screenrc.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henry S. Thompson wrote:
> Micah Cowan writes:
>
>> I'm not entirely sure I understand what the symptom is that you're
>> describing for running less under the screen-managed window, but it
>> sounds like it migh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henry S. Thompson wrote:
> I built screen 4.0.3 from source, with cygwin patches, on cygwin, with
> ncurses 5.7, and rxvt for my terminal emulator.
>
> The 'less' program has an irritating fault in this configuration which
> I can't figure out how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robin Lee Powell wrote:
> On Wed, Nov 05, 2008 at 02:39:13PM -0800, Micah Cowan wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Gokdeniz Karadag wrote:
>>> Hi,
>>>
>>> This i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gokdeniz Karadag wrote:
> Hi,
>
> This is more like a story, I am trying to automatically set "GNU screen
> window title" equal to the hostname that is connected by ssh.
This has been a recurring need, solved in various ways.
Thomas Adam just point
1 - 100 of 170 matches
Mail list logo
