Feature Request: Allow specifying paths relative to XDG user dir variables (${DOWNLOADS}/something
, ${PICTURES}/something
...)
#4653
Labels
duplicate
This issue or pull request already exists
The problem
Currently, we can reference XDG user dirs by variables regardless of their actual name:
${DOWNLOADS}
,${DOCUMENTS}
,${PICTURES}
,${VIDEOS}
,${MUSIC}
.Many programs use these directories only to create its own directory inside and use it for its purposes.
For example:
Telegram Desktop creates and defaults to
"Telegram Desktop"
directory inside${DOWNLOADS}
for its downloadsFlameshot defaults to
Screenshots
directory inside${PICTURES}
to save its screenshotsIdeally the profiles must only
whitelist
these default directories to allow default behaviour and deny everything else.But the only way to allow these dirs and not depend on any hardcoded names is to
whitelist
/noblacklist
the entire${DOWNLOADS}
/${PICTURES}
, as currently we get an error by trying to specify paths relative to XDG user dir variable:telegram-desktop.local:
The only way to go around that right now is to hardcode directory names relative to ${HOME} variable:
telegram-desktop.local:
/etc/firejail/keepassxc.profile:
Describe the solution you'd like
Allow specifying paths relative to XDG user dir variables as with
${HOME}
variable:Additional context
Even if we consider XDG user dirs to be "public" for use by media programs by default, one can't even change that personally without hardcoding relative to
${HOME}
. What if you renamed your XDG user dirs later, e.g.Downloads
->downloads
?The text was updated successfully, but these errors were encountered: