Live data from Hacker News

Lapce – Fast open-source code editor

lapce.dev

41–50 of 231 posts

Re: Lapce – Fast open-source code editor

#41
Author 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 submit a feature request or bug report in Github Issues or leave your feedback here.

Re: Lapce – Fast open-source code editor

#42
I tried to change the font by backspacing whatever the default was in the font family box in settings, but once I deleted the last character, the program crashed and would not open again.

Running with a trace gets:

    thread 'main' panicked at 'assertion failed: `(left == right)`
      left: `23`,
     right: `0`', /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/font-kit-0.10.1/src/loaders/freetype.rs:817:13
    stack backtrace:
       0: rust_begin_unwind
                 at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/std/src/panicking.rs:498:5
       1: core::panicking::panic_fmt
                 at /rustc/9d1b2106e23b1abd32fce1f17267604a5102f57a/library/core/src/panicking.rs:116:14
       2: core::panicking::assert_failed_inner
       3: core::panicking::assert_failed
       4: font_kit::loaders::freetype::Font::rasterize_glyph
       5: piet_wgpu::pipeline::Cache::get_glyph_pos
       6: piet_wgpu::text::WgpuText::get_glyph_pos
       7: piet_wgpu::text::WgpuTextLayout::rebuild
       8: ::build
       9: lapce_core::config::Config::editor_text_width
      10: >::layout
      11: druid::core::WidgetPod::layout
      12:  as druid::widget::widget::Widget>::layout
      13: druid::core::WidgetPod::layout
      14: >::layout
      15: druid::core::WidgetPod::layout
      16: >::layout
      17: druid::core::WidgetPod::layout
      18: >::layout
      19: druid::core::WidgetPod::layout
      20: >::layout
      21:  as druid::widget::widget::Widget>::layout
      22: druid::core::WidgetPod::layout
      23: >::layout
      24:  as druid::widget::widget::Widget>::layout
      25: druid::core::WidgetPod::layout
      26: druid::window::Window::layout
      27: druid::window::Window::do_paint
      28: druid::win_handler::AppState::paint_winit_window
      29: druid::app::AppLauncher::launch::{{closure}}
      30: winit::platform_impl::platform::x11::EventLoop::run_return::single_iteration
      31: winit::platform_impl::platform::x11::EventLoop::run
      32: winit::platform_impl::platform::EventLoop::run
      33: winit::event_loop::EventLoop::run
      34: lapce_core::app::lanuch
    note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Agree with other comments here that it's a bit too unusable at the moment, and unfortunately I wasn't even 30 seconds into my demo before this happened, so I can't really comment on the rest of the application.

Re: Lapce – Fast open-source code editor

#44
post #8

It looks really promising. I wonder why code editors have the file explorer on the left side by default, if you resize it you move the whole text (unless you write in a right-to-left language). A colleague made me aware of this a while ago and I cannot stop wondering. I moved it to the right ever since.

For the same reason almost all relevant ui-elements are left-aligned across operation systems and apps: because we are tuned to process things left-to-right and the mouse is more often on the left side than it is on the right, and it feels less intuitive to move it to the right end of the screen.

- window-operation buttons on macos (close, maximize ...)

- application-menus in gnome, macos etc (file, edit, view ...)

- heavy-used buttons in browser (page back, refresh ...)

Re: Lapce – Fast open-source code editor

#45
post #38
post #34

Earlier quoted context omitted.

I think that Visual Studio has it on the right hand side by default, but that's the only editor I can think of that does it.

It does not have it by default on the right, but you can move it yourself.

Visual Studio Code does not. But Visual Studio does.

Re: Lapce – Fast open-source code editor

#47
Just tossing an opinion out there. In the last 10 years my editor progression has been notepad++ -> sublime -> atom -> vscode -> pycharm. Virtually every pixel on Pycharm is dedicated to at least try to let me write better python code and ease development friction. Lapce may eventually be vscode++ but I'm no longer in the market for general purpose editors.

Re: Lapce – Fast open-source code editor

#49

Author 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…

Valiant effort and impressive personal project!

> 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.

Website claims "Native GUI" but this is not native GUI. I'd rather have basic UX before multi cursor or anything else nice to have but totally optional things. On Windows open dialog is broken, you can't select drives, you have to enter the drive letter manually, but in input field delete key is not working. That's as far as I got trying it out.

Post reply on HN