Based on what I've tried so far fossil ui will *always* choose the first user listed in the user table. None of $USER, --user, -U, default-user in global-config or in config will override fossil ui using the first user listed.
This is a problem because cloning from a file will preserve the users as listed in the original db. Cloning via http always puts the cloning user first in the table and so fossil ui works as expected. So if user 'bob' creates a fossil and I clone from his db via the filesystem then when I as 'matt' launch the ui the user will be 'bob' by default. If Bob starts up a server from his db and I clone via http then when I run 'fossil ui' the default logged in user will be 'matt'. I guess this was implemented this way for ticket c9e84b5671<http://www.sqlite.org/debug1/tktview?name=c9e84b5671>(which I don't think makes necessarily makes sense) so the solution is in fixing clone to add the target user as #1 when cloning from a file.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
