I'm having trouble adding a folder (and its subfolders) with @ in it's name as either source or destination. It goes fine to add a parent folder and browse though. Could this be a bug?
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
I think the @ symbol is reserved and used for variables within Toucan. It's an unusual letter in directory names. I don't think it'll work for specifically setting those paths but I'd wait for Steve the author to chime in.
Sometimes, the impossible can become possible, if you're awesome!
the @ sign is used for variables in Toucan, to be honest you are the first person in 600,000 downloads to ask about it, it is a pretty unusual character to have in a folder name. I wasn't kind of hoping that it should work, I think I can add a solution but it will take some planning, hopefully I will get it done in time for 2.1.1.
ok, I'm a little surprised I'm the only one though. The folder is a remnant from Steam. The "game manager" created it from my email address that I believe they used as account names also at that time. I'm pretty sure it was made automatically. Considering the amounts of people playing counter-strike I'd say the chance of receiving this bugreport again is quite high
It's not that surprising. Even if it is used by others, chances are it is deeper than the directory they are selecting. So the bug wouldn't pop up.
We once found a bug with dollar signs in OpenOffice.org's directory handling. That was after millions of downloads.
Sometimes, the impossible can become possible, if you're awesome!
How about using a different character that's not allowed within DOS filenames. Like the pipe character. Or the colon.
http://en.wikipedia.org/wiki/File_Allocation_Table#Directory_table
Sometimes, the impossible can become possible, if you're awesome!
is already used in the settings files to separate paths, colon is used in things like C:\, I think I should be able to get this sorted, I would rather go for the 2.1.0 release now though as it fixes quite a few bugs, if I make more changes we will have to go through more testing cycles.