-
-
Notifications
You must be signed in to change notification settings - Fork 23
FAQ
Some common questions about cord.nvim that nobody asked, yet we answered anyway. If you don't find your answer here or in the Troubleshooting Guide, don't hesitate to ask in our Discord community or GitHub Discussions!
Cord is compatible with Neovim 0.6.0 or newer.
No, you don't need Rust anymore. Cord will download the server binary for you. If you'd rather build it yourself, check the Build guide.
You can check the logs in two ways:
- Set a log level in your config. Messages at that level (and higher) will show up in
:messages.
require 'cord'.setup {
log_level = '...' -- one of 'trace', 'debug', 'info', 'warn', 'error'
}- Set the
CORD_LOG_FILEenvironment variable to a file path. This saves logs to a file instead of spamming your editor, which is especially useful when usingtraceordebuglevels.
Note
If you were asked to provide logs as part of an issue, you should enable verbose logging via log_level = 'trace' and set CORD_LOG_FILE environment variable. Use of relative paths is allowed, e.g. export CORD_LOG_FILE="./cord.log". The log file gets cleared at plugin startup, so keep that in mind.
To do this, you will have to create an application with the desired name in the Discord Developer Portal.
Then, copy its application ID and put it in the editor.client field:
require 'cord'.setup {
editor = {
client = '01234567890123456789'
}
}That's intentional.
Cord's server keeps running to maintain a single continuous connection to Discord and avoid hitting rate limits from reconnecting too often.
This is especially useful if you restart Neovim a lot.
If you'd rather shut it down sooner, there's the advanced.server.timeout option.
See Special Environments.
Cord detects buffers mostly by filetype (and sometimes by filename). Check the list of supported filetypes here.
If the language or plugin you use isn't found on the list, please open an issue.
Just keep in mind:
- Languages that don't expose a clear filetype or filename need extra setup (see this page).
-
Plugins need to override the buffer's
filetype, otherwise Cord won't be able to recognize them.
After the recent update, Discord started to properly rate-limit how often your Rich Presence can update. The exact numbers aren't known yet.
Not caused by Cord. See the discussion for details.
Disabling timestamps was previously possible but Discord appears to have introduced a bug. If you omit the timestamp now, it starts to misbehave, with the timer initially briefly disappearing but then reappearing and resetting to zero whenever the activity updates. No can do on our end.
Not caused by Cord. See the discussion for details.