As far as fossil is concerned, once you close the repo, it's out of site of mind. I still use git for most everything else. Only my dot files and my personal obsidian vaults are backed up to fossil.
> I was using git, however I like that fossil allows you to put the repository where ever you want on the file system. I don't have to worry about alias's, using .gitignore, or setting it it up where it doesn't show untracked files.
Git also lets you put the repository wherever you want on the filesystem, via worktrees or via the `--separate` link. And I fail to see the relationship with aliases or ignore files (the last item I guess you're talking about fossil not showing untracked files by default?)
Fossil doesn't show much unless you perform a open or a checkout against the repo file. Generally, it only shows the location of the config database ($HOME or $XDG) exmaples below. The added benefit is that you can do this open/checkout anywhere on the system. For instance, if I'm making changes in my /etc, I can commit a file from there without having to move the file. Another nice feature is they have an unversioned [1] mechanism as well, which allows you to commit files that you want to save but don't care about the history.
Ran from my $HOME
-------------------------
$ fossil info
config-db: /home/$USERNAME/.config/fossil.db
fossil: /home/$USERNAME/.local/bin/fossil
version: 2.19 [1e131febd3] 2022-07-21 16:10:55 UTC
$ fossil status
current directory is not within an open checkout
--------------------------
Used several times to back up some critical configurations (3rd/4th paranoia backup right before maintenance) on a few servers because the commit/open from anywhere. It doesn't pollute the file system as it's a single file.
With the untracked files: It's a little different. The git way you usually use do the dot file backup is with an alias `--untracked-files=no` so you don't see them unless you override it. At least most of the examples I followed the processes I've experimented with over the years recommended.
With fossil you see them when you consciously issue a fossil open in order to do a commit. I'd rather see the untracked files, when I'm ready to commit then to not see them at all and miss something. Out of site. out of mind is something I personally struggle with.
[1] https://fossil-scm.org/home/help/uv
* Edited for formatting.
Otherwise, you can always use chisel [0]