{"action":"created","issue":{"url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/issues/603","repository_url":"https://api.github.com/repos/autozimu/LanguageClient-neovim","labels_url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/issues/603/labels{/name}","comments_url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/issues/603/comments","events_url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/issues/603/events","html_url":"https://github.com/autozimu/LanguageClient-neovim/issues/603","id":359003756,"node_id":"MDU6SXNzdWUzNTkwMDM3NTY=","number":603,"title":"Feature request - Delay presenting diagnostics (or suppress highlighting)","user":{"login":"smhc","id":6404304,"node_id":"MDQ6VXNlcjY0MDQzMDQ=","avatar_url":"https://avatars1.githubusercontent.com/u/6404304?v=4","gravatar_id":"","url":"https://api.github.com/users/smhc","html_url":"https://github.com/smhc","followers_url":"https://api.github.com/users/smhc/followers","following_url":"https://api.github.com/users/smhc/following{/other_user}","gists_url":"https://api.github.com/users/smhc/gists{/gist_id}","starred_url":"https://api.github.com/users/smhc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smhc/subscriptions","organizations_url":"https://api.github.com/users/smhc/orgs","repos_url":"https://api.github.com/users/smhc/repos","events_url":"https://api.github.com/users/smhc/events{/privacy}","received_events_url":"https://api.github.com/users/smhc/received_events","type":"User","site_admin":false},"labels":[{"id":906295770,"node_id":"MDU6TGFiZWw5MDYyOTU3NzA=","url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/labels/feature%20request","name":"feature request","color":"189eaf","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-09-11T11:27:38Z","updated_at":"2018-09-14T01:55:41Z","closed_at":null,"author_association":"NONE","body":"## Is your feature request related to a problem? Please describe.\r\n\r\nDiagnostics information in the gutter, and especially highlighting, can be quite distracting when writing code. More often than not code that is in the process of being written is invalid until it is completed, either by ending the line, or exiting insert mode. This effectively results in the text and gutter flickering unnecessarily in the area that you are trying to focus on.\r\n\r\n## Describe the solution you'd like\r\n\r\nOne or more of the below solutions may be viable;\r\n\r\n- Diagnostics delayed on a timer, reset at each keypress\r\n- Diagnostics deferred being presented until exiting edit mode (or a new line)\r\n- An ability to turn off highlighting when in edit mode, or altogether\r\n- Use g:LanguageClient_changeThrottle, but with an ability to force a 'sync' just prior to autocompletion trigger\r\n\r\n## Describe alternatives you've considered\r\n\r\nSetting texthl to an empty string hides the highlighting, but it is still gets applied, affecting performance. It'd also be nice to see the highlighting, but when viewing code rather than trying to write it. The gutter signs are also present:\r\n\r\n```vim\r\nlet g:LanguageClient_diagnosticsDisplay = {       \r\n...\r\n \"texthl\": \"\", \r\n```\r\n\r\nI could try setting 'g:LanguageClient_changeThrottle', however this has an impact on autocompletion. \r\n"},"comment":{"url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/issues/comments/421205983","html_url":"https://github.com/autozimu/LanguageClient-neovim/issues/603#issuecomment-421205983","issue_url":"https://api.github.com/repos/autozimu/LanguageClient-neovim/issues/603","id":421205983,"node_id":"MDEyOklzc3VlQ29tbWVudDQyMTIwNTk4Mw==","user":{"login":"smhc","id":6404304,"node_id":"MDQ6VXNlcjY0MDQzMDQ=","avatar_url":"https://avatars1.githubusercontent.com/u/6404304?v=4","gravatar_id":"","url":"https://api.github.com/users/smhc","html_url":"https://github.com/smhc","followers_url":"https://api.github.com/users/smhc/followers","following_url":"https://api.github.com/users/smhc/following{/other_user}","gists_url":"https://api.github.com/users/smhc/gists{/gist_id}","starred_url":"https://api.github.com/users/smhc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/smhc/subscriptions","organizations_url":"https://api.github.com/users/smhc/orgs","repos_url":"https://api.github.com/users/smhc/repos","events_url":"https://api.github.com/users/smhc/events{/privacy}","received_events_url":"https://api.github.com/users/smhc/received_events","type":"User","site_admin":false},"created_at":"2018-09-14T01:55:41Z","updated_at":"2018-09-14T01:55:41Z","author_association":"NONE","body":"Throttling certainly breaks autocomplete for me until you trigger enough updates for the throttle timeout to expire. \r\n\r\nOn a side note the throttling looks like it might have another bug - it only causes some updates to be skipped. There doesn't appear to be a timer set up to trigger an update after the delay. It should be resetting a timer on each keypress/update attempt such that it will trigger the actual update when that timer expires without being reset again."}}
{"actor":{"display_login":"smhc"}}