Re: preventing the leading space in process substitution

[Angel Olivera <redondos@xxxxxxxxxxx>]

On Tue 09.Sep.08 15:41, martin f krafft wrote:
> I am trying to use <(...) to pass a file to a command that expects 
> the file argument following an equal sign, like so:
>
>  mycommand -file=/path/to/some/file
>
> The problem is that
>
>  mycommand -file=<(...)
>
> seems to yield
>
>  mycommand -file= /proc/self/fd/16
>
> with the space before the filename. How do I prevent that?

Also, how would one use =() in this case?

One alternative is:

  mycommand -file=$(print =(...))

but there must be a nicer way.

--
redondos

Attachment: signature.asc
Description: Digital signature