Live data from Hacker News

Tmux and Vim – better together

blog.bugsnag.com

201–210 of 297 posts

Re: Tmux and Vim – better together

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

If you'd like a consistently high-quality default user experience for emacs, check out Spacemacs![0] Especially since you're a Vim user. It's a distribution built around evil-mode with fantastic defaults.

[0] http://spacemacs.org/

Re: Tmux and Vim – better together

#203

Earlier quoted context omitted.

I think that's a little harsh. What a lot of people (including myself) dislike about IDEs is that you lose a lot of tool composability, and to some extent you have to play by the IDE's rules. With a Vim + CLI setup, you get to define the optimal flow, but the tradeoff is maintainability. For many, though, once you get your environment set up, it feels amazingly natural, more than an IDE could provide. It's more a mat…

Here is the key value provided by an IDE: * Autocomplete. This deserves way more recognition than it gets. Having function signatures, documentation, overloads, types, available IN-LINE while you type saves so much work from programming and is essential to delivering correct code. If you want to be an effective programmer, this is a fundamental tool. * Debugger. Easy breakpoints, conditional breakpoints, built-in pro…

re. Autocomplete - have a look at Vanilla vim's help files on Completion. Not the greatest, but still quite good and easily extensible (even without compiling in YouCompleteMe).

http://vimdoc.sourceforge.net/htmldoc/usr_24.html#24.3

And a debugger doesn't have to be built into an editor to be functional. PDB, GDB, PRY, your browser's built-in debugger... all are quite useful without being built-in to your code editor. As a bonus, all but the last can be easily accessed from your terminal (which, hey, you have multiple terminal windows readily available in tmux!).

Sorry, troll fed. My apologies.

Re: Tmux and Vim – better together

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

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.

Re: Tmux and Vim – better together

#205
post #8
post #5

Earlier quoted context omitted.

I used it for a while but then I realized that ConEmu also supports split panes, and then i can just scroll/select the buffers by mouse instead of ctrl+b, [. ConEmu really is an amazing piece of work. Quirky to configure (but hey, so it tmux), but truly amazing still :-)

If you like ConEmu try out cmdr http://cmder.net > Cmder is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.

If you've already extensively customized ConEmu, Cmder is probably just going to annoy you. It's ConEmu in portable app mode with different defaults and some bundled tools.

Re: Tmux and Vim – better together

#206
post #93
post #75

Earlier quoted context omitted.

Nothing works out of the box, especially if you are trying to make two plugins work nicely with each other. If you want IDE like features i.e Autocomplete than you have to spend days to make it work and even after that it doesn't work like other "GUI" editors. + Terminal interface is very limiting to have nice plugins... I'm really glad I've switched to VSCode..

Same exact experience here. Like, I could never get ES6 highlighting to work in Vim. Just flat out didn't work, so all non-ES5 code I write looks terrible. Could be a conflict with my theme or something else. I don't know, or care to do the work to figure it out. I used Vim for a good 5 years. I still miss many things about it, but a shitty default UX is not one of them.

For anyone else who happens by and has the same issue, vim had (has?) substandard syntax highlighting for javascript. Pulling in pangloss's vim-javascript (https://github.com/pangloss/vim-javascript) fixed that up for me. If you write JSX, you can pull in https://github.com/mxw/vim-jsx to get great highlighting for that too.

Re: Tmux and Vim – better together

#207
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 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 wish someone would build a VSCode-like shell around kak, in order to provide a good IDE experience. I keep thinking it should be possible using Qt, with plugins providing a GUI part in the form of a QML widget that gets embedded in the GUI, and possibly a daemon component that gets started and managed automatically by the shell. So e.g. you'd have a file browser widget on the left showing recently opened files etc. that spawns new tabs or opens existing ones when you click on the files. But you could also instead have a project widget or whatever. Basically I want someone to make a pluggable IDE, with a focus on adding graphical widgets for the purpose of richer interaction than plain terminal allows, but lighter and easier to extend than Eclipse, one which focuses on integrating with a specific editing component, in this case kak.

Re: Tmux and Vim – better together

#208
post #109

I'm really a little disappointed how much this article is about using plugins and additional tools instead of learning to integrate both tools by oneself. At least vim is not a tool that gets better by plugins.

Vim absolutely gets better with plugins. ctrlp.vim, vim-tmux-navigator, vim-clang-format, ag.vim, vim-fugitive, supertab, vim-surround are all valuable plugins that I make use of every single day.

Re: Tmux and Vim – better together

#209
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.

Huh? my plugins never interfere with each other.

Re: Tmux and Vim – better together

#210

Tmux is a great program, especially when trying to edit on a remote server. But I think it's worth pointing out that for most purposes, Tmux is basically just a Tiling Window Manager that only works on your terminals. Tiling Window Managers are awesome, and I totally see why people who can't use one would choose to use Tmux, but if you have the option, I would totally recommend just going with the TWM and skipping Tm…

Used Ion for years but finally just "upgraded" to fvwm2 and multiple tmux terminal windows. Reason? More often than not dozens of Unix hosts are being accessed through SSH rather than X. Tmux is always there, regardless of method of connection. Also, use the antique "nvi" (rather than Vim or Neovim) whenever possible. Same reason; it's always there, no tweaking.

If I find myself craving extra functionality I'm probably overthinking things and am in need of a vacation.

Post reply on HN