mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #271] Allow Spaces in Directory Paths #189
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#189
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ilikenwf on GitHub (Jan 29, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/271
I have already tried escaping , as well as encapsulating with both single and double quotes, but due to the fact that Pale Moon's developer thought using "~/.moonchild productions" was ok for the browser's directory, firejail doesn't play nice with it.
Currently I'm using a copy of my firefox.profile for palemoon, modified with ~/.palemoon as the directory, with a custom built version of Pale Moon configured to use ~/.palemoon instead (this isn't JUST because of firejail, I like building this myself)...
Because we like standardization, it would be nice if you could either add space functionality for paths, or educate me if there is one already so we can have a default profile for pale moon as well - it is gaining in popularity as Firefox bloats and adds privacy intrusive features.
@dshmgh commented on GitHub (Jan 29, 2016):
Just put the path in verbatim with the spaces and no type of quoting. The path parsing is not standard unix shell. This fooled me too until I accidentally tried without any quoting. Perhaps the profile man page needs a mention?
@ilikenwf commented on GitHub (Jan 30, 2016):
Ah, that makes sense. It would be extremely helpful if someone would add an example to the manpages.
@netblue30 commented on GitHub (Jan 30, 2016):
I'll try to bring in a Pale Moon profile.
@netblue30 commented on GitHub (Feb 1, 2016):
Added it to my list of things to do/