D28201: Add KIO::CommandLauncherJob to replace KRun::runCommand

[David Faure]

dfaure added a comment.


  (technically, connecting to &KJob::result is missing in the dolphin port, but unlike ProcessLauncherJob, CommandLauncherJob is very unlikely to fail. QProcess will only fail to start if we're out of resources for forking or if `sh` can't be executed... we don't detect bad shell commands, that happens after QProcess::start(). I wonder if it's worth connecting to the result signal of a CommandLauncherJob....)

REPOSITORY
  R241 KIO

REVISION DETAIL
  https://phabricator.kde.org/D28201

To: dfaure, apol, davidedmundson, nicolasfella, vkrause, broulik
Cc: kde-frameworks-devel, LeGast00n, cblack, GB_2, michaelh, ngraham, bruns
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20200322/f0b12127/attachment.html>