If there is a space after the last filename when using command line arguments, it open the specified file(s), but it also creates a new blank document. Which is always forced to the front as the active document. Needless to say this is extremely disruptive to your workflow.
TextPad Help:
.. but <space> is not equal to "". I could somewhat understand it if this behavior was triggered on multiple spaces. But not on a single space character.An empty, quoted filename (i.e. "") causes a new document to be created.
I have several applications that pad each file name with a trailing space when passing command line arguments to launch external tools, and it's extremely frustrating having a blank document slapped in my face every time I want to do a quick edit in TextPad. So, because of this I'm using Notepad++ instead for these small tasks, but I would much more prefer to be using TP.
Just recently purchased a TP8 license, and this age-old bug is still here. Would love to see this dealt with. It's been bothering me for like a decade :)