Re: load new file - not working consistently

I'm using build 2507, dated 10/05/14 19:50:41

In most cases, when I load a new file, it sets the path to c:\pspad,
rather than my current path.

Wait for new build please and don't start new and new topics.
Your problem is that you start pspad with command line and send file without path as parameter. It works correctly, if PSPad doesn't running - new instance.
But it doesn't work if PSpad is already running. In this case instance what is started sends filename into existing instance and path. But PSpad in this moment doesn't know fromn where you start your file. The path you see is the working directory of running PSPad instance.

Solution what I need to do is add path for this case and send filename include path into existing instance.

Oh, sorry about starting new topic; I considered it new topic because the original topic had been addressed by build 2507, but I won't do that in the future.

You are correct, that I am loading new files into pspad from the command line, after the editor is already loaded; I tend to leave my editor running for days or even weeks at a time, and just load in new files from the command line as I need them.

I hope your new solution will work...

Test new build 2512

Yes!!! Seems to derive the current path properly now for new files, both when pspad is already running, and when it is not. And, of course, it still properly loads existing files in both cases.

Thank you again for the prompt assistance!

Well, unfortunately, build 2512 still has an issue with opening new files.

I'm in the directory C:\game.notes\Legend of Grimrock 2
and I open non-existent file x.txt

pspad build 2512 actually opens FOUR different non-existent files:

c\game.notes\Legend
c:\pspad\of
c:\pspad\Grimrock
2\x.txt

I'm guessing it didn't allow for spaces in the filename...

Gorlash:

Well, unfortunately, build 2512 still has an issue with opening new files.

I'm in the directory C:\game.notes\Legend of Grimrock 2
and I open non-existent file x.txt

pspad build 2512 actually opens FOUR different non-existent files:

c\game.notes\Legend
c:\pspad\of
c:\pspad\Grimrock
2\x.txt

I'm guessing it didn't allow for spaces in the filename...

Does PSPad instance run already when you open your file or not?

Ahhh... that's a good question...

If PsPad is NOT running, and I do this experiment, it works fine.

If PsPad IS already running, then I have this problem.
Interestingly, it does not matter whether I had started PsPad in the failing directory or somewhere else.

OK, I will try to handle it.

BTW, I am finding that this is *not* merely a new-file problem. Even when I am opening an existing file from the console, if there is a space anywhere in the path, I get the previously-described problem, where it opens several empty, non-existent files in each of the partial paths... this is really a headache!! Could you try to fix this??