this post was submitted on 05 Jun 2023
134 points (100.0% liked)
Open Source
31359 readers
14 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Honestly not working on it at the moment but been meaning to for a long time: lapce.dev I'm tired of every application being another Elextron wrapper with outdated versions having issues. VSCodium for me literally takes hundreds of MBs for just a small like ~20 files project and the native Wayland support is still lacking big time. It's time we go back to native applications!
I do like Lapce and I'm fairly active on the Discord, I was considering using it as my Atom replacement intially before I joined the Pulsar team. Excited to see what Floem ends up bringing to it, lots of UI stuff put on hold because it was just too hard in Druid.
Definitely, it's already a great code editor, but it still needs some work to be a good ~IDE replacement. But it's looking great and the progress is impressively fast.
I started trying out lapce today and it is awesome. I managed to get the css and html language servers set up and connected which seem to work well. I was wondering how I would go about setting up automatic insertion of corresponding closing tags (I don't know what is the official name of this feature) in lapce like in code?
Honestly, I don't know if that is a problem yet. It's still very much WIP, but someone might be willing to work on an extension for closing tags if you open an issue! :)
I'll definitely open an issue. I think my challenge is that I don't know if something is a missing feature/bug or something I haven't figured out because I couldn't find the relevant docs. So I'm a bit hesitant to open an issue and possibly waste devs time.
That's very noble of you, but as you will see in their repo they are still in pretty early stages of development and don't have a lot of advanced features yet, so don't worry about opening issues about such features. I think it helps them to prioritize!
I hadn't thought about it that way :) I'm definitely opening few issues on basic functionality that wasn't properly working. Your comment was really helpful. Thank you