> > > > > > evolution CAMEL_DEBUG=all > > > > No, it should be > > > > CAMEL_DEBUG=all evolution > > What would be the diff: > > [guru@tiny ~]$ CAMEL_DEBUG=all env | fgrep CAM > CAMEL_DEBUG=all > [guru@tiny ~]$ env CAMEL_DEBUG=all | fgrep CAM > CAMEL_DEBUG=all
What does env do? To quote 'man env': " env - run a program in a modified environment" and without a program to run, it prints the environment variables. So the first version sets the variable and then runs the program 'env' (which prints out the environment); with the second version the variable is set *by the program* and then it prints out the environment. Setting the variable the second way is not a generic thing, it is unique to the program 'env'. It happens that both forms, in this case, have the same result. Generically, in a command such as: evolution CAMEL_DEBUG=all the 'CAMEL_DEBUG=all' is an argument to the command and is passed to the program in that way. It does not set an environment variable. In fact, since the argument doesn't start with a '-' (i.e. is an option), then evolution interprets it at as a URI to act on, which it can't understand, and hence the first line of the output is: > (evolution:3766): evolution-shell-WARNING **: Cannot import any of the > given URIs P. _______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
