Re: Get rid of windows limit in 'window'?
On 6/15/08, Pieter Verberne <[EMAIL PROTECTED]> wrote: > On Sun, Jun 15, 2008 at 12:05:34PM +, rivo nurges wrote: > > On Sun, Jun 15, 2008 at 01:44:12PM +0200, Marc Espie wrote: > > > > I still don't understand the current craze about window, since > > > it doesn't have the one killer feature of screen, namely the > > > ability to attach/detach sessions at will... > > > > window(1) addicts can use misc/dtach from ports. I haven't used > > this combination myself but in theory it should work. > > > > Also misc/tmux looks very promising. > > > and what about dvtm? > http://www.brain-dump.org/projects/dvtm/ no detach.
Re: Get rid of windows limit in 'window'?
On Sun, Jun 15, 2008 at 01:44:12PM +0200, Marc Espie wrote: > On Sat, Jun 14, 2008 at 06:18:31PM -0700, F. Caulier wrote: > > I just discovered 'window' in base, a very usefull > > tool! > > I still don't understand the current craze about window, since > it doesn't have the one killer feature of screen, namely the > ability to attach/detach sessions at will... $ dtach window or just $ dtach :) Ow, it is GPL... Pieter Verberne
Re: Get rid of windows limit in 'window'?
On Sun, Jun 15, 2008 at 12:05:34PM +, rivo nurges wrote: > On Sun, Jun 15, 2008 at 01:44:12PM +0200, Marc Espie wrote: > > I still don't understand the current craze about window, since > > it doesn't have the one killer feature of screen, namely the > > ability to attach/detach sessions at will... > > window(1) addicts can use misc/dtach from ports. I haven't used > this combination myself but in theory it should work. > > Also misc/tmux looks very promising. and what about dvtm? http://www.brain-dump.org/projects/dvtm/
Re: Get rid of windows limit in 'window'?
On Sun, Jun 15, 2008 at 01:44:12PM +0200, Marc Espie wrote: Hi! > I still don't understand the current craze about window, since > it doesn't have the one killer feature of screen, namely the > ability to attach/detach sessions at will... window(1) addicts can use misc/dtach from ports. I haven't used this combination myself but in theory it should work. Also misc/tmux looks very promising. -- rix http://www.ripe.net/perl/[EMAIL PROTECTED]
Re: Get rid of windows limit in 'window'?
On Sat, Jun 14, 2008 at 06:18:31PM -0700, F. Caulier wrote: > I just discovered 'window' in base, a very usefull > tool! > I was used to install 'screen' to get a terminal > multiplexer but as I found 'window' which gives me > multiplexing without 'screen's' bloat and restrictive > license. I still don't understand the current craze about window, since it doesn't have the one killer feature of screen, namely the ability to attach/detach sessions at will... I mean, probably like a lot of people, my main use of screen is to have interactive sessions I can keep around from login to login, or around a flaky network connection. Nothing as unpleasant as having a build fail just because your network timed out and make got SIGHUP'ed.
Re: Get rid of windows limit in 'window'?
F. Caulier wrote: > I just discovered 'window' in base, a very usefull > tool! > I was used to install 'screen' to get a terminal > multiplexer but as I found 'window' which gives me > multiplexing without 'screen's' bloat and restrictive > license. > > Just two questions: > > Is there an example.windowrc available somewhere or > would someone be so kind a send me his own customized > one? > I already searched the web on this but couldn't find > much. yes, the name "window" is highly unfortunate when it comes to using search engines, as I recall. Here is something I ultimately came up with, based on something I found...don't ask me where or how. It is admittedly imperfect, but it did the job. /home/nick $ more .windowrc close all myrows = $nrow - 2 mycols = ( $ncol / 2 ) - 1 window ( 1, 1, $myrows, 80 ) # "80" in following command should be $mycols, but we'll just chop long lines window ( 1 , $mycols + 2 , $myrows, 80) label ( 1, "dvd0 (top drive)" ) label ( 2, "dvd1 (bottom drive)" ) write 1 "sleep 1 ; chkdrv 0\n" #write 1, $mycols $myrows write 2 "sleep 6 ; chkdrv 1\n" it creates two windows in the current screen, with a split down the middle. It then starts a program called "chkdrv" with a different parameter in each of the windows. It's a starting point. And no, I don't really recall what the comment meant. :) This was for an app which burned a pair of DVDs regularly, and I wanted to have the final output of each burn to be left on the screen. I did ultimately replace this use of "window" with running X, auto-launching a pair of xterms running the app. I found it easier for normal users to see and look through the output. Nick.
