[Bug 272159] New: Many KDE applications that accept file arguments fail reading Bash process substitutions

[Dan Douglas]

https://bugs.kde.org/show_bug.cgi?id=272159

           Summary: Many KDE applications that accept file arguments fail
                    reading Bash process substitutions
           Product: kde
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: doug0213 at metnet.edu


Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

Process substitutions are generally mishandled by KDE applications.

Reproducible: Always

Steps to Reproduce:
Some examples:

$ kate <(xclip -o)
...snip...
kate(30848)/kio (KDirWatch) KDirWatchPrivate::removeEntry: doesn't know
"/dev/fd/63"

(Kate loads and shows a blank buffer)

$ kompare <(curl -s 'http://bugs.gentoo.org/attachment.cgi?id=268673') $(equery
w dev-lang/ocaml)

(no error, but only shows a blank file in place of curl output)

$ rekonq <(curl -s localhost)

Error: "When connecting to: file:///dev/fd/63"

$ okular <(man -t bash)
okular(1610)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(1610)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(1610)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(1610)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(1610)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
okular(1610)/okular (app) Okular::Document::openDocument: No plugin for
mimetype '"inode/fifo"'.

Okular pops up "Could not open /dev/fd/63"

The following does work correctly, but either should be fine. Not all programs
accept "-" nor is it as versatile:

$ man -t bash | okular -


Expected Results:  
Programs should read/write pipes as though they were files.

Process substitution creates a named pipe under /dev, runs a command, connects
stdout or stdin to the named pipe, and places the fd of the pipe in a
positional parameter of a command. This allows programs which read or write
files to do so directly to a command pipeline. The exact behavior is platform
dependent. The syntax is:
$ cmd <(cmds)
or
$ cmd >(cmds)

http://www.gnu.org/software/bash/manual/html_node/Process-Substitution.html#Process-Substitution

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.