Tmux and Vim – better together • Hacker News Board

Re: Tmux and Vim – better together

#281

Post by afghanPower » Fri, Apr 21, 2017, 3:07 PM UTC

Taek wrote: post #187

I've found my flow with vim+i3+ranger i3 is a window manager that can outcompete anything you can do with vim splits or a tool like tmux/screen. It's whole existence is based around putting windows in the right place at the right time. Ranger is a vim-like ncurses file browser. I think it's genuinely one of the most underappreciated tools in programming. The ability to hjkl through your file system, with quick marks,…

For people wanting to try i3/awesomeWM/anotherTilingWM: Learn all the keyboard shortcuts, not just the basic ones. Spend some time on perfecting the configuration for you. Make keybindings that make sense to you.

Tip: Once you realize that you can make everything tabbed/stacked, your workflow becomes really fluent.

Example:

Workspace 1:

    Stacked (left):
        VIM - ASM / C
        terminal
    Stacked (right):
       ddd
       firefox (stackoverflow ftw)

Re: Tmux and Vim – better together

#282

Post by jamesgeck0 » Fri, Apr 21, 2017, 3:16 PM UTC

baldfat wrote: post #221

jamesgeck0 wrote: post #205

Earlier quoted context omitted.

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.

You certainly can configure ConEmu but you can't make it into Cmdr.

Cmder is a bundle of ConEmu, configuration files, a tiny launcher that makes ConEmu's portable app mode easier to manage, and some provisioning stuff for the unix tools and cmd enhancements.

I'd use Cmder if I needed to carry a complete environment around on a USB stick, but it's not difficult to set up something similar for a single system manually with ConEmu.

Re: Tmux and Vim – better together

#283

Post by wsdjeg » Fri, Apr 21, 2017, 4:24 PM UTC

matzy wrote: post #234

dotsh wrote: 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…

SpaceVim help many people move to vim. as I know arroud me.

Re: Tmux and Vim – better together

#284

Post by _e » Fri, Apr 21, 2017, 4:26 PM UTC

vonkow wrote: post #216

city41 wrote: 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.

Check out spacemacs, it works beautifully out of the box.

Spacemacs is only good if you actually use it consistently throughout the day.

From the prompt, it is faster to open a large file in vim than emacs since you have to wait for all of the spacemacs plugins to load.

Re: Tmux and Vim – better together

#285

Post by greenshackle2 » Fri, Apr 21, 2017, 4:32 PM UTC

austinpray wrote: post #64

On my mac I used tmux and vim for years. However, only after building a little arch linux box did I realize I actually wanted a tiling window manager and an ide all along.

At one point I was using a tiling WM and tmux. But between the WM, tmux and vim windows.. well, I don't really need 3 layers of tiling, so I got rid of tmux.

Re: Tmux and Vim – better together

#286

Post by nobleach » Fri, Apr 21, 2017, 5:31 PM UTC

matzy wrote: post #223

artursapek wrote: post #66

Earlier quoted context omitted.

Why does Atom feel more productive?

Because he/she never learned how to use vim

I am a huge fan of Vim. I've used it for quite a few years... but vim-mode-plus for Atom has made me very happy for the last month.

Re: Tmux and Vim – better together

#287

Post by tcoff91 » Fri, Apr 21, 2017, 6:16 PM UTC

erikb wrote: post #276

tcoff91 wrote: post #208

Earlier quoted context omitted.

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.

But you don't know what it stopped you from discovering about vim core that you solve your problems that way. And as shown in another comment in this thread, each problem you can solve with vim core you can combine with other features: E.g., if you don't use a plugin for command execution and instead learn about ":!command" then you will at some point be able to automatically read the results from your command into t…

I still do those things you are talking about (really handy to read the output of find into the buffer when creating a new CMake file), but you are going to be hard-pressed to achieve something like :Gblame command from vim-fugitive or the funcitonality of ctrlp.vim without plugins.

Re: Tmux and Vim – better together

#288

Post by btschaegg » Sat, Apr 22, 2017, 9:31 AM UTC

zeroxfe wrote: post #48

adrianN wrote: post #33

Earlier quoted context omitted.

Neovim tries to improve defaults. My vimrc is 32 lines and contains no ifs and I'm reasonably happy with it. I don't use many plugins. The configuration is only as complicated as you make it to be. I suppose over the decades you used vim your vimrc accrued many layers of cruft. I wonder how your VSCode config will look like in 20 years.

> The configuration is only as complicated as you make it to be. Sure, I understand that, and it's tricky maintaining a balance between simple configuration and features. My point is that with VSCode, there's just so much I get for free, with a very pleasant user experience. I still use vim when I need a quick editor in a terminal, but VSCode is my always-on go-to editor of choice for coding. > I suppose over the dec…

> Still, it's a pain point that VSCode takes away. :-/

Interesting. May I ask why you use that particular smiley then? If VS Code works better for you, isn't that a good thing?

However, I would also be interested if there's more to this for you than the configuration. VS Code is the nicest editor I'm allowed to use at work (because it's a MS product, some companies are really paranoid when it comes to other software) - but I never really warmed up to it. It feels very clunky to me when compared with Sublime Text or Neovim. Also the Vim plugins for it really haven't impressed me so far.

Am I missing something, or is this a pure matter of taste?

Re: Tmux and Vim – better together

#289

Post by btschaegg » Sat, Apr 22, 2017, 9:46 AM UTC

bigger_cheese wrote: post #256

ruleabidinguser wrote: post #167

Earlier quoted context omitted.

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…

For a debugger I usually run gdb in a terminal it initially had a pretty steep learning curve but I find it to be extremely powerful I mostly use it for analyzing core dumps rather than stepping through breakpoints. Being able to backtrace and step through stack frame by frame is really, really useful.

This.

I've only spent a few hours in GDB so far (mainly because my working environment doesn't let me), but once you've tried it, it's astonishing how little comfort most IDEs actually give you when compared to it.

I had to remotely debug C/C++ code on a very obscure ARM platform. Normal IDEs didn't get me anywhere. There are GDB wrappers like Nemiver that worked, but still were very clunky.

But with GDB in TUI mode, I just had to SSH in. If I have to learn two or three commands to use it, so be it.

Every time I have to do any of that remote debugging dance with any Microsoft product, I still long back for my GDB terminal. :-/

Re: Tmux and Vim – better together

#290

Post by erikb » Sat, Apr 22, 2017, 1:04 PM UTC

tcoff91 wrote: post #287

erikb wrote: post #276

Earlier quoted context omitted.

But you don't know what it stopped you from discovering about vim core that you solve your problems that way. And as shown in another comment in this thread, each problem you can solve with vim core you can combine with other features: E.g., if you don't use a plugin for command execution and instead learn about ":!command" then you will at some point be able to automatically read the results from your command into t…

I still do those things you are talking about (really handy to read the output of find into the buffer when creating a new CMake file), but you are going to be hard-pressed to achieve something like :Gblame command from vim-fugitive or the funcitonality of ctrlp.vim without plugins.

Yes, you can't achieve the same thing without the plugins. You also can't achieve the interactive debuggers that IDEs have. But have you missed those? After some time I bet you've found other ways to debug your code that are just as handy, maybe not in all cases but therefore are even better in others. When I started to miss debuggers it forced me to really learn strace, logging frameworks of my favorite languages, dmesg, and journalctl filtering. It's still more work than setting up a breakpoint and tabbing through my code, but on the other hand I have it available as well, when I need to debug a wordpress plugin a contract worker wrote for my customer 10 years ago on a webserver that has none of my usual settings, plugins etc. In the end the pros and cons equal out I'd say.

And let's assume we can agree on that: Great plugins and great skill can on average be just as good. Why do I think that in vim plugins are the wrong course? Because everything in vim is based around skill. You can't even navigate efficiently without spending some time learning search, word/block navigation, etc. If one wants to achieve success with plugins I'd say it's much smarter to build your tools on a foundation that is created for plugins like emacs or an IDE.