Re: FVWM: Piperead vs. Exec

From: Mikhael Goikhman <migo_at_cortext.co.il>
Date: Fri, 5 May 2000 01:00:01 +0300

On 04 May 2000 18:10:15 -0230, Neil Zanella wrote:
>
> I cannot see that Piperead would be any more useful than Exec.
> Could anyone give me an example of a useful Piperead command
> that cannot be implemented as an Exec command?

PipeRead and Exec are totally different commands, although they both start
shell commands. Exec is non-blocking, i.e. fvwm continues to run following
commands immideately without worrying about launched applications, it is
ideal for launching X applications. Contrary, PipeRead is blocking, i.e.
it waits until its shell command is finished *and* in addition executes
its standard output, as if it is fvwm native commands.

Examples (the second is for 2.3 versions, see fvwm-menu-xlock man page):

  PipeRead `echo "All ($USER_at_$HOST) Iconify"`
  PipeRead 'fvwm-menu-xlock --name MenuXLock --title "Lock Screen"'

Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Thu May 04 2000 - 17:03:36 BST

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