Live data from Hacker News

Porn, Zen, and .vimrc

karolis.koncevicius.lt

111–120 of 131 posts

Re: Porn, Zen, and .vimrc

#111

Earlier quoted context omitted.

Mouse takes far longer than a second for a selection. Switching between keyboard and mouse already takes longer than typing the usual vim-commands for a simple action. And casual keyboard-commands just don't scale well. Moving cursor x chars means you must type the movement-key x times. With vi you just type the number x and the movement, and usually save big time. Aditionally, vi has more knowledge about textual obj…

I have exclusively used vim keys for years now, but even after that time I find some of this just doesn’t ring true. Anything in vi that involves counting some number is usually faster with normal keys or the mouse. For example moving down 20 lines is way faster with the mouse, you just click. With vi you have to count the lines in your head - better hope you don’t lose count half way because two lines blur together.…

> For example moving down 20 lines is way faster with the mouse, you just click.

Correction - you must move your mouse hand from the keyboard, move the mouse to the desired location, _then_ click.

Ergonomic concern often goes side-by-side with editors like vim.

I'm also not convinced that comparing the simple editor things is demonstrating the value of vim much. It's how easy vim handles the _not_ simple things, and also how easy it is to motion the often unique or rarely used edits, combined with drop-of-the hat programmability, that makes vim a good choice.

Re: Porn, Zen, and .vimrc

#112

Earlier quoted context omitted.

Mouse takes far longer than a second for a selection. Switching between keyboard and mouse already takes longer than typing the usual vim-commands for a simple action. And casual keyboard-commands just don't scale well. Moving cursor x chars means you must type the movement-key x times. With vi you just type the number x and the movement, and usually save big time. Aditionally, vi has more knowledge about textual obj…

I have exclusively used vim keys for years now, but even after that time I find some of this just doesn’t ring true. Anything in vi that involves counting some number is usually faster with normal keys or the mouse. For example moving down 20 lines is way faster with the mouse, you just click. With vi you have to count the lines in your head - better hope you don’t lose count half way because two lines blur together.…

You don't have to count. I typically make a rough estimation and go from there. For me that still is faster than putting hand on mouse, searching current cursor position, aim, click, and back to proper keyboard position. Of course ymmv

Re: Porn, Zen, and .vimrc

#113
Ever since I started using vim exclusively for development a couple of years ago, I deliberately decided not to use plugins nor to edit the defaults unless strictly necessary. Nowadays, my .vimrc is just a few lines, all regarding indentation.

It had worked for me so far and I never really felt any less productive than when I used IDEs or VS Code.

Re: Porn, Zen, and .vimrc

#114

Earlier quoted context omitted.

Mouse takes far longer than a second for a selection. Switching between keyboard and mouse already takes longer than typing the usual vim-commands for a simple action. And casual keyboard-commands just don't scale well. Moving cursor x chars means you must type the movement-key x times. With vi you just type the number x and the movement, and usually save big time. Aditionally, vi has more knowledge about textual obj…

I have exclusively used vim keys for years now, but even after that time I find some of this just doesn’t ring true. Anything in vi that involves counting some number is usually faster with normal keys or the mouse. For example moving down 20 lines is way faster with the mouse, you just click. With vi you have to count the lines in your head - better hope you don’t lose count half way because two lines blur together.…

Relative number lines solved the counting issue for me in most scenarios.

Re: Porn, Zen, and .vimrc

#115

Earlier quoted context omitted.

I have exclusively used vim keys for years now, but even after that time I find some of this just doesn’t ring true. Anything in vi that involves counting some number is usually faster with normal keys or the mouse. For example moving down 20 lines is way faster with the mouse, you just click. With vi you have to count the lines in your head - better hope you don’t lose count half way because two lines blur together.…

> For example moving down 20 lines is way faster with the mouse, you just click. Correction - you must move your mouse hand from the keyboard, move the mouse to the desired location, _then_ click. Ergonomic concern often goes side-by-side with editors like vim. I'm also not convinced that comparing the simple editor things is demonstrating the value of vim much. It's how easy vim handles the _not_ simple things, and…

Yes, it's certainly more ergonomic and comfortable. Still, I find the mouse pretty fast overall. But I'm pretty good at aiming at things with it after playing FPS games for a while.

>how easy vim handles the _not_ simple things

Agreed, despite any minor differences in movement speed, even '.' by itself is useful enough to never switch back.

Re: Porn, Zen, and .vimrc

#116
post #41

Earlier quoted context omitted.

i just keep a repo of public configs and curl them to any new machines and have a simple script to symlink the various configs to their expected locations

There's a standard tool for that: https://www.gnu.org/software/stow/

thank you, i was not aware and I will investigate it

Re: Porn, Zen, and .vimrc

#117
post #45
post #23

Earlier quoted context omitted.

Same. My normal set up is having a shell window with 4 tabs: 1. Text editing 2. Command Line 3. Program logs 4. Code console Flipping through them is a breeze, and I never have to leave Terminal. The displays are always simple, straight forward, and focused. No distractions. I'm able to just get in the zone with the code and forget anything else exists.

If you can move your tabs to tmux, you will greatly improve your situation. It's easy. Then you can, for instance, make your development machine a dedicated cloud server, like digital Ocean etc. This is what I do and it's very nice to be able to use any hardware I want, including cheap underpowered stuff, since it's just a window to my real machine.

I use tmux to group shells by context, setting a shell variable that various things in my bashrc respond to. The biggest win is a separate bash history per context, so my commands related to project A don't get mixed up with my commands related to project B or my sysadmin commands or ...

It's very nice!

Re: Porn, Zen, and .vimrc

#118
post #19

Here is my only remapping: map Q Whenever I use vim without my config I wind up hitting Q and entering ex mode and wishing I had my config. I've used vim on and off for at least 6 years and have never installed a plugin. Vim is great for quick edits, arranging text in temporary files (control x + control e in the terminal, quit without saving), moving chunks of code around, running macros. Its also great to use the k…

Have you tried using Doom Emacs? The process of installing everything you need for a particular language only involves uncommenting a line on your config and running "doom sync". It's really good.

I haven't tried Doom/Spacemacs yet. The same thing that keeps me from installing vim plugins probably keeps me from installing large "frameworks" for emacs. Doom does seem relatively lightweight and I'll give it a try at some point this weekend.

Re: Porn, Zen, and .vimrc

#119
post #16

If your .vimrc is minimal, you will have a pretty good time using systems that implement "vim like" text editing. Take Overleaf for example, no vimrc is available, but I'm quite happy with what I got, and sometimes I even forget I'm in the browser.

> If your .vimrc is minimal, you will have a pretty good time using systems that implement "vim like" text editing.

This has not been my experience, fwiw. Everywhere implements "most" of what I do, but I still wind up hitting something in the unimplemented portions pretty frequently.

Post reply on HN