Project Build Parameters

[ScrKiddle]

I open a Markdown-Project.
The project should get compiled with Pandoc https://pandoc.org/MANUAL.html .
The command looks some thing like the following.
pandoc pandoc.md --from markdown --to html5 --standalone --template=Pandoc_Template.html --toc --syntax-highlighting=none -o output.html
Pandoc is in the system path settings and working from any where in the CMD.

Now i enter in the Project settings the following build or compile commands:
Command: pandoc
Argument: --from markdown --to html5 --standalone --template=Pandoc_Template.html --toc --syntax-highlighting=none -o output.html
Selected File(s): pandoc.md

when i click the build command in the project-menu the output window at the bottom opens and absolutely nothing happens, the output-windw shows nothing, no error no success, no message, pandoc does not build the html-file.

What would be expected:

RJ TextEd should add the selected file after the command.
RJ TextEd should add the given arguments after the selected files.
RJ TextEd should run pandoc which is in the path settings, with the selected file and the given arguments.

May a better solution would be to allow users to use some fancy parameters like active opened file %ActiveFile, may with different flavor like only the file name or the file name with absolute path or such things, and the same options for the selected files which then get build by running the given command over all selected files.
This could be very handy if a command des not expect the file to build as its first parameter.

A file name option would also be very handy to specify the output file, it could dynamically be the same name as the input file but without the file extension, in this case it may would be -o %ActiveFileNoExt%.html .

Maybe there could also be an option to run the command in the directory of the active file, or may in some other working directory or the project-directory.

I thing many compile systems would profit from such options.

[Rickard Johansson]

If you only want to convert the active document - you should probably use tools instead. Tools does everything you want (and more).

Open the "Tools" menu and select "Configure tools...".

[ScrKiddle]

If you only want to convert the active document - you should probably use tools instead. Tools does everything you want (and more).

Open the "Tools" menu and select "Configure tools...".

Yes this is a quick fix that works, thanks for that.

Code: Select all

Menu-Text: PanDoc: MD > HTML
Type: Execute (*.exe|*.com|*.bat|*...)
Command: pandoc
Start-Directory: [CurrentFileDir]
Arguments: "[FileDir]\[FilePath]" --from markdown --to html5 --standalone --template=Pandoc_Template.html --toc --syntax-highlighting=none -o "[FileDir]\[FileTitle].html"
[x] Save file if changed
[x] Execute as DOS-command and catch output
[x] output is in UTF-8 format
Open output window/new document
 > only if file-output or exit-code 0

It works perfect, how ever it is a global command and not a per-project command.
If you have multiple projects with use similar but different arguments, the global tools menu will soon get huge.
It is possible to configure per-project commands but there you can only configure three user-commands and you cant use the very handy variables like [FileDir]\[FilePath], [FileDir]\[FileTitle], [CurrentFileDir] and so on.

But even one an the same project could need more than three similar but not the same arguments, and multiple projects could need more than three user-tools, while the per-project command do not belong to the global user-tool commands.

Hw ever, this quick-fix to use the global commands works very well.

Thanks