Live data from Hacker News

Tmux and Vim – better together

blog.bugsnag.com

241–250 of 297 posts

Re: Tmux and Vim – better together

#241
post #30

All this looks really great, however I think I just can't deal with the effort of maintaining these complex editor configurations anymore. I've been a multi-decade Vim user, until I switched to VSCode last year. It made me realize how much better the user experience can be for an editor. I had all kinds of complex vim configurations and plugins with special cases for linux vs. mac, server vs. desktop, GUI vs. termina…

In my humble opinion, emacs is much closer by default.

There are a couple of things which I think could make the default config simpler:

- Enable global-subword-mode by default.

- Enable delete-selection-mode by default.

With that, and maybe adding multiple-cursors to the default distribution (with a little bit more refinement) and I could use it out of the box. I would still probably set up colours, and I like my fonts really tiny, but those would be a matter of customization.

One other thing maybe is making M-x customize more discoverable. I think for a lot of users (including myself sometimes) it is sometimes simpler to search for an option by what you think it should be called, and select one of the known good values than it is to write the elisp expression for it.

Re: Tmux and Vim – better together

#242
post #204

Earlier quoted context omitted.

Have you considered emacs + evil?

I think emacs falls in the same camp as vim in this regard. Setting up emacs is just as painful as setting up vim.

If you like searchable multiple-choice configuration, there's always customize.

M-x customize

Re: Tmux and Vim – better together

#243
post #234
post #94

Earlier quoted context omitted.

I know what neovim is. I was talking about answering to all vim problems with "did you try neovim?"

Who really says that though? As a regular lurker on the vim/neovim subreddits and mailing lists, I've never seen anyone try to fix someone's issue in vim by telling them to get neovim (literally never). Because, in the end, they're going to end up with the same issue. You already know what neovim is....so why would switching solve anything? Say they don't know how to use tabs, omnicompletion...why would neovim be any…

As I said before I have no problem with neovim. Yet, I'm reading HN from about 3 years and I see more and more posts like quoted above. Even in this thread was one or two - dunno where they are now.

My point here is only to learn first and extend further. Not throw yourself into high water with SpaceVim and than say how much vim or neovim is bloated.

Re: Tmux and Vim – better together

#244
post #204

Earlier quoted context omitted.

I think emacs falls in the same camp as vim in this regard. Setting up emacs is just as painful as setting up vim.

If you like searchable multiple-choice configuration, there's always customize. M-x customize

That doesn't help emacs noobs at all. Half the Emacs term still used today 40 years after being coined don't make any sense. Wait - this is not the Window, but the... Frame? What?

Re: Tmux and Vim – better together

#245
post #43

Earlier quoted context omitted.

Weird. I built my .rc files like 10 years ago, and only edit them about twice a year to add a plugin or modify a keybinding. Not a pain to maintain at all.

How do you store them? Just backup into a dotfiles repo or what? I've been looking into dotfiles + gnu stow.

I was searching for this earlier, I came across a HN post which someone from Atlassian write up really nicely: https://developer.atlassian.com/blog/2016/02/best-way-to-sto...

No extra tools (just git), no symlinks.

Re: Tmux and Vim – better together

#246

Earlier quoted context omitted.

No matter how much you tweak it, you will never even start to scratch an experience like Visual Studio. Vim is a fundamentally weaker platform.

Meh. I've used both and disagree. Visual Studio is a better IDE. Vim is a better text editor.

Has anyone tried VsVim [1]? It is the best vim experience I've had in any other editor. And I've already tried Sublime's, VSCode's, and others. Most of the vim functions I use are there, but it's been a while since the last time I used VisualStudio, so I don't recall the ones with problem. You can even plug in relative line numbers [2].

[1]: https://marketplace.visualstudio.com/items?itemName=JaredPar...

[2]: https://marketplace.visualstudio.com/items?itemName=ZoltanKl...

Re: Tmux and Vim – better together

#247
post #145

Earlier quoted context omitted.

I've always felt vim is an excellent editing experience but a lousy project management (ie "IDE") experience. I've also grown tired of the song and dance of setting up vim config and plugins, getting excited when I finally get a decent autocomplete working without stopping to consider VS Code has great autocomplete out of the box. The problem is vim editing never quite mixes well with other editors. The vim plugin fo…

The real solution to this problem is for IDEs to support an editing frontend interface and then editors to be split into frontend and backend so that really you could use them in the context of the IDE. The obvious example would be using the neo-vim frontend to interact with VSCode, Eclipse, IntelliJ, etc. What I want most is a Neo-Vim frontend to org-mode in Emacs, because it would be hilarious and because while Spa…

that's exactly how limetext approached it. one back end, multiple frontends. I think that project is dead-ish though

Re: Tmux and Vim – better together

#248

Earlier quoted context omitted.

Meh. I've used both and disagree. Visual Studio is a better IDE. Vim is a better text editor.

Has anyone tried VsVim [1]? It is the best vim experience I've had in any other editor. And I've already tried Sublime's, VSCode's, and others. Most of the vim functions I use are there, but it's been a while since the last time I used VisualStudio, so I don't recall the ones with problem. You can even plug in relative line numbers [2]. [1]: https://marketplace.visualstudio.com/items?itemName=JaredPar... [2]: https:/…

The biggest issue is you're still tied to the real crappy windowing of VS, not the much better ones of vim or tmux.

VsVim is getting really good though, it even reads your vimrc these days.

Re: Tmux and Vim – better together

#249
post #145

Earlier quoted context omitted.

I've always felt vim is an excellent editing experience but a lousy project management (ie "IDE") experience. I've also grown tired of the song and dance of setting up vim config and plugins, getting excited when I finally get a decent autocomplete working without stopping to consider VS Code has great autocomplete out of the box. The problem is vim editing never quite mixes well with other editors. The vim plugin fo…

The real solution to this problem is for IDEs to support an editing frontend interface and then editors to be split into frontend and backend so that really you could use them in the context of the IDE. The obvious example would be using the neo-vim frontend to interact with VSCode, Eclipse, IntelliJ, etc. What I want most is a Neo-Vim frontend to org-mode in Emacs, because it would be hilarious and because while Spa…

This is basically what the language server protocol (https://github.com/Microsoft/language-server-protocol) is doing, just in reverse.

Re: Tmux and Vim – better together

#250

Earlier quoted context omitted.

I've taken a month or two off from plugging Kakoune on HN because I was worried about becoming tiresome, but I can't resist mentioning it in this context. I used vim for 20 years, although I always preferred to stick with the default configuration. I switched to kak a couple of months ago, and I couldn't be happier. It's got great tmux integration, it automatically runs a server so you can connect multiple clients to…

I'd like to try Kak, a friend recently told me about it. But, I'm concerned about needing to relearn common commands. For instance, I believe that they mentioned that in Kak the Vim equivalent to `dw` is `wd`. I've got decades of use with Vi(m) under my belt, as well, and I am not too thrilled at the idea of having to unlearn/relearn common commands.

It's painful, but on the plus side it's way outside of the uncanny valley, it's not like a vim clone. In practice I found that this meant going back to vim (kak didn't work for me) easy.
Post reply on HN