Closed sjmackenzie closed 5 years ago
Hi @sjmackenzie! Thanks for filing this bug. :slightly_smiling_face:
Looks like this line is to blame. We should be falling back to a default theme if a custom one can't be found, and only raising an error if the fallback fails.
Steps to reproduce:
amp = "0.5.2"
usingbeta
ornightly
)<shft>-q
Expected behaviour
Actual behaviour
<shft>-q
exits and the editor edits and saves files.System conf
Further notes:
I worry I might have mistyped something in the config file and
amp
sulked. 1) where is the default config.yaml file normally 2) have you seen this issue before.Update
okay the problem was
theme: solazized_dark
(note the spelling mistake) in the~/.config/amp/config.yml
file. Might be good to have more robust parsing of the yaml file.