It would be nice to be able to pass the current document, selected text, etc. to the stdin of a build command. This would be particularly useful for cases where you don't have a new file saved yet, but still want to lint the document (or part of it) for example.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013
What about a [custom command](https://geany.org/manual/index.html#sending-text-through-custom-commands) for that purpose?
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215545338
On 29 April 2016 at 06:02, Colomban Wendling notifications@github.com wrote:
Is it safe to replace the file with the lint output?
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215606455
Good point, it's not, yet one wants to see the output. So nevermind that suggestion, it wasn't worth anything.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215606812
This doesn't seem likely to have a significant use-case. In general lint should not be run without previously compiling the source successfully. An erroneous source file is likely to cause lint to emit many false messages. But generally compiling requires a file, since compilers use the extension to decide what to do.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215621545
@elextr I had something like JavaScript in mind actually
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215622402
Well I guess "somebody" will have to design how to configure build commands to send the file to stdin, and also actually implement the functionality.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215622914
No spoiler ahead, but a little time ago I was thinking of writing a all-purpose command spawner with all the missing features we currently have, including arbitrary placeholders, environment modifications, selectable stdin/stdout/stderr, etc. It should actually be fairly easy to implement the feature itself with the new spawn API we have, and it'd be a "mere matter" of writing a nice configurable UI for that. If I get time I'll try to work on that further.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215687217
@b4n don't forget to parse the output for file:line so its possible to jump to it by clicking on the output
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215688554
a neat design for that would require being able to customize the available action, so have easy scriptability… we'll see.
--- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1013#issuecomment-215688734
github-comments@lists.geany.org