-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can edit and save preferences but they're not applied #137
Comments
That seems fine. Did you edit the preferences using the |
Yes, initially via preferences::edit, which saved them to ~/.config/amp/config.yml. Is there a way to display which config file is in use after launching amp? |
Sadly, no, there isn't. However, you can call the |
Thanks for the tip. No errors thrown unfortunately! |
There isn't; the intent is for this to be bulletproof, but clearly it isn't! Can you try putting a type-specific tab width to see if that applies? I'm not 100% convinced that it's the preference file not being read; it might be that the open buffer isn't triggering those global configuration rules, as weird as that may be. 🙂 |
Very true -- correctness != bug-free :) I tried an 'rs' type with a ridiculous width (17 spaces) and that worked perfectly. So I think you're right -- global rules aren't working but type-specific ones are. |
Nice! I'm curious if the file type itself is confusing the classifier. Can you remove the type-specific configuration and try the global |
OK. that worked too. So maybe it's particular settings that aren't working? |
Hmm, |
A good point. I tend to use dark terminal themes, however I have different dark themes in xfce4-terminal, xterm, sakura and guake and the guide didn't show in any of them. Same appears to be the case for line_wrapping -- not currently applying either. My uneducated guess is that both these settings are closely related somehow and that they're being prevented by the same thing... |
I just set and saved a few simple preferences:
On restarting amp, none of these were applied. Amp was installed via cargo build in Devuan Ascii.
Am I missing a step somewhere?
The text was updated successfully, but these errors were encountered: