>>>>> "Rob" == Robert Nation 885-9815 <rnation_at_mansvr.sanders.lockheed.com> writes:
>> Honestly, I don't care if fvwm can look like any other window managers
>> or not. I like fvwm's look the way it is, but it was the other
>> features (and the fact that it was so small) that made me want to use
>> it initially. And I plan to keep it that way - as small as possible
>> and as powerful as possible too, only adding things to enhance it's
>> "value" without bloating it.
Rob> Just a historical side-note...
Rob> The original versions of fvwm had the top corners merged with the
Rob> buttons, and the title-bar merged with the top side-bar, so that
Rob> the top of the window looked more or less like the bottom, but
Rob> fatter. I liked it, but several people sent patches to make it
Rob> look like the current scheme, so I figured, its time to switch...
Sounds interesting. Just out of curiosity, what version # did that
change in?
Rob> Anyway, it would probably be genuinely useful to modify fvwm to
Rob> gracefully acept malloc and window creation failures than to make
Rob> it have more border styles.
Agreed, and actually I think there are a lot of other things that fall
into the "more important than more border styles" category right now.
I'm going to try and do some of them over my vacation next week.
Rob> Right now, when you run out of swap space, its likely that fvwm
Rob> will die, instead of just some user-application. This seems kind
Rob> of bad, even if it doesn't generally happen much.
Yeah, that should probably be handled a little better...
Rob> (Does anyone know if the X server handles malloc failures well?
Rob> If not, there's not much point in fixing fvwm...)
Good question. No clue here.
Chuck
--
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 Mon Dec 18 1995 - 10:58:47 GMT