A future version of screen will have a feature that will make screen
itself slightly less obtrusive. It will not fix the issue of C-a a a
a a [space], nor will it allow you to grab non-screen'd processes
into screen, but it will make starting a new screen session
(reattaching, actually) mor
On Tue, May 16, 2006 at 04:00:55AM EDT, Stephane Chazelas wrote:
> On Mon, May 15, 2006 at 10:34:46PM -0400, cga2000 wrote:
> [...]
> > > Nikolai's entry is:
> > >
> > > screen-256color|VT 100/ANSI X3.64 virtual terminal,
> > > am, km, mir, msgr, xenl,
> > > cols#80, it#8, lines#24
In my main use model, I'm multiplexed at multiple levels. I often have more
than one computer going (meaning two keyboards, two mice, two monitors). I
then usually run virtual desktop managers, giving me 4 to 6 desktops. I then
open up a bazillion xterms, because I generally prefer to have ev
I just do everything in screen. But if you're tired of doing C-a
space to change screens, then just keep to one window in screen... ;)
(To me, if you've got more than one screen, then you've got a reason
to use screen all the time anyway...)
"Aaron Davies" <[EMAIL PROTECTED]> writes:
> Yeah, p
While we're on the subject of feature requests, I would love to see an
official cygwin version of screen. I'm stuck using windows at work,
and I really miss screen.
--
Aaron Davies
[EMAIL PROTECTED]
___
screen-users mailing list
screen-users@gnu.org
ht
Yeah, pretty much. I got tired of going "ctrl-a a a a a " to
change screens. Anyone here know the Telnet Song, by Guy Steele and
Knuth? Screen is the modern incarnation. :-)
These days, my standard .*profile finshes up with a prompt asking me
whether I want to run screen or not, and executes it a
Phil,
I tried something like that once and found it too annoying. Mainly, I ran
into the oddball sorts of TERMCAP / backspace / etc. issues too often when
logging in from "strange" hosts. Also, what happens when you ssh from host A
to host B? If every session I have open is runs screen, it
* Joe Zbiciak <[EMAIL PROTECTED]> [2006-05-16 06:34 -0700]:
> If screen develops the capability to import TTY FDs from another
> process, then the answer may be as simple as a wrapper around your shell
> that does little more than hold the FDs for your TTY, and pipes them
> through.
But then you'd
On Tue, May 16, 2006 at 08:37:14AM -0400, Aaron Davies wrote:
> A related feature I'd love to see implemented some day is the ability
> to import a non-screen process into screen. For example, I might start
> a compilation or a download in a normal shell, realize I have to go
> somewhere, and want
"Me too!"
Freaky thing is, this *may actually be possible*.
If screen develops the capability to import TTY FDs from another process, then
the answer may be as simple as a wrapper around your shell that does little
more than hold the FDs for your TTY, and pipes them through. (Well, it'd al
On May 16 08:37, Aaron Davies wrote:
> On 5/16/06, Michael Schroeder
> A related feature I'd love to see implemented some day is the ability
> to import a non-screen process into screen. For example, I might start
> a compilation or a download in a normal shell, realize I have to go
> somewhere, an
On 5/16/06, Michael Schroeder
<[EMAIL PROTECTED]> wrote:
On Tue, May 16, 2006 at 02:17:06AM -0300, Henrique Niwa wrote:
> hi,
>
> Is there a way, to incorpore a second session to the
> current one, i mean joining the windows created by the
> first session, into the working one
Not at the moment.
On Tue, May 16, 2006 at 02:17:06AM -0300, Henrique Niwa wrote:
> hi,
>
> Is there a way, to incorpore a second session to the
> current one, i mean joining the windows created by the
> first session, into the working one
Not at the moment. It is also not easy to implement, screen would
have to se
On Mon, May 15, 2006 at 10:34:46PM -0400, cga2000 wrote:
[...]
> > Nikolai's entry is:
> >
> > screen-256color|VT 100/ANSI X3.64 virtual terminal,
> > am, km, mir, msgr, xenl,
> > cols#80, it#8, lines#24, colors#256, pairs#32767,
> > bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[
14 matches
Mail list logo
