4 ms·
Fair enough on most points. Have to point out typing the filename is unnecessary, however. Just run "fossil open" on the repository file once and from there on
by jaccarmac 9y ago
Fair enough on most points.
Have to point out typing the filename is unnecessary, however. Just run "fossil open" on the repository file once and from there on out any fossil command in that directory will run against said repo.
- zaarn 9y ago>Just run "fossil open" on the repository file once and from there on out any fossil command in that directory will run against said repo. During my testing I never encountered that command much, though it doesn't really relieve the problem of having to double-open a repository; open folder, then open repo. When I change a directory in Git, it automatically `fossil open`'s the current repo. If no repository file is specified there should be an automatic fallback. Or even better, make using a non-default repo file a special flag, just like in git. I don't really want to have to deal with opening something or connecting something when changing directories should be sufficient.
- jaccarmac 9y agoIt's inconvenient for sure, but to be clear opening a repository is a one-time operation. It puts a file called ".fslckout" in the current directory which acts like the ".git" directory does for Git.