setting ignore-glob has both versioned and non-versioned values: using versioned value from file "D:/xxx/.fossil-settings/ignore-glob" (to silence this warning, either create an empty file named "D:/xxx/.fossil-settings/ignore-glob.no-warn" in the check-out root, or delete the non-versioned setting with "fossil unset ignore-glob")

What docs do I need to study to understand what's happening here and what I might want to do about it?

I don't see this addressed in https://fossil-scm.org/home/doc/trunk/www/unvers.wiki

I've found this conversation from 9 years ago and repeats about how to silence the warning, but I don't know if that's a good idea or not - https://fossil-users.fossil-scm.narkive.com/sXhDq1Xb/fossil-unset-ignore-glob-seem-not-to-work

You maight look at the docs for the settings command:

Settings marked as versionable are overridden by the contents of the file named .fossil-settings/PROPERTY in the check-out root, if that file exists.

So you have a setting for ignore-glob created by the settings command, and that is overridden by the contents of the file .fossil-settings/ignore-glob in your checkout.

The message you quoted suggests two ways to deal with it.

I have unversioned files in this repo but they're not part of either of glob pattern.

It has nothing at all to do with unversioned files, despite the description "unversioned."

$ fossil set --global ...

creates a setting which applies to all repositories and is not "versioned" in the sense that it's not part of any repository's SCM history. It's local to that specific user/machine. Such settings are stored in your user account's "global" fossil database (typically ~/.config/fossil.db, but that can differ per system).

The .fossil-settings/... files apply to the repository, and every clone of that repository. When .fossil-settings/FOO exists, it overrides the global FOO setting and you are warned that the "global" setting does not apply because the repo-specific setting supersedes it.

despite the description "unversioned."

The error speaks of "non-versioned" values. Maphew made an unwarranted leap from that term to "unversioned".

indeed, I did lump un- and non- into the same mental bucket. Thank you both for the clarifications.

Realize also that this non vs un thing is a side matter. We could swap it to "nonversioned files" and "unversioned settings", and the outcome would be the same. Files ≠ settings, though perhaps confusingly, settings may be defined in files.