superfile icon indicating copy to clipboard operation
superfile copied to clipboard

custom config file not working on mac

Open mactanxin opened this issue 9 months ago • 11 comments

Describe the bug A clear and concise description of what the bug is. Installed from homebrew. After install, there's no ~/.config/superfile/config.toml or even the ~/.config/superfile/ folder.

I created the folder with mkdir -p ~/.config/superfile/, then touch & edited the config.toml followed from Tutorial, Themes section, nothting changed.

then I found ~/Library/Application\ Support/superfile/ folder and after edit config files it works.

Expected behavior generate config files in ~/.config/superfile folder and overwrite the default ones.

Screenshots If applicable, add screenshots to help explain your problem.

System information (please complete the following information):

  • OS: MacOS
  • Version 14.2.1 (23C71)
  • Superfile Version v1.1.2

mactanxin avatar May 11 '24 08:05 mactanxin

https://github.com/adrg/xdg

So it's not technically a bug I think the documentation needs to be updated..

image I actually update this in next version to make it easier for users to find the config file location.

yorukot avatar May 11 '24 09:05 yorukot

Was also expecting to user .config folder. But for me even the Application Support folder doesn't seem to work. Tried with both creating the folder /superfile and putting the config.toml / hotkeys.toml directly in the Application Support folder. Any suggestions? Can't run spl pl either, just gets me into superfile with "pl" as a search term.

albinabc avatar May 21 '24 09:05 albinabc

You should be running v1.1.2 v1.1.2 does not have this feature :(

yorukot avatar May 21 '24 13:05 yorukot

Ahh. Tested building from source now instead, and now the pl command works, and I can get the config path. However, one thing I'm noticing is that if I try to copy the path and paste for just opening in an editor, it doesn't find the config file because it doesn't escape the space in the "Application Support". However since it seemed to work for OP I guess that's not the culprit here...

albinabc avatar May 21 '24 13:05 albinabc

I tried updating the config path in the src and rebuilding, to see if I could put the config files in the .config/superfile folder instead. But that doesn't seem to work either. Not really getting those hotkeys, and can't get a theme to apply either.

A note, do I need to put themes like "catppuccin-latte" in the superfile/theme folder to be able to use it, or should it be available to begin with?

image

Note, running macOS 14.3 (23D56)

albinabc avatar May 23 '24 09:05 albinabc

@albinabc Are you using the current branch version? If so, you can try changing the data in /src/config/fixed_variable.go.

yorukot avatar May 23 '24 12:05 yorukot

Just updated to try, did the config in /src/config/fixed_variable.go as you mentioned, rebuilt and moved the executable (to a non-privileged folder and running from there instead), but no difference. So what I'm testing to check if it has applied if I close the application with q (I'm using the vim hotkeys file) and also if the theme specified in config.toml has applied. Nothing seems to apply, and as the screenshot in my previous message, the path looks right after running spf pl. The command spf eh yields nothing, is that expected?

albinabc avatar May 23 '24 13:05 albinabc

Would you like to send your fixed_variable.go because I tested that it changes after updating it.

// ...

var HomeDir = xdg.Home
var SuperFileMainDir = "/home/nightcat/Documents/code/superfile" + "/superfile"
var SuperFileCacheDir = xdg.CacheHome + "/superfile"
var SuperFileDataDir = xdg.DataHome + "/superfile"
var SuperFileStateDir = xdg.StateHome + "/superfile"

// ...

yorukot avatar May 23 '24 14:05 yorukot

var HomeDir = xdg.Home
var SuperFileMainDir =  "~/.config/superfile"
var SuperFileCacheDir =  "~/.config/superfile"
var SuperFileDataDir =  "~/.config/superfile"
var SuperFileStateDir = "~/.config/superfile"

And also

var (
	ThemeFoldera      string = SuperFileMainDir + "/theme"
	LastCheckVersiona string = SuperFileDataDir + "/lastCheckVersion"
	ThemeFileVersiona string = SuperFileDataDir + "/themeFileVersion"
	FirstUseChecka    string = SuperFileDataDir + "/firstUseCheck"
	PinnedFilea       string = SuperFileDataDir + "/pinned.json"
	ConfigFilea       string = SuperFileMainDir + "/config.toml"
	HotkeysFilea      string = SuperFileMainDir + "/hotkeys.toml"
	ToggleDotFilea    string = SuperFileDataDir + "/toggleDotFile"
	LogFilea          string = SuperFileStateDir + "/superfile.log"
)

And yes this seems to apply, before I had updated it to .config/superfile I got the Application Support folder outputted from spf pl. The thing is that it doesn't seem to matter, because in neither case I can get any configuration/hotkeys to load.

albinabc avatar May 24 '24 20:05 albinabc

I tested it a little bit and I probably know why, you should use full paths instead of relative paths (~).

yorukot avatar May 25 '24 04:05 yorukot

Heyy that works! I guess it's still a mystery as to why the original XDG path did not work for me, because then I hadn't fiddled with the paths or anything. But it's a viable workaround, thanks for the help!

albinabc avatar May 25 '24 05:05 albinabc