Live data from Hacker News

Amp – A complete text editor for the terminal

amp.rs

41–50 of 174 posts

Re: Amp – A complete text editor for the terminal

#41

Earlier quoted context omitted.

I do wish there were more modal, terminal-based text editors that weren't so similar to Vim. Kakoune is Vim-like, and now this.

I on the other hand would like to see other non-modal editors. Vim is already the best and most customizable modal editor, but does anyone know a good non-modal editor beyond basic nano?

You can try micro: https://micro-editor.github.io/

Re: Amp – A complete text editor for the terminal

#42

Earlier quoted context omitted.

I do wish there were more modal, terminal-based text editors that weren't so similar to Vim. Kakoune is Vim-like, and now this.

I on the other hand would like to see other non-modal editors. Vim is already the best and most customizable modal editor, but does anyone know a good non-modal editor beyond basic nano?

> Vim is already the best and most customizable modal editor

Weird statement. "Best" is up to debate, but "most customizable" is definitely Emacs.

I cannot really imagine a really good non-modal programmer's editor. Surely it should behave differently when editing Python compared to editing HTML?

Re: Amp – A complete text editor for the terminal

#43
post #35

Earlier quoted context omitted.

I have been using Vim for several years now and I still struggle with basic-level movement commands. Like, I never remember if f-h will move me to |hello or to h|ello. If those are working for you, that is great, but I appreciate some alternatives there. The usual Vim approaches ("do vimtutor!" or "practice one new command a week!") are not working for me.

> I never remember if f-h will move me to |hello or to h|ello. …Isn't the answer "neither"? If the cursor is somewhere before that `h`, then doing `fh` will put the cursor on that `h`. If you want to enter insert mode before that `h`, you would press `i`, or `a` to enter insert mode after the `h`.

You are probably right. Which is my point. Vim movement commands remain unintuitive to me, even after using the thing for years.

Re: Amp – A complete text editor for the terminal

#44

Earlier quoted context omitted.

I do wish there were more modal, terminal-based text editors that weren't so similar to Vim. Kakoune is Vim-like, and now this.

I on the other hand would like to see other non-modal editors. Vim is already the best and most customizable modal editor, but does anyone know a good non-modal editor beyond basic nano?

[deleted]

Re: Amp – A complete text editor for the terminal

#45
post #42

Earlier quoted context omitted.

I on the other hand would like to see other non-modal editors. Vim is already the best and most customizable modal editor, but does anyone know a good non-modal editor beyond basic nano?

> Vim is already the best and most customizable modal editor Weird statement. "Best" is up to debate, but "most customizable" is definitely Emacs. I cannot really imagine a really good non-modal programmer's editor. Surely it should behave differently when editing Python compared to editing HTML?

You're using the emacs definition of major modes. "Modal editor" has a different meaning. Vim has three modes [1]. Emacs is not considered a modal editor, but some of its features are similar to Vim's last-line mode.

[1] https://alvinalexander.com/linux/vim-vi-mode-editor-command-...

Re: Amp – A complete text editor for the terminal

#46
post #6

>A modal, keyboard-driven interface inspired by Vim that makes navigating and editing text fast. But what does it do different than vim? Having competition is good, but I don't see any "that's why you should use amp and not vim"-reason. Where is it?

I do wish there were more modal, terminal-based text editors that weren't so similar to Vim. Kakoune is Vim-like, and now this.

Do you know about micro? https://github.com/zyedidia/micro

Re: Amp – A complete text editor for the terminal

#47
post #6

>A modal, keyboard-driven interface inspired by Vim that makes navigating and editing text fast. But what does it do different than vim? Having competition is good, but I don't see any "that's why you should use amp and not vim"-reason. Where is it?

I thought it was pretty clear actually: it works out of the box with no configuration (batteries included).

> Amp is complete from the start.

As a long time vim user, the more advanced you get the more customized your vimrc and plugins become and you aren’t able to just walk up to vim somewhere else and be efficient (pairing with another vim user becomes impossible). Shared defaults are a powerful thing! Convention over configuration.

Imagine we even both like using the nerd tree plugin but can’t agree what the leader key should be mapped to in order to activate it: a common problem.

That’s why you see the most advanced vim users go back to a minimal vimrc which admittedly makes it a less useful editor.

I think we can all agree vims defaults are crap and without plugins it doesn’t have all of the features of a modern editor.

Re: Amp – A complete text editor for the terminal

#48
post #18
post #6

>A modal, keyboard-driven interface inspired by Vim that makes navigating and editing text fast. But what does it do different than vim? Having competition is good, but I don't see any "that's why you should use amp and not vim"-reason. Where is it?

I think one of the main reasons it exists is that it's written in Rust. One clue is that the TLD is .rs, plus there's been a lot of "a written in Rust" lately. Which is fine; it's just an observation. I myself am going to be getting into Rust soon, hopefully.

> there's been a lot of "a written in Rust" lately

It's the new Go.

Re: Amp – A complete text editor for the terminal

#50
post #18

Earlier quoted context omitted.

I think one of the main reasons it exists is that it's written in Rust. One clue is that the TLD is .rs, plus there's been a lot of "a written in Rust" lately. Which is fine; it's just an observation. I myself am going to be getting into Rust soon, hopefully.

being written in rust might make it more appealing to develop, but it doesn't give any benefit to the user and I can't see it being a reason for someone to use this over vim

Rust programs tend to be more stable, more efficient, and more highly parallelized than equivalents written in other languages by developers of the same quality.
Post reply on HN