From article:
> This allows, for example, a Fossil-NG user to clone and use a repository out of GitHub while continuing to use the superior Fossil user interface.
I totally disagree here; I don't think Fossil user interface is superior at all!
> This allows, for example, a Fossil-NG user to clone and use a repository out of GitHub while continuing to use the superior Fossil user interface.
I totally disagree here; I don't think Fossil user interface is superior at all!
Have you even used it? I'm using both fossil and git and I find fossil's CLI and integrated documentation vastly susperior to git's in terms of usability.
The Web UI doesn't fare better and it somewhere on the lower half of my UX shitlist.
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.
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.