Probably because no one has come up with an application yet to utilize them.
I could go and set these right now on my system, but without any applications
to read them, it’s not very useful.
But, I guess it should start with a spec on how the variables should work.
So here’s what I suggest (examples):
Working similar to PATH, you have a list of applications, seperated by
colons. The first app in the list would be the default browser.
You could set this as well, which would override the ‘first in WEB_BROWSERS
list is default’ behavior. However, WEB_BROWSERS would still be useful, as
you have a list of all the available browsers for the system that you could
use, if you wanted to use a specific one or whatever.
These would work similar to the above, only applies to the email client
These would be for FTP access, etc. You could set up variables for other
things as well.
So, there’s a spec. Now we just need some applications out there that use it
and we are in business. Feel free to forward this on to anyone you want.On Wednesday 11 April 2001 11:56, you wrote:
Trying to do this in a cross-platform sort of way is /very/ tricky and
problematic. For example, under Linux you have so many possible browser
options which are actively in use you would have a very difficult time
trying to pull it off.
Why has noone come up with a “$WEB_BROWSER” or “$URL_HANDLER” or
some other environment variable, like “$EDITOR” (which we’ve had forever!)?