Live data from Hacker News

Tmux and Vim – better together

blog.bugsnag.com

141–150 of 297 posts

Re: Tmux and Vim – better together

#141
post #125

Earlier quoted context omitted.

My point is that after the initial investment in the setup, it takes almost no time to maintain them. In my particular case, I invested about 2 weeks tweaking settings here and there until I felt comfortable with it. After that initial setup, it just gets out of your way.

I disagree. Plugins breaking or interfering with other plugins is a regular thing.

I guess I must be doing something terribly wrong, because I can't relate to that at all.

Re: Tmux and Vim – better together

#143
post #54

Disappointed in Bugsnag for covering such trodden trails for a HN front page grab. Content marketing should have something to do with your business. There are hundreds of blog posts describing this exact setup.

Not once does the article mention Bugsnag or try to market their product. Who is to stop an enthusiastic engineer from sharing a workflow they find useful. The article has great content and powerful visuals to help convey their point. I'm happy to see companies not try to influence authors to plug their product in their blog posts.

Then it goes on their personal blog.

Re: Tmux and Vim – better together

#144
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…

Have you considered splitting up your vim config into multiple files, particularly for the conditional stuff? It doesn't cut down on the size of configurations as a whole but it does make it a bit easier to approach. I was in a similar situation. I had a lot of junk in my config files from when I started learning vim seriously, a lot of which I never really used. I've recently started to rebuild them to try and simpl…

Thanks. And I think SpaceVim is good for beginners.

Re: Tmux and Vim – better together

#145
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…

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 for VS Code is great, but do you let it take over Ctrl? Do you get Ctrl-R for redo, and sacrifice other VS Code usages of Ctrl for example? The vim plugin is also pretty buggy here and there and no matter what, I always find a vim plugin is missing some vim feature I depend on.

It's frustrating in a first world sense. It's hard to have your cake and eat it too with vim.

Re: Tmux and Vim – better together

#148

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.

The whole point of Kak is that it's a different editing paradigm, still modal and "text editing language" based, but in subject verb order rather than verb subject order. The idea is to give you more confidence as you type your commands by visually showing what they'll be applied to, instead of having to wait to see the result if you screw up.

If you're not interested in kak because of that paradigm change why are you interested in it at all?

Re: Tmux and Vim – better together

#149

Earlier quoted context omitted.

> I disagree. The default settings of Visual studio work perfectly fine for me. That's lucky for you, but unfortunately, it's not the case for me at all. > As an added advantage, I can use other developers in my companies workstations to show them something quickly if I need I might be using other peoples computers 10 hours a year, but I'm using my own maybe as much as 2200 hours a year. It doesn't seem logical to ta…

Have you actually tried to get YouCompleteMe[1] to work for C/C++ autocomplete? It's a huge PIA. Autocomplete just works in VSCode and many other IDEs once you point them at the right directory. https://github.com/Valloric/YouCompleteMe

I'm a front end web dev who decided to learn C (the other week actually). Took about 5 minutes to download and install YouCompleteMe.. What problems did you have?

The one problem I had was that I had to use the system version of clang as I'm using Arch.

Re: Tmux and Vim – better together

#150

Earlier quoted context omitted.

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.

Having switched to Kak recently, I've found this painful since I sometimes SSH into machines with only vi installed and so have to switch back and forth between kak and vi; it's a real headache...and a real shame since kak's selection method is much nicer IMO

If I can SSH to a remote host I can use Emacs TRAMP mode to edit files or I can mount the remote machine file system with SSHFS and change the file locally.

I will never be forced to use vi! ^__^

Post reply on HN