On Wed, May 04, 2005 at 06:34:32PM +0200, Richard Levitte - VMS Whacker wrote:
> In message <[EMAIL PROTECTED]> on Wed, 4 May 2005 09:22:38 -0700, Gary Kline
> <[EMAIL PROTECTED]> said:
>
> kline> One thing that may help ctwm grow is more documentation
> kline> with examples like yours about with accompanying
> kline> screenshots. --I find docs with *examples* the best
> kline> way to go. For example, some man pages list umpteen
> kline> switch options with thumbnail summaries; but having
> kline> just a few EXAMPLE offerings at the bottom is a
> kline> significant plus++.
>
> So basically, you want a cookbook section...
Something like that. If ctwm has a /usr/local/share/doc/ctwm
directory, a few pages of html with thumbnails could show,
could serve as examples.
Last fall I gave a presentation of ctwm to the Seattle BSD
Users Group. No slides, just examples. It went over well.
And I'll put my sweat where my fingers are and offer to
help write up a few examples.
>
> kline> A final note concerns having xterms in as many workspaces
> kline> as desired. I have 10 workspaces on most of my platforms:
> kline> ones for "Mail", "Programming", "Writing", "Broswer",
> kline> and so on. I wanted at least two xterms in each w-space,
> kline> but ctwm kept putting everything in my first workspace,
> kline> "SysAdmin". There are probably other ways of accomplishing
> kline> this, but I discovered that my linking xterm -> mailxterm
> kline> and "ln xterm browserxtem" and editing ~/.ctwmrc
> kline> did the trick.
>
> You're doing this with the Occupy variable, right? Isn't there a way
> to tell an xterm to have a specific name for you to trigger on?
>
Sorry, could you rehrase your second question? Yes, I
have this hack in the Occupy {} section. Example is:
Occupy
{
# Evidently the prefix term ``Window'' required.
Window "writingxterm" {"Writing"}
Window "xterm" {"NetSysadmin"}
Window "progxterm" {"Programming"} # Java pops up here, too.
Window "ns1xterm" {"SageAdmin"} # DNS server
Window "otherxterm" {"OthersAdmin"}
####Window "top" {"SageAdmin"}
Window "xcpustate" {"System_I"}
"sys1xterm" {"System_I"}
......
"sys2rxvt" {"System_II"}
"xperfmon++" {"System_II"}
"sys2xterm" {"System_II"}
Window "browsexterm" {"Browser"}
Window "scratchxterm" {"Scratch"}
Window "mailxterm" {"Mail"}
Window "xlbiff" {"Mail"}
}
Works like a charm :-)
enjoy!
gary
PS: If anyone else has any off-beat tricks or nifty
howto's, please share... .
--
Gary Kline [EMAIL PROTECTED] www.thought.org Public service Unix
