Re: FVWM: Re: Re: Tcl, fvwm, etc.

From: Albrecht Kadlec <albrecht_at_auto.tuwien.ac.at>
Date: 07 May 1998 11:24:07 +0200

Jason L Tibbitts III <tibbs_at_hpc.uh.edu> writes:

> >>>>> "BM" == Brady Montz <bradym_at_cs.arizona.edu> writes:
>
> BM> I'd even go so far to say that I think we should release the current fvwm, and
> BM> make scwm fvwm version 3. Since scwm looks like what a lot of people would
> BM> like fvwm to become, and renaming scwm to fvwm3 would give them instant name
> BM> recognition and a large user/tester base, it could be a good thing for
> BM> everybody. The only issues would be political (which often are the hardest to
> BM> overcome).
>
> There was a big discussion about this on fvwm-workers a while back;
> unfortunately I doubt that this will ever happen. I gave the same argument
> about inheriting the FVWM user base that you did, but it didn't fly.

well more time has passed, and I might switch to scwm too. Maybe others
will follow.

This looks familiar to the minix discussion list, where they asked
"where've all the people who supplied patches gone to"

They'd gone Linux'.

If we all wait for the conversion tools to be written, we might wait a long
time.

I've rewritten my .fvwmrc several times so far. (1.24-> 2.0 -> extensions)
before that I had a .mwmrc, .twmrc & others.

I think I'll add a .scwmrc as soon as possible.
-- 
Albrecht Kadlec
Vienna University of Technology / Department of Automation
----------------------------------------------------------
The chicks are getting cheaper on the not so common market
Stockpile experience before the blonde hairs turn to grey  -- Marillion
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu May 07 1998 - 04:24:55 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:38:01 BST