Additionally store absolute paths in session files, my suggestion is to store the absolute path as a fallback when the relative path cannot be loaded, separated with a pipe char.

When you move the session file, relative paths won't work anymore. On the other hand storing relative paths is cool when working with a stick.

So, my suggestion is to store the absolute path as a fallback, when the relative path cannot be loaded, separated with a pipe for example:

Icfu

Thanks for the suggestion, I am rather skeptical as I want list files as compatible as possible with other applications. Do you have any, sort of, typical format of list files?

maybe a good compromise is to make the paths relative to the root, or in other words absolute but leaving out the drive letter.

e.g.

that way the .lst file can be moved around (as long as it is in the same drive) and it will also work on sticks where the drive letter could change.

blues

There is another way, have a look at what Total Commander does. When starting, TC adds temporary envvars:
%COMMANDER_PATH% points to the application home directory.
%COMMANDER_DRIVE% points to the root.

If you implement %HiEditor_Path% and %HiEditor_Drive%, you can store paths relatively absolute, like that (in fact this is what blues has proposed, but with a real drive letter):
%HiEditor_Drive%\bla\blubb\target.txt

When saving, don't add absolute paths as fallbacks separated with a pipe but on a new line.

The nice side effect is that other applications will be able to use these list files as well, without the need to support relative paths.

Icfu

Thank you guys,

Icfu, it is not 100% clear to me, can you give me a sample list file demonstrating what you are saying?