diff options
| -rw-r--r-- | lsp-parse.c | 16 | ||||
| -rw-r--r-- | main.c | 1 |
2 files changed, 2 insertions, 15 deletions
diff --git a/lsp-parse.c b/lsp-parse.c index 0c75acf..86a223d 100644 --- a/lsp-parse.c +++ b/lsp-parse.c @@ -327,20 +327,8 @@ static void process_message(LSP *lsp, JSON *json) { JSONValue error = json_get(json, "error.message"); if (error.type == JSON_STRING) { char err[256] = {0}; - json_string_get(json, error.val.string, err, sizeof err);; - - if (streq(err, "waiting for cargo metadata or cargo check")) { - // fine. be that way. i'll resend the goddamn request. - // i'll keep bombarding you with requests. - // maybe next time you should abide by the standard and only send an initialize response when youre actually ready to handle my requests. fuck you. - if (response_to.type) { - lsp_send_request(lsp, &response_to); - // don't free - memset(&response_to, 0, sizeof response_to); - } - } else { - lsp_set_error(lsp, "%s", err); - } + json_string_get(json, error.val.string, err, sizeof err); + printf("%s\n",err); goto ret; } @@ -11,7 +11,6 @@ - run everything through valgrind ideally with leak checking - rust-analyzer bug reports: - bad json can give "Unexpected error: client exited without proper shutdown sequence" - - rust-analyzer should wait until cargo metadata/check is done before sending initialize response FUTURE FEATURES: - robust find (results shouldn't move around when you type things) - multiple files with command line arguments |