Live data from Hacker News

Lapce – Fast open-source code editor

lapce.dev

71–80 of 231 posts

Re: Lapce – Fast open-source code editor

#71
post #65

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…

Off Topic: https://www.lapce.dev has a certificate issue. Also, the editor does not seem to run on Windows 7 ("createpseudoconsole could not be located" in KERNEL32.dll)

> Windows 7

is EOL and should be treated as such.

Re: Lapce – Fast open-source code editor

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

This is a valid point. File explorer is not something that is used very frequently so moving it to the right makes sense. > I moved it to the right ever since. What text editor are you using?

I'm using vs code which is quite flexible

Re: Lapce – Fast open-source code editor

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

Why is moving the entire text a problem? It needs to be redrawn, but that's not expensive - it's like moving an entire window. If for some reason you needed to resize the left side very often, or it would even resize automatically, I would understand the concern.

It's not about computation, I like the text to stay still. When I was aware of this it started bothering me, so I've changed it to the right ever since. Of course this is a very small and picky detail.

Re: Lapce – Fast open-source code editor

#74
post #65

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…

Off Topic: https://www.lapce.dev has a certificate issue. Also, the editor does not seem to run on Windows 7 ("createpseudoconsole could not be located" in KERNEL32.dll)

> Also, the editor does not seem to run on Windows 7 ("createpseudoconsole could not be located" in KERNEL32.dll)

Windows 7 EOL was 2 years ago though. (I know it's the last version of Windows that isn't an add-bloated spyware but still)

https://www.microsoft.com/en-US/windows/windows-7-end-of-lif...

Re: Lapce – Fast open-source code editor

#76
post #15

Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."

At least they went with "lighting-fast" instead of "blazing-fast"

“Lightning fast” is no less meaningless in practice than “blazing fast”. Both get used extensively by projects in such languages as JavaScript and Rust, on projects of similar scope that nonetheless have at least an order or two of magnitude’s performance difference.

Re: Lapce – Fast open-source code editor

#77
> You can connect to a remote machine seamlessly, with a "local" experience, benefiting from a identical environment with your production server, or utilizing the full performance of the remote machine.

What does this mean? Is it like Emacs' TRAMP[1]?

[1] https://www.gnu.org/software/tramp/

Re: Lapce – Fast open-source code editor

#78
This is one of the cases where not having null pointers in Rust really doesn't seem to help:

  % touch test
  
  % lapce test
  thread 'main' panicked at 'Error in Surface::configure: parent device is lost', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.12.0/src/backend/direct.rs:214:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

  % RUST_BACKTRACE=full lapce test
  thread 'main' panicked at 'Error in Surface::configure: parent device is lost', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.12.0/src/backend/direct.rs:214:9
  stack backtrace:
   0:     0x56474aaac84c - 
   1:     0x56474aad958c - 
   2:     0x56474aaa38f8 - 
   3:     0x56474aaaeea7 - 
   4:     0x56474aaaeb6f - 
   5:     0x56474aaaf60a - 
   6:     0x56474aaaf2f7 - 
   7:     0x56474aaaccf4 - 
   8:     0x56474aaaeff9 - 
   9:     0x5647494db8e3 - 
  10:     0x56474a7d8499 - 
  11:     0x56474a7d8f62 - 
  12:     0x56474a6b7345 - 
  13:     0x56474984e455 - 
  14:     0x564749657184 - 
  15:     0x56474953e4a5 - 
  16:     0x5647494ee8b6 - 
  17:     0x5647494dc243 - 
  18:     0x5647494dc2b9 - 
  19:     0x56474aaabf31 - 
  20:     0x5647494dc282 - 
  21:     0x7f084a6d3310 - __libc_start_call_main
  22:     0x7f084a6d33c1 - __libc_start_main@GLIBC_2.2.5
  23:     0x5647494dc165 - 
  24:                0x0 - 
Arch Linux, lapce 0.0.10, Rust 1.61.0-nightly, Sway/Wayland.

Re: Lapce – Fast open-source code editor

#79

> You can connect to a remote machine seamlessly, with a "local" experience, benefiting from a identical environment with your production server, or utilizing the full performance of the remote machine. What does this mean? Is it like Emacs' TRAMP[1]? [1] https://www.gnu.org/software/tramp/

It's similar to VSCode's remote development https://code.visualstudio.com/docs/remote/remote-overview

Or trying to be.

Post reply on HN