Skip to main content
Clean up the answer to allow cleaning up the comments.
Source Link
Stephen Kitt
  • 481k
  • 59
  • 1.2k
  • 1.4k

As revealed in the comments, thisThis happens when a Meld window is already open. In that case, running meld again tries to use the existing Meld process; but that process can’t access the /dev/fd files which are used for the substitution...

There doesn’t seem to be an option to force Meld to use the “new” process, ignoring all others.

As revealed in the comments, this happens when a Meld window is already open. In that case, running meld again tries to use the existing Meld process; but that process can’t access the /dev/fd files which are used for the substitution...

There doesn’t seem to be an option to force Meld to use the “new” process, ignoring all others.

This happens when a Meld window is already open. In that case, running meld again tries to use the existing Meld process; but that process can’t access the /dev/fd files which are used for the substitution...

There doesn’t seem to be an option to force Meld to use the “new” process, ignoring all others.

Source Link
Stephen Kitt
  • 481k
  • 59
  • 1.2k
  • 1.4k

As revealed in the comments, this happens when a Meld window is already open. In that case, running meld again tries to use the existing Meld process; but that process can’t access the /dev/fd files which are used for the substitution...

There doesn’t seem to be an option to force Meld to use the “new” process, ignoring all others.