> Amp is inspired by Vim's modal approach to text editing
And I closed the page. Modal editing simply makes zero sense on a modern keyboard. It is awful.
Amp – A complete text editor for the terminal
31–40 of 174 posts
Re: Amp – A complete text editor for the terminal
#32Earlier 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.
It is indeed quite amazing how modal editing is usually defined by vi, which does so in very specific ways, when there are alternatives (like kakoune) which really show there's a whole spectrum of possible implementations of that idea. I wish there was a modal editor with the same scope as nano which would help introducing that concept to newcomers without aiming to maximize productivity / expressiveness.
Well, nano is modal. If you press CAPS LOCK you enter "uppercase mode" :)
Re: Amp – A complete text editor for the terminal
#33> Amp is inspired by Vim's modal approach to text editing And I closed the page. Modal editing simply makes zero sense on a modern keyboard. It is awful.
Have you used it extensively? Why on modern keyboards? I can't stand non-modal editors now. I find them extremely limiting.
Re: Amp – A complete text editor for the terminal
#34> Amp is inspired by Vim's modal approach to text editing And I closed the page. Modal editing simply makes zero sense on a modern keyboard. It is awful.
In what way is modal editing awful?
Modal editors are the only solution I've come across to what I see as the problem with modern keyboards and editors: the inability to do everything you want to do without moving your hands away from the home row. Intellij, eclipse, sublime text, every "modern" non-modal editor I've used expects me to move my hands to the arrow keys if I want to move the caret. This is a personal gripe for me as repeatedly moving my hand back and forth between the home row, the mouse and arrow keys triggers my RSI. At least a non-modified bash prompt lets me navigate using some archaic control key combinations (^a: beginning of line, ^e: end of line, ^f: forward one character, etc.)
Re: Amp – A complete text editor for the terminal
#35I honestly don't know why people would want to navigate code using jump-mode/easymotion. I've found it far more confusing than just searching for the word.
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.
Re: Amp – A complete text editor for the terminal
#36>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.
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?
Re: Amp – A complete text editor for the terminal
#37I honestly don't know why people would want to navigate code using jump-mode/easymotion. I've found it far more confusing than just searching for the word.
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`.
Re: Amp – A complete text editor for the terminal
#38Earlier 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.
I think it's a lot easier for someone to learn a new language, or learn the benefits of a new language, by recreating something which already exists.
I usually go for irc bots when trying to learn a new language. I already know the api and the thought process which makes it easier.
Re: Amp – A complete text editor for the terminal
#39>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.
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
Re: Amp – A complete text editor for the terminal
#40I think I'm too into vim to like this now. I miss more "advanced" gestures, like: daw, caw... Not being able to edit a word without positioning caret at the beginning feels limiting.