🚀 go-pugleaf

In article <MUTS.93Jan7141241@PMCS.estec.esa.nl>, muts@estec.esa.nl (Peter Mutsaers) writes:
|> >>On Mon, 4 Jan 93 11:35:19 GMT, sinkwitz@ifi.unizh.ch (Rainer Sinkwitz) said:
|> 
|>   Rainer> One vote for olvwm, you get the virtual screens and much
|>   Rainer> more, and it's free !!!
|> 
|> One vote against olvwm. It is open look. (typing this on a SUN with
|> ^&*%#$ open look completely removed; I use plain X11R5 instead). Use
|> ctwm, it is like twm, thus completely customizable (the standard
|> customization is not very nice) but offers virtual screens as well. I
|> shall append my .ctwmrc file, which is quite nice:
|> 
|>  

 **example removed**

|> --
|> _________________________________________________________________________
|> Peter Mutsaers.         |================================================ 
|> muts@pmcs.estec.esa.nl  |        Quod licet bovi, non licet Jovi



I also love ctwm; but Peter's example .ctwmrc file didn't include an
example of another nice feature - the ability to place a new window
(or whatever) in a predetermined workspace. Here's what the man page
says:

Occupy { occupy-list }
         This  variable  specifies  which  window  occupy   which
         workspace at startup.

         Where occupy-list is a list entries of the form :

                   [Window]   win-name { wpsc1 wspc2 ... }
              or   Workspace  wspc-name {win1 win2 ... }

         Example :

              Occupy {
                             "xload"   {"all"}
                  Window     "xterm"   {"here" "there" "elsewhere"}
                             "xv"      {"images"}
                  WorkSpace  "images"  {"xloadimage"}
              }


BUT note that it doesn't matter when the window is called.




There is also a mapform for ctwm (shows map of all windows on all workspaces and
allows user to use mouse to manage these windows - simple to move windows from one
w'space to another and (of wanted) to warp cursor there)

Michael