Marco Mariani writes:
> The most difficult thing is using info (or emacs) to browse through the
> info file. I hate those hyperthings.
TeX it and print it out, then.
> Is there a way to refer to $HOME within FvwmM4 or Fvwm ?
>
> I'd like to include(`~/.fvwm-whatever'), because I often launch X from a
> directory that is not $HOME.
GNU m4:
File: m4.info, Node: Esyscmd, Next: Sysval, Prev: Syscmd, Up: UNIX commands
Reading the output of commands
==============================
If you want `m4' to read the output of a UNIX command, use `esyscmd':
esyscmd(SHELL-COMMAND)
which expands to the standard output of the shell command SHELL-COMMAND.
Prior to executing the command, `m4' flushes its output buffers.
The default standard input and error output of SHELL-COMMAND are the
same as those of `m4'. The error output of SHELL-COMMAND is not a part
of the expansion: it will appear along with the error output of `m4'.
Assume you are positioned into the `checks' directory of GNU `m4'
distribution, then:
define(`vice', `esyscmd(grep Vice ../COPYING)')
=>
vice
=> Ty Coon, President of Vice
=>
Note how the expansion of `esyscmd' has a trailing newline.
The builtin macro `esyscmd' is recognized only when given arguments.
Håvard Fosseng
--
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 Sat Aug 24 1996 - 16:41:20 BST