Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nano-ycmd with clang 3.9.1 doesn't show FixIt 100% time but randomly #1

Open
orsonteodoro opened this issue Feb 12, 2017 · 2 comments
Open

nano-ycmd with clang 3.9.1 doesn't show FixIt 100% time but randomly #1

orsonteodoro opened this issue Feb 12, 2017 · 2 comments
Labels
bug

Comments

@orsonteodoro
Copy link
Owner

This needs a fix because it is slowing productivity. The system is not predictable and FixIts are randomly made available to the user far less than expected.

Also, DiagnosticResponse doesn't show an immediate updated list of FixIts after a trivial problem has been immediately introduced.

It could be a problem with clang, ycmd, or nano-ycmd. I don't know.
@orsonteodoro
Copy link
Owner Author

It could be related to enough time between parses. Having transitioned /run_completer_command FileReadyToParse to react to alarm than to keypress/character added to nano's open buffer, the problem seems to have disappeared.

@orsonteodoro
Copy link
Owner Author

It still suffers from the same problem. Also there is no replacement text in the response body of the response of FileReadyToParse.

@orsonteodoro orsonteodoro reopened this Feb 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@orsonteodoro