XY to retain Variables on adress paths.

[SkyFrontier]

Is it possible have XY to keep variables not resolved on adress bar, so %USERPROFILE%, %tmp% and such could be really PORTABLE paths right from the app statup?
Currently if you enter %tmp% you have as result something like:

Code: Select all

C:\Documents and Settings\Administrator\Local Settings\Temp\

There are TWO variables in that common path, though (C:\Documents and Settings\%userprofile%\Local Settings\%Temp%\).
So if one use a PORTABLE file manager on another machine, the result will be

Code: Select all

Location currently not available

instead of real, live and pulsing

Code: Select all

D:\Users\Temp\

-custom path, of course.

What about...?

Thanks.

[admin]

Not possible in the address bar. But favorites, catalog etc will keep the variable.

[SkyFrontier]

Admin:

Not possible in the address bar. But favorites, catalog etc will keep the variable.

...it's the automation thing that amuses me. Perhaps our (kind of; déja vu for sure) recent discussion on session management can turn things easier, then.

Thanks, anyway.

[TheQwerty]

Isn't this precisely the reason that this INI Tweak exists?

Code: Select all

; Tweak: set to 1 to store paths relative to app path
PortableTabs=0

EDIT: Nevermind.. I didn't follow what you actually meant at first.
I think it might be time for some more caffeine.

EDIT2: That said, why couldn't this tweak be expanded to use Environment variables as well?

[admin]

Isn't this precisely the reason that this INI Tweak exists?

Code: Select all

; Tweak: set to 1 to store paths relative to app path
PortableTabs=0

BTW, I'm still waiting for feedback on this tweak. It should go to UI level...

[SkyFrontier]

Code: Select all

; Tweak: set to 1 to store paths relative to app path
PortableTabs=0

Wadda...???

I mean... errr... since when? WHERE???

Did you managed to built in XY the time machine since last time I went around, Don, so Qwerty brought that back from the future to us?

And yes, I'd really like to know where that info is... not on History.txt (9.30!), nor recent posts...

edit: Found it. Since "Fast Tag Search" (v8.80.0101), probably overlooked it due to being amazed by FTS...

Time to test... Ah, my testing system... I'll miss you...

[nas8e9]

Is it possible have XY to keep variables not resolved on adress bar, so %USERPROFILE%, %tmp% and such could be really PORTABLE paths right from the app statup?
Currently if you enter %tmp% you have as result something like:

Code: Select all

C:\Documents and Settings\Administrator\Local Settings\Temp\

There are TWO variables in that common path, though (C:\Documents and Settings\%userprofile%\Local Settings\%Temp%\).
So if one use a PORTABLE file manager on another machine, the result will be

Code: Select all

Location currently not available

instead of real, live and pulsing

Code: Select all

D:\Users\Temp\

-custom path, of course.

I'm confused: Windows defines %TEMP% and %TMP% as separate variables instead of concatenating %USERPROFILE% or %LOCALAPPDATA% with strings. That should mean that changing %TMP% to something outside %USERPROFILE% or %ALLUSERSPROFILE% should still result in %TMP% returning the right folder?

[SkyFrontier]

Code: Select all

PortableTabs=1

...it OBVIOUSLY was not what I was expecting, but I have a naive faith... I had to try... despite the statements of "relative to XY path".
Problem with that concept is: almost NOTHING fits on paths relative to XY, nothing system-related, of course...
Some time ago I tried to put apps relative to XY and deal with them from there. That was a pain when I needed to backup stuff created from such apps, which are totally XY-blind...

Errr... "Not possible in the address bar" means a technical, unbreak-able limitation, Don, or there's still a hope to wait for...?

[Stefan]

so %USERPROFILE%, %tmp% and such could be really PORTABLE paths right from the app statup?
Currently if you enter %tmp% you have as result something like:

Code: Select all

C:\Documents and Settings\Administrator\Local Settings\Temp\

There are TWO variables in that common path, though (C:\Documents and Settings\%userprofile%\Local Settings\%Temp%\).

You mixed things up here.
"C:\Documents and Settings\%userprofile%\Local Settings\%Temp%\" is wrong.

%userprofile% points to
C:\Documents and Settings\<UserName>
for XP
or
for W7 to
C:\Users\<UserName>

and %tmp" to
C:\Documents and Settings\<UserName>\Local Settings\Temp\
or
C:\Users\<UserName>\AppData\Local\Temp

and so always "portable".

So if you use "goto %temp%;"
you go always to the temp folder of the current logged-in user, no matter if XP or W7.


To be portable relative to XYplorer-folder you can use
goto "<xypath>\NewItems";
or even something like
goto "<xypath>\..\OtherTools\ToolB\b.exe";


Maybe you can provide an example what you want to do?

[SkyFrontier]

Nas8e9:

I'm confused: Windows defines %TEMP% and %TMP% as separate variables instead of concatenating %USERPROFILE% or %LOCALAPPDATA% with strings. That should mean that changing %TMP% to something outside %USERPROFILE% or %ALLUSERSPROFILE% should still result in %TMP% returning the right folder?

Works like a charm for me, compadre.
And I really prefer that way.
Sometimes there are leftovers out os setups which I needed for a reason or another, and running image-based systems as I do I'm more than happy to discover that such stuff was NOT erased in the occurrence of disasters/recoverings.
U$ 0,02, anyway.

[admin]

Code: Select all

PortableTabs=1

...it OBVIOUSLY was not what I was expecting, but I have a naive faith... I had to try... despite the statements of "relative to XY path".
Problem with that concept is: almost NOTHING fits on paths relative to XY, nothing system-related, of course...
Some time ago I tried to put apps relative to XY and deal with them from there. That was a pain when I needed to backup stuff created from such apps, which are totally XY-blind...

Errr... "Not possible in the address bar" means a technical, unbreak-able limitation, Don, or there's still a hope to wait for...?

Too much work.

[Stefan]

I'm confused: Windows defines %TEMP% and %TMP% as separate variables
instead of concatenating %USERPROFILE% or %LOCALAPPDATA% with strings.
That should mean that changing %TMP% to something outside %USERPROFILE% or %ALLUSERSPROFILE%
should still result in %TMP% returning the right folder?

%temp% and %tmp% pointing both to
C:\Documents and Settings\<UserName>\Local Settings\Temp\
%UserProfile%\Local Settings\Temp\
or
C:\Users\<UserName>\AppData\Local\Temp
%UserProfile%\AppData\Local\Temp


You can do "set TMP=C:\myTemp"
and then %tmp% points to " the right folder" "C:\myTemp" , but not to "%UserProfile%\....\Temp\" anymore.

Please note that %temp%/%tmp% came from an time where there wasn't any "user profile folders".
And back in that days %temp% and %tmp% pointed to different dirs.

HTH to clarify a bit

[SkyFrontier]

Thanks, Stefan. In a hurry and seeing different system scenarios anywhere I look (and several days of bad sleeping, too) can cause such laughable confusions. You are right, in a wider range.

But the thing is: I'd really enjoy the possibility to have XY tabs pointing to each system's destination (following global, system-independent variables) instead of a last valid target as it currently does, zero point-and-click, zero CKS. Simple like that.

[SkyFrontier]

Stefan:

And back in that days %temp% and %tmp% pointed to different dirs.

-I see the benefits of puting stuff in different folders, as pointed above. Old school but saves me confusion. Believe it or not.

[SkyFrontier]

Admin:

Too much work.

What about aliases to get the work done? Or is it the same problem, from the technical point of view?