Vim has mouse support. You just need to turn it on in your .vimrc/init.vim with `set mouse=nv` (that specifically enables the mouse in normal and visual modes).
Why don’t we have good code editors?
31–40 of 74 posts
Re: Why don’t we have good code editors?
#32Does anyone know what "modal editing" is? I've read the article, and it's mentioned several times, but I've no idea what it actually means.
Basically, having two ways of interacting with the file: one mode lets you execute commands to edit the file, the other mode lets you type like in a typical GUI editor.
Re: Why don’t we have good code editors?
#33Does anyone know what "modal editing" is? I've read the article, and it's mentioned several times, but I've no idea what it actually means.
Basically, having two ways of interacting with the file: one mode lets you execute commands to edit the file, the other mode lets you type like in a typical GUI editor.
While editing a file in VSCode, I can press CTRL+P, which opens a small command box in which I can type to find a command with autocomplete - like a souped-up version of vim's "colon prompt" (not sure what it's called!) - does that count?
Re: Why don’t we have good code editors?
#34TL DR; The author wants a modal editor (like vim) that's also "modern"/graphical.
My view: this is largely a religious issue.
Editor design is like QWERTY keyboards (or beer): preferences are more dominated by your muscle memory and what you're used to, than any objective notion of "good" or "best".
Re: Why don’t we have good code editors?
#35>a terminal does not a pleasant user experience make Author doesn't establish this, just takes it as a given. I wonder what features terminal emulators/editor programs would lack that are afforded by GUIs? I consider the terminal text editing experience far more efficient
Usually? File handling. It's convenient on large projects to have a list of files in view next to the code.
Nerdtree for vim? Emacs out of the box ...
Wtf.
This stuff is decades old
Re: Why don’t we have good code editors?
#36> In all seriousness though, a terminal does not a pleasant user experience make. Yes, yes it does. At my fingertips I have access to every single tool and program without needing to clumsily navigate through folders or Finder, whatever it is. Moving my hand away from my keyboard to my mouse to check TS typings is biggest waste of time when I know how to get to any line in any file with less than 3 keystrokes. > The…
The mouse is not a "clumsy" input and there are plenty of situations in which the mouse allows more efficient usage than the keyboard like when navigating through 2D space. For example it is clearly more efficient to place your cursor at a certain arbitrary point in the document using the mouse than to navigate there using keyboard commands. I'm also not really convinced about the "hands on the keyboard" argument...…
> Are they on the keyboard right now?
Of course they're not on the keyboard while I'm exclusively reading. But while I'm in vim, my hands certainly are on the keyboard nearly at all times, resting on the home row.
Re: Why don’t we have good code editors?
#37Vim has mouse support. You just need to turn it on in your .vimrc/init.vim with `set mouse=nv` (that specifically enables the mouse in normal and visual modes).
Does that work in terminal? Afaik I had the only working in gvim.
Re: Why don’t we have good code editors?
#38Earlier quoted context omitted.
Basically, having two ways of interacting with the file: one mode lets you execute commands to edit the file, the other mode lets you type like in a typical GUI editor.
While editing a file in VSCode, I can press CTRL+P, which opens a small command box in which I can type to find a command with autocomplete - like a souped-up version of vim's "colon prompt" (not sure what it's called!) - does that count?
No
Re: Why don’t we have good code editors?
#39Earlier quoted context omitted.
While editing a file in VSCode, I can press CTRL+P, which opens a small command box in which I can type to find a command with autocomplete - like a souped-up version of vim's "colon prompt" (not sure what it's called!) - does that count?
No
OK... what is the difference, as you see it?
Re: Why don’t we have good code editors?
#40Summary: I would like a vscode that better integrates modal editing. Verbosity is an existential threat.
Well, it would not be a proper rant if it wasn't as verbose.