You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just saw https://github.com/qxb3/fum/wiki/Rices section in wiki and while trying to apply them I run into couple issue/roadblocks:
Missing players, use_active_player and debug
Yeah i intentionally hid them so you just copy the layout important part. Feel free to add them tho if you want.
Having to type long path for config
Instead of fum -c ~/.config/fum/long_config_name.json, fum could also accept long_config_name and look for it in config dir width and height should be inside layout (maybe rename UI?)
Also few ideas how to improve the situation
a.
layout: accept string, name of the layout
layouts: array, each layout has a name
b.
Same as a. but have layouts in separate files. That way there would be config.json with layout and several layout-$NAME files along it.
Yeah having like a separate file for different layouts can be interesting. I also ran to this problem while screenshot-ing the project where i have to delete the current one to replace it with another one. I might consider this
After some time of consideration, i decided not to go with this as its i think unnecessary feature that most people don't want. I guess if someone wants to have a layouts management they could write a script to do it, Writing one should be really easy to do.
Especially now that im planning to make the config auto-reload when changed. #42
Just saw https://github.com/qxb3/fum/wiki/Rices section in wiki and while trying to apply them I run into couple issue/roadblocks:
players
,use_active_player
anddebug
I would forget to add it myself and get stuck for couple seconds thinking whats wrong
Instead of
fum -c ~/.config/fum/long_config_name.json
, fum could also acceptlong_config_name
and look for it in config dirwidth
andheight
should be insidelayout
(maybe rename UI?)Also few ideas how to improve the situation
a.
layout
: accept string, name of the layoutlayouts
: array, each layout has aname
b.
Same as
a.
but have layouts in separate files. That way there would beconfig.json
withlayout
and severallayout-$NAME
files along it.The text was updated successfully, but these errors were encountered: