From 327ddbe2b49b80c72d43590a633ca135b0654e06 Mon Sep 17 00:00:00 2001
From: Nathan Sobo <nathan@zed.dev>
Date: Mon, 31 Jan 2022 18:34:20 -0700
Subject: [PATCH] Always issue a new completions request when typing a trigger
 character

We'll interpolate the anchor range of original request, but it's still a good idea to be up-to-date in case the language server is influenced by the content preceding the location. This doesn't *seem* to be the case with rust-analyzer so far, but it's how VS Code works so let's do it this way.
---
 crates/editor/src/editor.rs | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/crates/editor/src/editor.rs b/crates/editor/src/editor.rs
index 4e383d5518f5ad6525e6b0c3caf412c03c171e79..1f892369eee35ef86bcc0e93521083077867f2aa 100644
--- a/crates/editor/src/editor.rs
+++ b/crates/editor/src/editor.rs
@@ -1390,15 +1390,13 @@ impl Editor {
     }
 
     fn trigger_completion_on_input(&mut self, text: &str, cx: &mut ViewContext<Self>) {
-        if self.completion_state.is_none() {
-            if let Some(selection) = self.newest_anchor_selection() {
-                if self
-                    .buffer
-                    .read(cx)
-                    .is_completion_trigger(selection.head(), text, cx)
-                {
-                    self.show_completions(&ShowCompletions, cx);
-                }
+        if let Some(selection) = self.newest_anchor_selection() {
+            if self
+                .buffer
+                .read(cx)
+                .is_completion_trigger(selection.head(), text, cx)
+            {
+                self.show_completions(&ShowCompletions, cx);
             }
         }
     }