Skip to content

update roadmap #231

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

Closed
wants to merge 1 commit into from
Closed

update roadmap #231

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion roadmap.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,9 +36,13 @@ <h3><a href="https://github.com/neovim/neovim/milestone/19">0.5</a></h3>
<li>Extended marks (text properties, decorations, virtual text)</li>
Copy link
Member

@justinmk justinmk Jul 3, 2021

Choose a reason for hiding this comment

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

i don't think 0.5 has Lua remote plugin host, so that should be moved to 0.6 also?

</ul>

<h3>0.6</h3>
<h3><a href="https://github.com/neovim/neovim/milestone/11">0.6</a></h3>
<ul>
<li>Better file-change detection</li>
<li>Terminal UI as a remote UI</li>
<li>Virtual lines (think virtualtext but on new lines)</li>
<li>Improved folds</li>
<li>Diagnostic API</li>
Copy link
Member

@justinmk justinmk Jul 3, 2021

Choose a reason for hiding this comment

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

assuming this is for LSP, or is a general UI subsystem enhancement?

Suggested change
<li>Diagnostic API</li>
<li>LSP: Diagnostic API</li>

Copy link
Member

@bfredl bfredl Jul 3, 2021

Choose a reason for hiding this comment

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

I think it is meant to be generic, i e reuse the LSP UI logic even for non-LSP sources

Copy link
Member

@clason clason Jul 3, 2021

Choose a reason for hiding this comment

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

Yes, the motivation was for people to (be able to) stop shoehorning random linters into LSP via null-ls or efm while still getting decent-looking diagnostics (that don't fight each other).

</ul>

<h3>Future/Long-term</h3>
Expand Down