archseer

Joined 13 years ago

Karma

664

Submissions

105

Member since

Sep 28

my public key: https://keybase.io/speed; my proof: https://keybase.io/speed/sigs/TcbsclNHt4mvME-VM0Q_qIKPifMnC0AfDsZC4sECs1c

View on Hacker News

Recent submissions

Comment · 2 months ago

Comment · 1 year ago

https://github.com/helix-editor/helix/pull/12527

Comment · 2 years ago

Author here. I listen to feedback, but it's hard to incorporate every possible requested feature without the codebase becoming an unmaintainable mess.

We're a small team with limited time and I've always emphasized that helix is just one version of a tool and it's perfectly fine if there's a better alternative for some users. Someone with a fully customized neovim setup is probably going to have a better time just using their existing setup rather than getting helix to work the same way.

Code editors in particular are very subjective and helix started as a project to solve my workflow. But users don't always respond well to having feature requests rejected because they don't align with our goals. Plugins should eventually help fit those needs.

Comment · 2 years ago

Yet.

Comment · 3 years ago

Splits are provided, tabs and terminals aren't. Diff mode is work in progress.

Comment · 3 years ago

https://www.mpscholten.de/docker/2016/01/27/you-are-most-lik...

Comment · 3 years ago

I think you're mistaken. See https://www.youtube.com/watch?v=3UAaky12REM for example.

Comment · 3 years ago

Both ZSTD and LZ4 were built by the same author. They have slightly different target goals: https://news.ycombinator.com/item?id=23211804

Comment · 3 years ago

There's also a dramatic video rendition by the author: https://youtube.com/watch?v=_lLm3a33WsE

Comment · 3 years ago

Thanks for the kind words! Fixed the link :)

Comment · 3 years ago

There's this config you might like: https://github.com/LGUG2Z/helix-vim

We can't invert the bindings though (wd -> dw) because that would require a big internal change to add operator pending mode:

When you press `d` in vim, that enters the operator pending mode, where it will wait for an object to be specified, in this case `w` and then delete it.

In a selection first model, `d` is very simple: it just always deletes the selection. So you select a word, then delete.

Comment · 3 years ago

A tree-sitter grammar is slightly more complex but it has a bunch of benefits! Syntax highlighting is more correct, faster and a bunch of smart features like indentation and folding, bracket matching can be built on top of it.

Comment · 3 years ago

If the bindings were the same, then what's the point? We're not a "vim ported to rust", instead we got our own take on things. (from the vision doc: "Don't try to be everything for everyone. There are many great editors out there to choose from. Let's make Helix one of those great options, with its own take on things.")

> helix wants to get much wider adoption

I've stated this before: I just want to make a good editor that I like using daily. There's a growing community of users with similar preferences that are very happy with it, but I'm not aiming to corner the market -- this isn't a startup. Much in the same way as vim isn't trying to become more like VSCode to increase it's market share.

That said, thanks for giving it a try! For keybinds, we do have a couple of guides:

- `hx --tutor` is the equivalent to vimtutor

- https://github.com/helix-editor/helix/wiki/Migrating-from-Vi...

- Our Matrix chat is always happy to help with questions :)

Comment · 3 years ago

1) there's a pull request that fixes this but needs a bit of polish (https://github.com/helix-editor/helix/pull/1819)

3) There's also a discussion for this, we hoped to include it in this release but it's instead going to be in the next cycle (https://github.com/helix-editor/helix/pull/4439)