https://bugs.kde.org/show_bug.cgi?id=441692
--- Comment #5 from Christopher Yeleighton <[email protected]> --- (In reply to Dominik Haumann from comment #2) > From what I understand it's that we'd need to add another line edit for the > Output Path. > > Of course that can be done, but isn't it that you can do that already via > the arguments? You suggested already a way, maybe it can be simplified, e.g. > you could write a script that your just call an external tool. Some external tools, like gcc, allow giving the output file as an argument, some, like gzip, do not. Calling an interpreter just to redirect the standard output seems like an overkill for a standard redirection that should be done by the plug-in. It also makes the definition of the tool harder to understand. If the tool produces text output that is not excessive, it can be inserted into a new buffer and let the user decide what to do if it. If the output is binary, this method does not work: it must be saved to an actual file. Note that a tool cannot take input from a file either. But I have no use case for taking input from a file. -- You are receiving this mail because: You are watching all bug changes.
