Skip to content

feat: send $/lean/fileProgress notification #510

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.

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

Merged
merged 2 commits into from
Jun 5, 2021

Conversation

gebner
Copy link
Member

@gebner gebner commented Jun 4, 2021

Closes #503.

The vscode implemention is already deployed.

Copy link
Member

@Vtec234 Vtec234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also send a progress update after compiling the header? This would be a publishProgressAtPos after FileWorker.lean:208. The headerSnap should have the right endPos. Oh well, I guess nextCmdSnap will do it, so this was a useless suggestion.

Looks good, thanks!

@Kha Kha merged commit f50647e into leanprover:master Jun 5, 2021
@Kha
Copy link
Member

Kha commented Jun 5, 2021

Guess I'll have to think about what to do in Emacs now... 😬

ChrisHughes24 pushed a commit to ChrisHughes24/lean4 that referenced this pull request Dec 2, 2022
The support for `Max` and `Min` classes is still somewhat minimal (no pun intended). The relevant files still require proper porting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Progress notification server protocol extension proposal
3 participants