Earlier quoted context omitted.
And there is a stack trace. Worlds apart.
Well stack traces are just a gdb session away, no changes to code/binary needed. No?
But most crashes can be turned into an exploit.
Lapce – Fast open-source code editor
151–160 of 231 posts
Re: Lapce – Fast open-source code editor
#152I was waiting for the "written in Rust", was not disappointed. :)
Great project by the way.
Re: Lapce – Fast open-source code editor
#153Author here. Thanks for all the feedback. I'm aware that Lapce lacks lots of basic stuff. It's a personal project so the initial set of features and key bindings are tight to my personal preferences. I'm currently working on the missing pieces, like multi cursor support(in master but not released yet), mouse support, sane default key bindings(probably I'll stick to an existing editor), basic UX etc. Feel free to subm…
> It's a personal project so the initial set of features and key bindings are tight to my personal preferences.
As it should be. Well done.
Re: Lapce – Fast open-source code editor
#154Re: Lapce – Fast open-source code editor
#155Re: Lapce – Fast open-source code editor
#156Re: Lapce – Fast open-source code editor
#157Earlier quoted context omitted.
Are there any plans to release the app as a Flatpak, they are a great way to package your application cross-distro with a central way of updating (such as Flathub).
No relation to this project. Just wanted to chime in to say that KDE's Kate editor pulled its Flatpak because the sandboxing makes much of the system integration (terminal, git, language servers) hard or impossible. A Flatpak may have to ship with an independent copy of a lot of basic developer tools, and even then I don't know whether I want two different versions of git access the same local repository with a chanc…
I'm having the same issue with the Visual Studio Code (Flatpak). I want to use the compilers, interpreters and tools from the host, not whatever it's provided by the Flatpak or the runtimes from flathub/gnome, if it's provided at all.
Re: Lapce – Fast open-source code editor
#158No Electron? That is already one good thing ;) Why does Rust folks seem to encapsulate and separate their stuff more and more? Own build-tools and infrastructure are one thing. Am I right that Druid is not an very own Toolkit but a layer like WxWidgets?
No, Druid does not delegate to system widgets as far as I know. In that sense, it's slightly wrong that it's called "native", as it's not native UI, but it's compiled "native code" (= not Electron or a wrapper to some other framework that's written in some other language).
Here are the goals of Druid; be sure to read about the non-goals too: https://github.com/linebender/druid#Goals
Re: Lapce – Fast open-source code editor
#159No Electron? That is already one good thing ;) Why does Rust folks seem to encapsulate and separate their stuff more and more? Own build-tools and infrastructure are one thing. Am I right that Druid is not an very own Toolkit but a layer like WxWidgets?
No, Druid does not delegate to system widgets as far as I know. In that sense, it's slightly wrong that it's called "native", as it's not native UI, but it's compiled "native code" (= not Electron or a wrapper to some other framework that's written in some other language). Here are the goals of Druid; be sure to read about the non-goals too: https://github.com/linebender/druid#Goals
Thank you. I was misguided by the dependency upon Gtk!
For Gtk there is anyway gtk-rs[1] available.
Re: Lapce – Fast open-source code editor
#160Is the name meant to be read as "lapse"? 1. a brief or temporary failure of concentration, memory, or judgement. synonyms: failure, failing, slip, error, mistake, blunder, fault, omission, oversight, negligence, dereliction, slip-up, fail
No - it'd an acronym for Light And Powerful Code Editor