In message <rjray-9702280030.AA001823633_at_snakepit.ecte.uswc.uswest.com>, "Randy
J. Ray" writes:
>> I use:
>>
>> + "Terminal" Exec exec xterm
>>
>> Which seem to do what you want?
>
>That will work, yes, but it seems like Fvwm should prepend "exec" automaticall
>y
>when processing an Exec command. I understand using a shell (environment
>variable expansions, etc.), but you don't expect to be using that top-level
>shell for anything afterwards-- why not always use exec?
If the user wants to do more then one action, like
Exec xset s blank ; xset s activate ; xlock ; xset s noblank
If you don't have anything like that you could try
doing:
ExecUseShell sh exec
I'm not sure if it would work, because I'm not sure if fvwm will
look for a shell named sh space exec, or for a shell called sh
and pass it exec and whatever comes on the Exec line.
--
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 Fri Mar 28 1997 - 08:58:22 GMT