Weird behaviour with deno autocomplete
I thought it was because of my terminal so I uninstalled deno and re-installed it with
cargo and I have this behaviour again. When I start typing deno run for example, if I use tab to autocomplete with a local file, I get this and it breaks the command line. I don't know if it's a known issue or if it's related to my configuration but I didn't experience that on older versions of Deno 🤔
2 Replies
I wasn't able to find the answer to your question in the official Deno documentation. However, based on the information you've provided, it seems like there might be an issue with your shell's autocomplete configuration rather than with Deno itself.
Please note that the advice I'm providing is not based on the Deno documentation, and I would advise you to double-check the accuracy of the advice given. If you're experiencing issues with shell autocompletion, it could be related to the shell you're using or the specific configuration for autocompletion scripts.
One thing you could try is to ensure that your shell's completion scripts for Deno are correctly installed and sourced. For example, if you're using bash, you might need to source the Deno completion script in your
.bashrc or .bash_profile. If you're using a different shell like zsh or fish, the process might be different.
If the issue persists, it might be helpful to check if there are any open issues on the Deno GitHub repository or to open a new issue with details about your environment and the problem you're encountering. This way, the Deno community and maintainers can provide assistance and potentially fix any bugs related to autocompletion.Helpful Links:
Deno 1.12 Release Notes
Deno 1.21 Release Notes
Deno 1.17 Release Notes
Deno 1.23 Release Notes
Using Visual Studio Code | Deno Docs
Deno 1.37: Modern JavaScript in Jupyter Notebooks
Import Completions and Intelligent Registries
Import path autocomplete doesn't work - Deno
Command Line Interface
Deno is well sourced from the cargo path, it is available from the command line, it just acts weird when I try to autocomplete the rest of the command, and it does not do that with other binaries :/