File tree Expand file tree Collapse file tree 1 file changed +10
-1
lines changed
Expand file tree Collapse file tree 1 file changed +10
-1
lines changed Original file line number Diff line number Diff line change @@ -260,7 +260,16 @@ export_hyde_config() {
260260 # ? This function is used to re-source config files if
261261 # ? 1. they change since the script was started
262262 # ? 2. the script is run in a new shell instance
263- # ? 3. When you needed the arrays to be available in the current shell session // bash does not export arrays
263+ # ? This function is used to re-source HyDE config files in the following scenarios:
264+ # ? 1. If the config files change since the script was started (e.g., another process or user updates theme or state).
265+ # ? Example: You edit your theme or state config while this script is running; call export_hyde_config to reload changes.
266+ # ? 2. If the script is run in a new shell instance (e.g., after opening a new terminal or sourcing this script in a subshell).
267+ # ? Example: You start a new shell session and want to ensure the latest config is loaded; call export_hyde_config at the start.
268+ # ? 3. If you need arrays from the config to be available in the current shell session (since bash does not export arrays).
269+ # ? Example: You want to use theme or wall arrays in your shell; call export_hyde_config to populate them.
270+ # ?
271+ # ? Usage: Call export_hyde_config whenever you need to ensure the current shell has up-to-date config and arrays.
272+ # ? Typically called after config changes, at shell startup, or before using config-dependent arrays.
264273
265274 local user_conf_state=" ${XDG_STATE_HOME} /hyde/staterc"
266275 local user_conf=" ${XDG_STATE_HOME} /hyde/config"
You can’t perform that action at this time.
0 commit comments