On 12/23/2022 3:53 AM, Lucas Vieites via Users wrote:
Thank you, Lex.
I have signed up and written a small howto with the successful
instructions: https://wiki.geany.org/howtos/win32/build-command
Kind regards,
--
*Lucas Vieites <https://namedrop.io/lucasvieites>*
Blog @ codexion.com <https://blog.codexion.com/>
LinkedIn <https://www.linkedin.com/in/lucasvieites>
I hate to complicate things, but it's a little more complex than that.
So far, in my experience, the *only* time I have needed to wrap a build
command into the cmd.exe shell was with this one command in which I
attempted to run the "python -m markdown %f > %e.html" command. All
other build commands have worked just fine without being wrapped in a
shell. For example, if I compile a markdown file using Pandoc or
Darkslide, I can run the command directly from inside Geany without a
shell. Only this unique command required the shell.
I suspect the problem is with the ">" character. With that character in
the build command, Geany seems to stop executing the command once it
comes across that character. It appears that the ">" needs a cmd.exe
shell in order to be processed. The Python build command uses the ">" to
output to a file. Neither Pandoc nor Darkslide use the ">" character for
file output; therefore, they don't require a shell.
All that is to say that it is perhaps a little overly-simplistic to
imply that all build commands in Geany running in Windows require the
cmd.exe shell as they don't. But, it's useful to have the information
available so users like me can have something more to experiment with.
Virgil
_______________________________________________
Users mailing list -- users@lists.geany.org
To unsubscribe send an email to users-le...@lists.geany.org
