summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNate Sesti <sestinj@gmail.com>2023-09-01 18:31:33 -0700
committerNate Sesti <sestinj@gmail.com>2023-09-01 18:31:33 -0700
commit2f792f46026a6bb3c3580f2521b01ecb8c68117c (patch)
tree36cecf6d218bc166c0a8c1c78261b4feac7f01cd /docs
parent5c8b28b7fddf5b214de61102c768ef44d4087870 (diff)
downloadsncontinue-2f792f46026a6bb3c3580f2521b01ecb8c68117c.tar.gz
sncontinue-2f792f46026a6bb3c3580f2521b01ecb8c68117c.tar.bz2
sncontinue-2f792f46026a6bb3c3580f2521b01ecb8c68117c.zip
feat: :sparkles: improved model dropdown
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/troubleshooting.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/docs/docs/troubleshooting.md b/docs/docs/troubleshooting.md
index 2f7c12ae..70dec2bf 100644
--- a/docs/docs/troubleshooting.md
+++ b/docs/docs/troubleshooting.md
@@ -50,10 +50,6 @@ If your Continue server is not setting up, try checking the console logs:
3. Select `Console`
4. Read the console logs
-## Meilisearch on Windows
-
-As of now Windows users must manually download and start Meilisearch to use the '@' context referencing feature. To do so, follow the instructions here: https://www.meilisearch.com/docs/learn/getting_started/installation. Alternatively, you can track our progress on support for Meilisearch on Windows here: https://github.com/continuedev/continue/issues/408. Once Meilisearch is up and running on http://localhost:7700, Continue should be able to automatically connect. You may just have to reload the VS Code window first.
-
## Still having trouble?
Create a GitHub issue [here](https://github.com/continuedev/continue/issues/new?assignees=&labels=bug&projects=&template=bug-report-%F0%9F%90%9B.md&title=), leaving the details of your problem, and we'll be able to more quickly help you out.