FVWM: Another Shell for PipeRead?

[M***@gmx.de]

Hi!

The man page of FVWM says regarding the PipeRead command:

> This command is executed by /bin/sh as if you typed it on the command line.

This was not a problem until Debian Lenny. Since Debian Squeeze (and Wheezy currently),
/bin/sh is not a symbolic link to /bin/bash anymore but a symlink to /bin/dash.

I prefer my PipeRead commands interpreted by BASH, not by DASH
(because DASH for example does not know 'echo -e -n'), but I don't want
to change the global symlink '/bin/sh' for the whole system.

There is a command named 'ExecUseShell', but obviously, this has no effect
on PipeRead.

I could swap (outsource) my code into shell scipts and let PipeRead
call these scripts, but this isn't a nice solution for my taste.

Has anybody an Idea how to change the standard shell for PipeRead?

Thanks in advance,
Michael

[Michael Großer]

> Gesendet: Montag, 20. April 2015 um 12:52 Uhr
> Von: "Thomas Adam" <***@fvwm.org>
> An: "Michael Großer" <***@gmx.de>
> Cc: fvwm <***@fvwm.org>
> Betreff: Re: FVWM: Another Shell for PipeRead?
>
> On 20 April 2015 at 10:22, <***@gmx.de> wrote:
> > Hi!
> >
> > The man page of FVWM says regarding the PipeRead command:
> >
> >> This command is executed by /bin/sh as if you typed it on the command line.
>
> Yes, because we use popen() to do this. Re-designing this to use
> fork()/execle() is not worth it just because Debian use /bin/dash.
>
> > Has anybody an Idea how to change the standard shell for PipeRead?
>
> Use container scripts.
>
> -- Thomas Adam

Hm. OK.

I will do it.

Thank you for your answer and the explanation.


- Michael -