3.0 and beyond #1997
Replies: 5 comments 1 reply
-
|
Virtual lines, to me, is the other big one. It's pretty breaking for API so I'd say that one's also non negotiable. |
Beta Was this translation helpful? Give feedback.
-
I'll edit when more come to mind. |
Beta Was this translation helpful? Give feedback.
-
also I agree with @Guldoman |
Beta Was this translation helpful? Give feedback.
-
For this, please head over to https://github.com/lite-xl/lite-xl-plugin-manager and post an issue; I'd be happy to discuss over there. The interface doesn't have to move in lockstep with LXL, so we can potentially do this earlier if you have some good ideas. |
Beta Was this translation helpful? Give feedback.
-
Also, the general design philosophy of lite-xl is aimed at being minimal; so a lot of stuff being provided by plugins is actually a design goal, rather than a drawback. Multi-cursors however, is a feature that is directly in the core editor, so no worries there; it's already in core. Settings isn't for a variety of reasons; but IMO mainly due to the fact that the core way of modifying settings via lua code is a lot more flexible than the settings plugin, and not everyone wants the GUI interface for it. It is however bundled with the editor upon release for those who want it, so we do get a bit of the best of both worlds with this approach. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It's 2025 and we need to define what is 3.0, and how we can achieve 3.0. First, we need to discuss a list of features, mostly breaking changes, that is required to each 3.0.
Everyone is welcome to pitch ideas for any breaking changes. The concrete ones are to have Project Rework (#1455), I don't know about others.
Beta Was this translation helpful? Give feedback.
All reactions