Stuck in YYZ for three hours, so naturally I'm wrestling with Codeium in my editor. The "enhanced" suggestions (read: aggressive completions) are fine for my Python scripts, but they're actively hostile when I'm editing config files.
Example: every time I tab into a `.yaml` or `.toml` file, it tries to autocomplete entire, often incorrect, blocks. It's like an overeager intern who hasn't learned about idempotence yet.
I know I can turn it off globally, but I don't want to. I just want to disable the fancier, multi-line suggestions for specific file types/extensions. Is there a:
* Editor-specific setting (using VSCode)?
* Codeium config block I can drop in my project?
* Or is this a "all or nothing" toggle buried in the dashboard?
Status page is my homepage.
Ah, the overeager intern analogy is perfect, I know exactly what you mean. You're in luck, it's not an all-or-nothing toggle.
For VSCode, check your workspace settings for `codeium.enable_per_language_configuration`. Set that to true, then you can add a `codeium.languages` object. Inside it, you can set suggestions for 'yaml' or 'toml' to 'disabled' or maybe just 'basic' if that's an option. That should let you keep the Python help while taming the config files.
Safe travels out of YYZ.
Remember the rules
Oh, the config file struggle is real! I've had the exact same fight with `.json` files, where it suggests a whole nested structure that's completely wrong for the schema. Your "overeager intern" is spot on.
The per-language config that user194 mentioned is definitely the way to go. One caveat I found: sometimes you need to restart VSCode after setting `enable_per_language_configuration` for the `languages` object to be recognized properly.
Also, setting it to 'basic' vs 'disabled' is a good middle ground. It'll still offer single-word or line completions in your YAML, which can be handy for repeating keys, but it stops trying to write the whole spec for you. Safe travels!
automate the boring stuff
Great analogy with the overeager intern, that's exactly the feeling. Following the per-language setting advice, have you checked your vendor's SLA for these kind of configuration updates? Sometimes these settings reset after an extension update, and I'm curious if that's considered a service disruption or just expected behavior.