~/.config/micro with empty bindings.json and settings.json

Description of the problem or steps to reproduce

Installed on Ubuntu 20.04.3 by sudo snap install micro --classic. The ~/.config/micro directory is empty. Doesn't have *.json files populated with default bindings, settings, colorschemes, etc. Is it intentional?

In fact, micro -options does show the default options. I can very well recreate settings.json and customize it. Wondering if this is the intended design. For colorschemes, it's a bit more complicate as I don't know the command to list all the possible choices. Must look at https://github.com/zyedidia/micro/tree/master/runtime/colorschemes to guess colorschemes names.

Rebuilding for bindings.json requires more work. Must read throughtly https://github.com/zyedidia/micro/blob/master/runtime/help/keybindings.md. Which I didn't have time to go through yet. Again wondering if it is intentional design to have an empty bindings.json.

ll ~/.config/micro/
total 12K
-rw-r--r-- 1 user1 user1   84 Sep 28 22:38 bindings.json
drwxrwxr-x 2 user1 user1 4.0K Sep 28 22:40 buffers
-rw-r--r-- 1 user1 user1    3 Sep 28 22:38 settings.json

Content of bindings.json

{
    "Alt-/": "lua:comment.comment",
    "CtrlUnderscore": "lua:comment.comment"
}

Content of settings.json

{}

Specifications

micro -version
Version: 2.0.10
Commit hash: b976385
Compiled on August 07, 2021

OS: Ubuntu 20.04.3.
Terminal: tmux 3.0a

Start by comparing the installed ~/.config/micro files with the defaults exposed by micro -options and the contents of runtime/colorschemes and runtime/help/keybindings.md. Determine whether the empty settings.json and bindings.json are intentional, and document the expected default-file behavior and how users can discover available colorschemes and bindings.