Drop Portable Variables in 2.0?

Could not care less.

--
Life is about the journey not the destination!

My site * My Blog

The Kazoo Spartan

I think portable variables have unreplecable function when synchronizing between computers which have user data located in different paths, e.g. on different drives (C: on one, D: on second).

Also, I don't work with directories of 'C:\Documet and settings\\...blabla...\My Documents\' type, but purely in ':\LuP\'; I use a named portable variable which points to ':\LuP\' when synchronizing.

I only use it for paths on 1 computer. Maybe remove the ability to add new ones within the interface, but still leave the backend code so we can manually add it to the INI.
----
Ryan McCue.
Blog.
So all that Airbus-delay trouble over here in Europe is because of YOU!
Simeon.

I would like to be able to use them, but they aren't all that reliable. The backslash doubling is a problem, but also often just a drive letter doesn't seem to want to work right. (Making P: as a variable and then doing @ExampleDrive@\PortableApps or whatever doesn't work, however entering P:\PortableApps works fine.)