Portabel SS needs Portabel Settings

We welcome any suggestions for new features or improvements in Altap Salamander. Please post one suggestion per report.
GuidoR13
Posts: 10
Joined: 09 Feb 2006, 17:53

Portabel SS needs Portabel Settings

Post by GuidoR13 »

Hello, like already discussed running SS from a "normal" USB-Stick (or a CD) would be more than convenient for me.

But that's half the way: Currently I do not see a possibility to set the paths to the tools (archiver, editor, user menu) in a portable way. Even if variables are possible in the arguments (really fine solution), this is not possible with the programms themself. So what shall I do with a portable SS when my Editor lies relavitve to SALAMAND. EXE - like ..\jEdit\jEdit.exe? Allowing EnVars would be great - my startup-script set e.g G__USB to the root of the USB-Stick so %G_USB%\jEdit\jEdit.exe would work...

Oh, a word to the INI-File: Please prefer XML against the standard INI-Format if possible ...

Guido
Jan Rysavy
ALTAP Staff
ALTAP Staff
Posts: 5231
Joined: 08 Dec 2005, 06:34
Location: Novy Bor, Czech Republic
Contact:

Re: Portabel SS needs Portabel Settings

Post by Jan Rysavy »

GuidoR13 wrote:Currently I do not see a possibility to set the paths to the tools (archiver, editor, user menu) in a portable way.
Confirmed, we will solve this problem, thank you for reporting it.
GuidoR13 wrote:Oh, a word to the INI-File: Please prefer XML against the standard INI-Format if possible ...
We prefer the standard text (unicode) file instead of XML. Why should we use bloated XML?
GuidoR13
Posts: 10
Joined: 09 Feb 2006, 17:53

Post by GuidoR13 »

Thanks!

I've installed some tools on my USB stick and even if they support an INI-File there is always some correction needed.

I tend to change configs in my script (see below) and there XML is more convenient for me than the INI-Format (even I speak SED, I really do not like the syntax). And file size is not of real importance for me (4G USB ;-)

But I'll prefer what you prefer ;-)

Take SS for example my startup skript will:

A) Before starting- parse the regfile of one configuration an adapt the hot path to the local user I am (I prefer addressing dirs with hotkeys and will see on some the ones for the current user, even on the network)
B) run SS once as admin and second as current user
E) wait until SS ends: - clean registry & - set configuration to the default

I use autohotkey for this, quite convinient

Guido
Post Reply