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
Work in progress on reimplementing existing features from Druid Lapce in Floem Lapce #2417
Comments
Wayland support is also no longer a thing. |
And basically nothing works on macos anymore |
Can you be more specific? I believe dzhou uses the editor on macos, so editing works (etc). Is there a specific feature that's missing? A specific integration with MacOS? |
|
Thanks. I'll add those to the list and discuss them.
Which specific LSP? |
Rust |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
as I said, that is expected, we're rewriting most of the codebase, use stable release if you want working editor |
Are there only these tasks to handle? There are still many differences when I run the floem version. |
These are the only written down. If something is missing, it should be noted here. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as off-topic.
This comment was marked as off-topic.
On macOS (and linux probably?) the keybindings are weird for colemak. Instead of using real keystrokes, lapce seems to use "places" on the keyboard. For example to press Cmd+N and create a new file, one should press Cmd+K, as the position of K in Colemak coincides with position of N in QWERTY. This should be changed, so lapce would use real key inputs and not their places (see #2800) |
Also #2801 |
@MinusGix mind adding this two to the list? Also menu bar support on macOS seems to be long gone again |
The Floem (UI library) version of Lapce
will behas been merged into themaster
branchsoon. Once that occurs, bringing it completely up to feature parity with the druid version of Lapce is needed. There is a variety of missing features, some of which were skipped over and some of which have happened since the fork, that need to be reimplemented.Easy: Features that are just a matter of porting code over
WorkbenchCommand::OpenLogFile
(feat: replace log with tracing and implement observability #2466)Medium: May need a good amount of changes and work
Hard: May be intricate to implement, even with the existing implementation. Either due to backend differences or other problems.
The text was updated successfully, but these errors were encountered: