Allow brittany to run when it can't write a global config file #226
Labels
No Label
blocked: dependency
blocked: info-needed
bug
duplicate
enhancement
fixed in HEAD
help wanted
hs:arrows
hs:brackets
hs:classes
hs:comments
hs:do-notation
hs:guards
hs:lists
hs:operators
hs:patterns
hs:records
hs:types
invalid
language extension support
layouting
needs confirmation
priority: high
priority: low
question
revisit before next release
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: hexagoxel/brittany#226
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
My use case is running brittany in a sandbox, providing it exactly one
.brittany.yamlconfig file, and not letting brittany do anything except write tostdout. There are no environment variables in this sandbox.I have two problems. One is that brittany calls
Directory.getAppUserDataDirectory(viareadConfigsWithUserConfiganduserConfigPath) which throws an exception when the environment variableHOMEis not defined.The second is that if I define the env var
HOMEthen brittany tries to write a config file there, but it has no write permissions in this sandbox.Is it possible to run brittany in a "pure" mode where it doesn't write a global config file?
I would also love to have the option for brittany to not touch
$HOME. Sadly, setting--config-fileflag does not seem to prevent$HOMEaccess.