Luis Rivera
Luis Rivera
> For anyone who's still looking for a solution for arm devices, _(I did not try the Arch way cited above and don't know if it will or will not...
the system was designed on a *nix, which assumes a (soft?) link to the lunamark modules in the `lunamark` file to the main lunamark directory; in windoze you need to...
> Some more rough edges: both `data-dir:` and `defaults:` don't interpolate the environment variables `${.}` etc., so neither > > ``` > data-dir: ${.} > defaults: a > ``` >...
Report: the second option: namely, ``` CommandLine = "C:\Program Files\GS\gsXX.XX\bin\gswin64c.exe" -sDEVICE=pdfwrite -o "%1.pdf" -f "%1" ``` works fine on Win10 (64bit). Apparently the interface (for lack of a better name)...
> "c:\program" not runnable or equivalent means the space in the command was not correctly allowed for. > Indeed. > This can in some cases be overcome by use `%ProgramFiles%\`...
neither doublet nor triplet worked, if that's what you meant to imply in your post; so, for the time being, I'll stick to the previous solution: ``` commandline = c:\windows\system32\cmd.exe...
hello! tried another, older gs (portable) installed at school, and the space seems indeed to be the problem: ``` CommandLine = c:\windows\system32\cmd.exe /k " "C:\portapps\napps\GSView\gs8.64\bin\gswin32c.exe" -sDEVICE=pdfwrite -o "%1.pdf" -f "%1"...
So, does the space parse problem qualify as a bug?
hello! any progress with this project?
it seems that the `scope: ...` parameter of `place` is not yet documented either: it yields an error in typst 0.11 .