Before I installed TBPortable.exe, on my PC .eml files were associated with the standard TB.exe. When I switched to the portable version I changed the association to launch the TB.exe file inside the TBPortable\App folder. However, that association didn't work well, because it launched TB.exe outside of its portable environment, so TB ended up running with an incomplete profile. So I reassociated .eml files with TBPortable.exe. That fixed the incomplete profile issue but introduced a new problem. When TB.exe is already running, double-clicking an .eml file doesn't open it, because TBPortable.exe doesn't seem to pass the .eml file argument to the running instance of TB.exe. Is this a know limitation of the launcher, and could it be fixed? Thanks
The error is actually within Thunderbird itself, not the launcher. The launcher does actually pass the command line you give it onto Thunderbird the same way it does with Firefox. But TB can't handle passing off to the first instance when the -profile switch is used (which it has to be in order to be portable). If you try dropping an eml file onto the launcher in Explorer when TBP isn't running, you'll see it open up the file just fine. This only affects one TB process passing it back to the 1st.
There is no workaround. I don't know if someone has opened a bug for it in bugzilla or not.
Sometimes, the impossible can become possible, if you're awesome!
OK, thank you. Then a work-around is to associate .eml files with ThunderbirdPortable\App\Thunderbird\thunderbird.exe and make sure to start ThunderbirdPortable\ThunderbirdPortable.exe before clicking any .eml files.
That doesn't work with Thunderbird 2.0 (which will be released soon). I already checked. There is no viable workaround until the bug in Thunderbird is fixed.
Sometimes, the impossible can become possible, if you're awesome!