SPF cant work well in restricted permissions

[lazysegtree]

Describe the bug
Cannot use spf as nobody user

To Reproduce
Steps to reproduce the behavior:

1. cd to /
2. Login to nobody user
3. Try launching spf
4. See error

Expected behavior
spf works with default configs.
Yazi works in this situation.

This shows a problem with error handling of spf. If files are not accessible it exits, instead of using default config.

Screenshots
No screenshots, but logs

➜  / [1:00:37] sudo -u nobody bash
bash: /Users/kuknitin/.bashrc: Permission denied

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
bash-3.2$ pwd
/
bash-3.2$ which yazi
/opt/homebrew/bin/yazi
bash-3.2$ /opt/homebrew/bin/yazi
bash-3.2$ which spf
/usr/local/bin/spf
bash-3.2$ /usr/local/bin/spf --version
2025/03/06 13:01:10 ERROR Error reading from file: error="open /Users/kuknitin/Library/Application Support/superfile/themeFileVersion: permission denied"
superfile version v1.2.0.0
bash-3.2$ /usr/local/bin/spf
2025/03/06 13:01:13 ERROR Error reading from file: error="open /Users/kuknitin/Library/Application Support/superfile/themeFileVersion: permission denied"
2025/03/06 13:01:13 Error creating directories: failed to check directory status /Users/kuknitin/Library/Application Support/superfile: stat /Users/kuknitin/Library/Application Support/superfile: permission denied
bash-3.2$

System information (please complete the following information):

• OS: MacOS
• Version 14
• superfile Version 1.2.0.0

[yorukot]

I saw that Yazi is supposed to work in this situation, but it didn’t work for me. Any idea why?

[lazysegtree]

[lazysegtree]

@yorukot Make sure to launch yazi in a directory which is accessible by nobody user like /tmp or /

[lazysegtree]

Most likely when you lauched yazi, you were inside you main user directory, which is not accessible by nobody user.

[yorukot]

Yeah after i change to the /tmp it works!

[lazysegtree]

Originally posted by @Moriarty1 in #959 (reply in thread)

Is it possible to run superfile without config file on readonly system?
I got this errors
time=2025-09-21T02:57:42.618+01:00 level=ERROR msg="Error creating theme directory" error="mkdir /home/chronos/user/.config: read-only file system"
time=2025-09-21T02:57:42.620+01:00 level=ERROR msg="Error while writing default theme directories" error="mkdir /home/chronos/user/.config: read-only file system"
Error creating directories: failed to create directory /home/chronos/user/.config/superfile: mkdir /home/chronos/user/.config: read-only file system

Another user request for this.