On Fri, Feb 19, 2021 at 02:30:15PM EST, david kerns wrote:
> just type screen ... if you're in a brand new window with no other text..
> you may not notice the subtly
> hit return a few times on a new window.. then type screen .. should be a
> fresh window.. then exit, and you'll get your old scree
just type screen ... if you're in a brand new window with no other text..
you may not notice the subtly
hit return a few times on a new window.. then type screen .. should be a
fresh window.. then exit, and you'll get your old screen back (as screen
exits)
On Fri, Feb 19, 2021 at 12:24 PM M.R.P. z
On 2/19/21 7:50 PM, M.R.P. zensky wrote:
> Hello I have installed screen on linux but how do you start screen?
>
In a terminal. Usually, I add the options -D -r when I run it.
See "man screen"
Once it is running, there won;t be much indication that it is runningm
though you can try,
sc
Hello I have installed screen on linux but how do you start screen?
Some may recall my previous trys, and failures, to create macros using screen
commands.
I was using exec tied to a bindkey in screenrc to run a shell script which
contained a series of the stuff commmands to send instructions to
the current application.
It didn't work. By experiment I
ev/ttyUSB3 57600,cs8' I find that AT
> commands are never recognized - I get no response from the modem as if
> it didn't catch the right line termination.
>
Now I feel rather silly. This was due to me using screen within a
screen session in which case screen starts translating C
On Tue, Apr 18, 2017 at 1:12 AM, Amadeusz Sławiński wrote:
> On Mon, 17 Apr 2017 08:00:01 -0700
> Tim Harvey wrote:
>
>> Greetings,
>>
>> I've often asked users I'm helping with modem support on Linux to use
>> GNU screen to issue AT
>> commands to modems to get their details (ie ATI), however I'
On Mon, 17 Apr 2017 08:00:01 -0700
Tim Harvey wrote:
> Greetings,
>
> I've often asked users I'm helping with modem support on Linux to use
> GNU screen to issue AT
> commands to modems to get their details (ie ATI), however I've noticed
> this doesn't work for me anymore on perhaps newer modems
Greetings,
I've often asked users I'm helping with modem support on Linux to use
GNU screen to issue AT
commands to modems to get their details (ie ATI), however I've noticed
this doesn't work for me anymore on perhaps newer modems and I'm
guessing its related to a missing stty setting relative to
On Thu, 19 Jan 2017, Tim RENAUD wrote:
Hello,
Before I get into details, I just want to confirm this is the mailing
list I use to discuss my issue?
That depends, what is your issue? This list is about using gnu-screen,
the terminal multiplexer.
--
Michael Parson
Pflugerville, TX
KF5LGQ
___
Hello,
Before I get into details, I just want to confirm this is the mailing list I
use to discuss my issue?
___
screen-users mailing list
screen-users@gnu.org
https://lists.gnu.org/mailman/listinfo/screen-users
On Thu, May 26, 2011 at 11:13 AM, Kipling Inscore wrote:
> While screen is running, the tty (at least if it's a pts) from which
> screen was launched still exists (and is still owned by user, not
> root) but isn't listed by w or who. Perhaps it's something to do with
> how w and who work or what
r, not
root) but isn't listed by w or who. Perhaps it's something to do with
how w and who work or what happens on the tty from which screen was
launched while screen is running.
I would recommend investigating w and who (unless someone else on the
screen list has a suggestion).
> On
On Tue, May 24, 2011 at 11:54, John K. Sherwood wrote:
> Hello all,
> I've been using screen for a while, but recently one of our system
> administrators noticed an interesting quirk of screen that made me wonder.
> It seems that if you run 'screen' after running
Hello all,
I've been using screen for a while, but recently one of our system
administrators noticed an interesting quirk of screen that made me wonder. It
seems that if you run 'screen' after running 'sudo bash', the system (as shown
by the utilities 'w
"Jae Norment" writes:
> I fairly pretty uncomfortable running any of the solutions presented
> here: I know enough about C/C++ to know that it's pretty easy to write
> code that can be pretty destructive to an instance of an operating
> system. The last thing I want to do is bring down the produ
creen. I am not sure where to start but
> the current problem is that the output characters for the border of the
> character based menu does not display as it should using screen. I have some
> screen dumps in jpg format but i am not sure if this can be posted to the
> mailing list.
>
&g
start but
the current problem is that the output characters for the border of the
character based menu does not display as it should using screen. I have some
screen dumps in jpg format but i am not sure if this can be posted to the
mailing list.
I do know the following:
1.) PASSPORT to WEB does
usually read most of what happens, and the
original isn't destroyed in the process, so I always have that, too...
-Original Message-
From: Micah Cowan [mailto:mi...@cowan.name]
Sent: Friday, January 30, 2009 3:24 AM
To: Jae Norment
Cc: screen-users@gnu.org
Subject: Re: using scre
Hi Jae,
I spent several hours trying to tackle this same issue. I wanted to
share what I found out. I found 2 programs that do a pretty good job in
removing the escape codes:
1. Ansifilter: http://www.andre-simon.de/doku/ansifilter/ansifilter.html
2. Ansi2txt: http://sourceforge.net/proj
-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
sed 's/[^[:space:][:print:]]//g'
or sg similar might do the trick
i once wrote a very small C program (perl was too slow) to check a file for
any non-printable bytes; it would probably be trivial to write a version
that would output printable bytes instead
On Fri, Jan 30, 2009 at 5:52 AM, Jae No
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 that I can open it in a text editor. I've been told that
a little perl co
On Wed, Aug 06, 2008 at 07:44:32AM -0700, Ken Steen wrote:
> I have a small file manager that uses screen to open programs in new
> screen windows. It works correctly except when using screen on a
> directory mounted with sshfs or when using screen on a directory that is
> a symbol
On Sun, Aug 10, 2008 at 09:18:21PM -0400, Andy Harrison wrote:
> On Wed, Aug 6, 2008 at 10:44 AM, Ken Steen <[EMAIL PROTECTED]> wrote:
> > I have a small file manager that uses screen to open programs in new
> > screen windows. It works correctly except when using scre
On Sun, Aug 10, 2008 at 09:18:21PM -0400, Andy Harrison wrote:
> Although completely unrelated to screen, I had similar permission
> problems with one of my sshfs mounts. I finally solved it with the
> following sshfs params: [... -o allow_root]
Hmm -- perhaps this is related to screen being set-
On Wed, Aug 6, 2008 at 10:44 AM, Ken Steen <[EMAIL PROTECTED]> wrote:
> I have a small file manager that uses screen to open programs in new
> screen windows. It works correctly except when using screen on a
> directory mounted with sshfs or when using screen on a directory that
On Wed, Aug 06, 2008 at 07:44:32AM -0700, Ken Steen wrote:
> If [my] program is started with 'screen program-name', and the
> current directory is a symbolic link to another directory opening a
> new screen window changes the pwd to the directory that is pointed
> to by the symbolic link instead of
I have a small file manager that uses screen to open programs in new
screen windows. It works correctly except when using screen on a
directory mounted with sshfs or when using screen on a directory that is
a symbolic link. If the program is started with 'screen program-name',
and t
On 8/6/07, Jean Jordaan <[EMAIL PROTECTED]> wrote:
> Hi Javier
>
> > > They moved me from a jailshell to a normal shell (which I much
> > > appreciated)
> > Oh, this is a new information. It is posible that you was in
> > a restricted environment (chroot or similar), without access
> > to a /dev/pt
On 8/6/07, Jean Jordaan <[EMAIL PROTECTED]> wrote:
> Hi Javier
>
> > Which operating system?
>
> Linux 2.6.9-42.0.3.ELsmp #1 SMP Fri Oct 6 06:28:26 CDT 2006 x86_64
> x86_64 x86_64 GNU/Linux
>
> > In linux, you must mount devpts filesystem
> > in order to get pseudo-terminals in /dev/pts directory.
Hi Javier
> > They moved me from a jailshell to a normal shell (which I much
> > appreciated)
> Oh, this is a new information. It is posible that you was in
> a restricted environment (chroot or similar), without access
> to a /dev/pts directory
I only realised I was in a jail after they told me.
Hi Javier
> Which operating system?
Linux 2.6.9-42.0.3.ELsmp #1 SMP Fri Oct 6 06:28:26 CDT 2006 x86_64
x86_64 x86_64 GNU/Linux
> In linux, you must mount devpts filesystem
> in order to get pseudo-terminals in /dev/pts directory. Check /etc/fstab
[EMAIL PROTECTED] [~]# cat /etc/fstab | grep pts
Hi there
On a box where I have a shell account, I get this:
[EMAIL PROTECTED] [~]# screen
Cannot access '/dev/pts/0': No such file or directory
Is there any way around that? How should the system be configured to
allow me to use screen?
--
jean . ..
34 matches
Mail list logo