sumatrapdf-tool (new in 3.7 pre-release)

[kjk]

Recently I've added ability to run tools like info or draw or convert on pdf files from command line with SumatraPDF.exe <tool>

This is now deprecated and now you should use console app sumatrapdf-tool.

It does the same but works fully correctly with console / shell / cmd.exe / powershell because sumatrapdf-tool.exe is a console application, not gui app.

I've updated the documentation to reflect that: https://www.sumatrapdfreader.org/docs/Tools

[yozhic]

The idea is great. But how will it work in the portable version?

[yozhic]

Is there really a need to “bundle” the DLLs into SumtraPDF.exe in the portable version? As far as I understand, the most significant difference between the portable version and the installable version is that the portable doesn’t write anything to the Windows Registry—not that it’s a single file instead of five.

Although, on the other hand, having a single file is convenient because if I carry both 32-bit and 64-bit versions of SumatraPDF on a USB drive, they can both access the same SumatraPDF-settings.txt file, and my settings are saved regardless of which system I’m working on.

Conclusion: it would probably be better to add a brief note about the syntax of the portable version to the documentation.

[GitHubRulesOK]

@yozhic
my understanding is the "portable" has always been "One.Exe" (+1 companion settings.txt) thus is less integrated than a dll system installation which has 6 or more files of different ilk (exe dll lnk + dozens of interrelated registration entries)

The 1.exe uses methods of "reflection" such as very much DDE communications and more recently "tool" commands. But hybrid.exe's have issues thus some applications may use 2 copies such as renaming Exif.exe ( rename to "exiftool.exe" for command-line use.)

In this case a smaller stub is being used for installed version rather than a full blown duplicate
the one.exe model still works by reflections but will thus "not be exactly the same" input output.

[GitHubRulesOK]

@yozhic
The current SuTools state is clearly variable but these produce same result

Installed 
18587>sumatrapdf-tool.exe merge -o target.pdf a.pdf b.pdf
Portable
18587>SumatraPDF-prerel-32.exe merge -o target.pdf a.pdf b.pdf

Where it matters is use of scripts In/Out and REPL (js commands on command line)

as a small example first installed then portable

18587>SumatraPDF-tool run
> print (1+1)
2
> print (2+2)
4
> quit()

18587>SumatraPDF-prerel-32 run

18587>>
18587>print (1+1)
2
> print(2+2)
Unable to initialize device PRN

[yozhic]

@GitHubRulesOK

my understanding is the "portable" has always been "One.Exe"

Thank you; it was interesting to learn that this is also a common understanding.

Unable to initialize device PRN

However, there is a workaround:

C:\totalcmd\Profile\tools\SUMATRAPDF>cmd.exe /c SumatraPDF-prerel-32.exe run
> print(1+1)
2
> print(2+2)
4
> print(2+2*6/3)
6
> quit()

C:\totalcmd\Profile\tools\SUMATRAPDF>

[GitHubRulesOK]

@yozhic OK I had not spotted that so a child console is working for you
Hmm interesting I overlooked that possibility and agree it works
C:\Users\WDAGUtilityAccount\Desktop\Apps\PDF\SumatraPDF\18630>cmd /c SumatraPDF-prerel-32 run

print (1+1)
2
print (2+2)
4
quit()

or
cmd /c SumatraPDF-prerel-32 run

var res=(1+1);print (res+res);quit()
4