Re: FVWM: Two Questions About Menus

From: Greg J. Badros <gjb_at_moa.cs.duke.edu>
Date: Tue, 18 Jun 1996 11:18:51 -0400 (EDT)

> >>>>> "Bob" == misha21 <misha21_at_ihgp.ih.att.com> writes:
>
> Bob> Also while looking thru the archives, I noticed a reference to an olvwm
> Bob> feature that will create a menu from a directory of executables (e.g.
> Bob> $HOME/bin). Is there any plan for this feature.
>
">" == Chuck
> Sort of. There will probably be a way to read the output of an
> executable, so you could make a small shell script to create the menu
> entries from a directory's contents. I plan to put that in the next
> beta, which is only one away from 2.1 if all goes well, although I am
> trying to minimize the amount of new stuff going it between now and
> then, so it might wait until slightly after 2.1 is released. Still
> haven't fully decided...
>

I don't know how minimal people want fvwm to be, but this sort of thing is
already do-able with m4. eg.

  define(`a_temporary_file',maketemp(`TMPDIR/fvwmincludedXXXXX'))
  syscmd(`system-command with options >' a_temporary_file)
  include(a_temporary_file)
  syscmd(rm a_temporary_file)

Of course, then you need to use m4, and it's not as clean as it could be
(though you could write a macro to clean it up! :-) ), but I use this
technique multiple times in my .fvwm2rc.* files. BTW, m4 does *not* have
any asynchronous issues like the discussion about the Read command pointed
out for it. You just have to learn m4, which can take a couple hours to
get comfortable with.

> Bob> One final thing. I would like to thank you Chuck and all of the
> Bob> providers for this wonderful window manager. I really don't know
> Bob> how I ever functioned here at work without it.
>
> No problem. I felt the same way after I started using fvwm.

Me too!

Greg J. Badros 8816 Nesbit Ave N., Apt 303
gjb_at_cs.duke.edu Seattle, WA 98103-4067
http://www.cs.duke.edu/~gjb voice 206/528.7513 fax 206/523.9328



--
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 Tue Jun 18 1996 - 10:34:42 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:59 BST