home.social

#lapce — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #lapce, aggregated by home.social.

  1. I managed to hack together a #zed / #gram extension to provide FASTA language support:

    gitlab.com/jrhawley/gram-zed-f

    tree-sitter-fasta.jrhawley.ca/

    I tried to write instructions for #lapce but it looks like all languages need to be defined in the Lapce code base for compilation 🫤 That puts a damper on that plan.

    And #emacs tree-sitter support feels like a moving target. I'd have to manually redefine a lot of font locks and other stuff.

    This process isn't as smooth as I'd hoped

  2. I managed to hack together a #zed / #gram extension to provide FASTA language support:

    gitlab.com/jrhawley/gram-zed-f

    tree-sitter-fasta.jrhawley.ca/

    I tried to write instructions for #lapce but it looks like all languages need to be defined in the Lapce code base for compilation 🫤 That puts a damper on that plan.

    And #emacs tree-sitter support feels like a moving target. I'd have to manually redefine a lot of font locks and other stuff.

    This process isn't as smooth as I'd hoped

  3. I managed to hack together a #zed / #gram extension to provide FASTA language support:

    gitlab.com/jrhawley/gram-zed-f

    tree-sitter-fasta.jrhawley.ca/

    I tried to write instructions for #lapce but it looks like all languages need to be defined in the Lapce code base for compilation 🫤 That puts a damper on that plan.

    And #emacs tree-sitter support feels like a moving target. I'd have to manually redefine a lot of font locks and other stuff.

    This process isn't as smooth as I'd hoped

  4. I managed to hack together a #zed / #gram extension to provide FASTA language support:

    gitlab.com/jrhawley/gram-zed-f

    tree-sitter-fasta.jrhawley.ca/

    I tried to write instructions for #lapce but it looks like all languages need to be defined in the Lapce code base for compilation 🫤 That puts a damper on that plan.

    And #emacs tree-sitter support feels like a moving target. I'd have to manually redefine a lot of font locks and other stuff.

    This process isn't as smooth as I'd hoped

  5. Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
    The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
    I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
    Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
    I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
    edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. lap.dev/floem/ :moomin_yay:
    The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

  6. Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
    The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
    I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
    Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
    I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
    edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. lap.dev/floem/ :moomin_yay:
    The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

  7. Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
    The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
    I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
    Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
    I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
    edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. lap.dev/floem/ :moomin_yay:
    The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

  8. Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
    The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
    I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
    Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
    I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
    edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. lap.dev/floem/ :moomin_yay:
    The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

  9. Giving #Lapce a try, so far I really like it. It's like a lighter weight #VSCode. I especially like that it doesn't seem to use #Electron.
    The choice of #WASM as scripting language is interesting, I'll be curious to see how it fares for one-off scripting tasks.
    I also like that it addresses my two biggest gripes with #Emacs: startup and input latency.
    Also, no LLM crap being shoved in my face! I don't know if the company behind it is involved with genAI stuff, but if they are, at least they aren't shoving it into their editor. :neofox_uwu:
    I also tried its modal editing mode, it's pretty nice being able to use some of the same commands that I'm used to from #DoomEmacs .
    edit: Read the description of its #GUI backend, hecc, it ticks almost all of my boxes. lap.dev/floem/ :moomin_yay:
    The one thing I miss from that feature list is a focus on #accessibility . :moomin_sad:

  10. I was always curious about the Xi editor, sad that it never really took off. Just learned about Lapce, described as a “spiritual successor” to Xi

    lap.dev/lapce/

    github.com/lapce/lapce

    github.com/xi-editor/xi-editor

    #Xi #Lapce #TextEditors

  11. I was always curious about the Xi editor, sad that it never really took off. Just learned about Lapce, described as a “spiritual successor” to Xi

    lap.dev/lapce/

    github.com/lapce/lapce

    github.com/xi-editor/xi-editor

    #Xi #Lapce #TextEditors

  12. I was always curious about the Xi editor, sad that it never really took off. Just learned about Lapce, described as a “spiritual successor” to Xi

    lap.dev/lapce/

    github.com/lapce/lapce

    github.com/xi-editor/xi-editor

  13. I was always curious about the Xi editor, sad that it never really took off. Just learned about Lapce, described as a “spiritual successor” to Xi

    lap.dev/lapce/

    github.com/lapce/lapce

    github.com/xi-editor/xi-editor

    #Xi #Lapce #TextEditors

  14. I was always curious about the Xi editor, sad that it never really took off. Just learned about Lapce, described as a “spiritual successor” to Xi

    lap.dev/lapce/

    github.com/lapce/lapce

    github.com/xi-editor/xi-editor

    #Xi #Lapce #TextEditors

  15. @mattesilver None. #RustRover is written in #Kotlin and has #JetBrains' own analyser for #Rust. Plus it's proper IDE, kind of heavy.

    #Lapce, #Zed, #VSCode are editors running #rust-analyzer in the background using LSP. They're much more lightweight, less feature bloated.

    It's really matter of taste and preference what to choose.

  16. @mattesilver None. #RustRover is written in #Kotlin and has #JetBrains' own analyser for #Rust. Plus it's proper IDE, kind of heavy.

    #Lapce, #Zed, #VSCode are editors running #rust-analyzer in the background using LSP. They're much more lightweight, less feature bloated.

    It's really matter of taste and preference what to choose.

  17. @mattesilver None. #RustRover is written in #Kotlin and has #JetBrains' own analyser for #Rust. Plus it's proper IDE, kind of heavy.

    #Lapce, #Zed, #VSCode are editors running #rust-analyzer in the background using LSP. They're much more lightweight, less feature bloated.

    It's really matter of taste and preference what to choose.

  18. @mattesilver None. #RustRover is written in #Kotlin and has #JetBrains' own analyser for #Rust. Plus it's proper IDE, kind of heavy.

    #Lapce, #Zed, #VSCode are editors running #rust-analyzer in the background using LSP. They're much more lightweight, less feature bloated.

    It's really matter of taste and preference what to choose.

  19. @mattesilver None. #RustRover is written in #Kotlin and has #JetBrains' own analyser for #Rust. Plus it's proper IDE, kind of heavy.

    #Lapce, #Zed, #VSCode are editors running #rust-analyzer in the background using LSP. They're much more lightweight, less feature bloated.

    It's really matter of taste and preference what to choose.

  20. @thewhalecc Unfortunately #Lapce stays behind #Zed in terms of usability term.

  21. @thewhalecc Unfortunately #Lapce stays behind #Zed in terms of usability term.

  22. @thewhalecc Unfortunately #Lapce stays behind #Zed in terms of usability term.

  23. @thewhalecc Unfortunately #Lapce stays behind #Zed in terms of usability term.

  24. 𝗟𝗮𝗽𝗰𝗲:

    #Editor #Rust #Open Source #Code #IDE #Lapce

    thewhale.cc/posts/lapce

    A modern open source code editor in Rust. Lightning-fast and Powerful. Quick from launch to every keystroke, and batteries included.

  25. 𝗟𝗮𝗽𝗰𝗲:

    #Editor #Rust #Open Source #Code #IDE #Lapce

    thewhale.cc/posts/lapce

    A modern open source code editor in Rust. Lightning-fast and Powerful. Quick from launch to every keystroke, and batteries included.

  26. 𝗟𝗮𝗽𝗰𝗲:

    #Editor #Rust #Open Source #Code #IDE #Lapce

    thewhale.cc/posts/lapce

    A modern open source code editor in Rust. Lightning-fast and Powerful. Quick from launch to every keystroke, and batteries included.

  27. 𝗟𝗮𝗽𝗰𝗲:

    #Editor #Rust #Open Source #Code #IDE #Lapce

    thewhale.cc/posts/lapce

    A modern open source code editor in Rust. Lightning-fast and Powerful. Quick from launch to every keystroke, and batteries included.

  28. 𝗟𝗮𝗽𝗰𝗲:

    #Editor #Rust #Open Source #Code #IDE #Lapce

    thewhale.cc/posts/lapce

    A modern open source code editor in Rust. Lightning-fast and Powerful. Quick from launch to every keystroke, and batteries included.

  29. @argv_minus_one @shye

    I don't think anything "went wrong" at all, except a couple of behaviours that I didn't like. Something that comes to mind is how #lapce somehow ended the default program to open text files, which felt a bit overkill for me.

    The keyboard shortcuts didn't work sometimes, only after clicking somewhere into the window. For a keyboard-centric user like me that felt irritating.

    And eventually, I felt it was more akin to a GUI editor than an IDE much. And therefore not something I'm interested in, because I have that with (g) #vim and I don't need another one 🙂

    But I also barely scratched the surface with lapce, so it's possible that it has a lot of functionality other people would like. It just wasn't my thing *enough* to keep at it. But there's certainly nothing wrong with it!

  30. @argv_minus_one @shye

    I don't think anything "went wrong" at all, except a couple of behaviours that I didn't like. Something that comes to mind is how #lapce somehow ended the default program to open text files, which felt a bit overkill for me.

    The keyboard shortcuts didn't work sometimes, only after clicking somewhere into the window. For a keyboard-centric user like me that felt irritating.

    And eventually, I felt it was more akin to a GUI editor than an IDE much. And therefore not something I'm interested in, because I have that with (g) #vim and I don't need another one 🙂

    But I also barely scratched the surface with lapce, so it's possible that it has a lot of functionality other people would like. It just wasn't my thing *enough* to keep at it. But there's certainly nothing wrong with it!

  31. @argv_minus_one @shye

    I agree. I tried #lapce but I've eventually given up and now I just use #vim . It's a shame that we don't have good IDEs.

    I haven't tried Kate but isn't that more an editor than a full-fledged IDE?

  32. @argv_minus_one @shye

    I agree. I tried #lapce but I've eventually given up and now I just use #vim . It's a shame that we don't have good IDEs.

    I haven't tried Kate but isn't that more an editor than a full-fledged IDE?

  33. @argv_minus_one @shye

    I agree. I tried #lapce but I've eventually given up and now I just use #vim . It's a shame that we don't have good IDEs.

    I haven't tried Kate but isn't that more an editor than a full-fledged IDE?

  34. @argv_minus_one @shye

    I agree. I tried #lapce but I've eventually given up and now I just use #vim . It's a shame that we don't have good IDEs.

    I haven't tried Kate but isn't that more an editor than a full-fledged IDE?

  35. @argv_minus_one @shye

    I agree. I tried #lapce but I've eventually given up and now I just use #vim . It's a shame that we don't have good IDEs.

    I haven't tried Kate but isn't that more an editor than a full-fledged IDE?