[HN Gopher] Dvtm: A dynamic tiling window manager for the terminal
       ___________________________________________________________________
        
       Dvtm: A dynamic tiling window manager for the terminal
        
       Author : yagizdegirmenci
       Score  : 45 points
       Date   : 2021-04-09 07:54 UTC (1 days ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | evanrelf wrote:
       | I would love to switch from tmux to dvtm + abduco, but dvtm
       | doesn't have 24bit/truecolor support.
        
       | [deleted]
        
       | rnhmjoj wrote:
       | If you are unsatisfied with tmux and familiar with vi, something
       | worth considering is using abduco and the built-in terminal
       | emulator of vim. It will you give windows, tabs and mouse
       | integration for free, it's just missing a couple of bindings to
       | spawn terminals like:                 map <silent><C-w>-  :split
       | +term<CR>       map <silent><C-w>\| :vsplit +term<CR>       map
       | <silent><C-w>t  :tabnew +term<CR>
       | 
       | and the rest you already know.
        
         | johncoltrane wrote:
         | Your mappings are for Neovim, not Vim, where :term already
         | splits the window.
         | 
         | Here they are, fixed for Vim:                   nnoremap
         | <silent> <C-w>-  :terminal<CR>         nnoremap <silent>
         | <C-w>\| :vertical terminal<CR>         nnoremap <silent> <C-w>t
         | :tab terminal<CR>
        
         | rav wrote:
         | Thanks for the pointer to :split +term - I just dug through all
         | of :help terminal. Apparently this is a feature from Vim 8.1
         | that I had completely missed!
        
       | ddevault wrote:
       | dvtm is very good in principle, but in practice its terminal
       | emulation leaves a lot to be desired. I would love to see someone
       | refactor it to use, say, libvterm as the terminal backend.
        
       | vmchale wrote:
       | I get this by default from XMonad though? And I can tile
       | terminals and other things alongside.
        
         | yjftsjthsd-h wrote:
         | It's useful when you're not running under X, or for folks who
         | want to tile terminals but not run a tiling window manager.
        
       | jitl wrote:
       | I skimmed the documentation but wasn't persuaded that this offers
       | much over how I use TMUX already
        
         | linkdd wrote:
         | tmux is literally the first program I install on a new setup,
         | even before wget.
        
           | unk wrote:
           | unless you have to wget your tmux source/package ;)
        
             | linkdd wrote:
             | who said i haven't the tar.gz on a usb stick ready to
             | deploy? :D
        
           | heavyset_go wrote:
           | Same, but Byobu because it has nice defaults for tmux.
        
         | krick wrote:
         | Yeah, my first thought too (well, I guess pretty much
         | everyone's). This seems like "tmux, but less" since tmux is
         | much more than a window manager, and tmux is absolutely not
         | some esoteric software: even if you don't use tmux, you
         | probably know, that if this is something you'd want, you'll
         | install tmux. So, what's the point? Codebase being smaller? I
         | absolutely don't care about the codebase of something I'm not
         | writing myself.
        
       | wantguns wrote:
       | how does this bring a better or even a different workflow than
       | tmux ?
        
         | yjftsjthsd-h wrote:
         | It's not necessarily better from that perspective; it's a much
         | smaller+simpler tool, and it solves some of the same problems
         | in a different way. But if tmux works for you and you're not on
         | a suckless binge, dvtm probably won't be appealing.
        
       | yjftsjthsd-h wrote:
       | dvtm is very much like dwm, both in some superficial details
       | (layouts), and in deeper philosophical ways ( _very_ heavy on
       | doing _only_ one thing well). This is good when you want a small
       | well-scoped tool to do one thing in your stack, but does add
       | friction when you just want everything to work because you need
       | to add more parts to do anything; for instance, dvtm explicitly
       | doesn 't handle sessions the way tmux or screen would; you're
       | expected to run with something else (probably abduco) for that.
       | This is not a negative, but it is a tradeoff.
        
       ___________________________________________________________________
       (page generated 2021-04-10 23:00 UTC)