Thank you (and others) for your replies. I appreciate the fact that you were
trying to help, but I see now that I wrote my question in such a way to make
it seem like I was a clueless newbie.
Let me try to restate the question. I know about resize handles. It is true
that if you resize using the resize handles, you can shrink a window without
having to grow it first. I failed to explain that I normally use resize from
a mouse binding. I do this very simply, using the following in my .fvwm2rc:
Mouse 2 WFSTI MS Resize
This allows me to start a resize operation with the cursor anywhere on a
window, by pressing meta-shift-button-2. (I find modifier key + button
combinations much faster to use than having to first seek out the appropriate
window frame/border element. It's a big win for operations like iconifying
and pushing/popping windows.)
What I find annoying is that after I press meta-shift-button-2 on a window, I
cannot resize it until I slide the cursor to the edge of the window and
actually make the window *larger*. Then I can strink it. I wish it were
possible to avoid that, and start the resize operation right away, without
first moving to the window edges.
Another list reader (Chris Siebenmann) understood what I meant in my original
question, and said that this is probably a hardcoded feature of fvwm. If so,
then I guess there is no configuration option that would change the behavior,
and it would require modifying the C code (which I wouldn't mind trying, if I
only had the time....).
--
Mike Hucka --- hucka_at_umich.edu --- http://ai.eecs.umich.edu/people/hucka
--
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 Sep 10 1998 - 12:01:09 BST