Hard-coding to 'kate' is not a good idea. It's better to find a way to determine the default application for "*.txt" on the used linux desktop or on Windows or on Mac OS X.
QDesktopServices::openUrl() opens the file with the default application. Maybe we can check Qt's source code here to see how the default application is determined or used an already available function in Qt or in KF5.

In D12721#258801, @asemke wrote:

Hard-coding to 'kate' is not a good idea. It's better to find a way to determine the default application for "*.txt" on the used linux desktop or on Windows or on Mac OS X.
QDesktopServices::openUrl() opens the file with the default application. Maybe we can check Qt's source code here to see how the default application is determined or used an already available function in Qt or in KF5.

But if default application for txt is vim? Or nano? Or another console editor? So, maybe better add editor option to R backend setting?

In D12721#258802, @sirgienko wrote:

In D12721#258801, @asemke wrote:

Hard-coding to 'kate' is not a good idea. It's better to find a way to determine the default application for "*.txt" on the used linux desktop or on Windows or on Mac OS X.
QDesktopServices::openUrl() opens the file with the default application. Maybe we can check Qt's source code here to see how the default application is determined or used an already available function in Qt or in KF5.

But if default application for txt is vim? Or nano? Or another console editor? So, maybe better add editor option to R backend setting?

Let's use Cantor's ScriptEditorWidget which is based on KTextEdit that is available together with KF5. This editor is already used in CantorPart::showScriptEditor(). We can extend this widget/editor later if need and use it for everything script related. For BUG 339127 we'll need to compile this script editor as a stand-alone executable and use it in runCommand(). Let's use maybe cantor_scripteditor as the name for this new executable similar to cantor_rserver, etc.

In D12721#258808, @asemke wrote:

Let's use Cantor's ScriptEditorWidget which is based on KTextEdit that is available together with KF5. This editor is already used in CantorPart::showScriptEditor(). We can extend this widget/editor later if need and use it for everything script related. For BUG 339127 we'll need to compile this script editor as a stand-alone executable and use it in runCommand(). Let's use maybe cantor_scripteditor as the name for this new executable similar to cantor_rserver, etc.

OK, i will try to do it soon.