`wordexp` support for `source` and `load` commands #1

New Issue

Open

opened 2024-04-30 12:27:14 +03:00 by hkc · 0 comments

hkc commented

2024-04-30 12:27:14 +03:00

Owner

Would be nice to not have /home/USER/.local/share/sounds/blah/_.txt all over the config file. source ~/.local/share/sounds/*/_.txt would be more convenient. Can't see any problems with sourcing.

loading sounds is a problem though. If there's more than one file matching, should I load all of them? Should I store each sound in another dynamic array? Array of arrays? 2D matrix of sounds and instances of sounds? Or should I just pick first one and ignore the rest? Don't know what to do here. If I choose an option of loading all of them, I should also add an option that changes how they're picked (random, round-robin, etc).

Also, are there any security implications with wordexp?

Would be nice to not have `/home/USER/.local/share/sounds/blah/_.txt` all over the config file. `source ~/.local/share/sounds/*/_.txt` would be more convenient. Can't see any problems with sourcing. `load`ing sounds is a problem though. If there's more than one file matching, should I load all of them? Should I store each sound in another dynamic array? Array of arrays? 2D matrix of sounds and instances of sounds? Or should I just pick first one and ignore the rest? Don't know what to do here. If I choose an option of loading all of them, I should also add an option that changes how they're picked (random, round-robin, etc). Also, are there any security implications with [wordexp](https://manpage.me/?q=wordexp)?