Earlier quoted context omitted.
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.
Tmux and Vim – better together
221–230 of 297 posts
Re: Tmux and Vim – better together
#222Earlier 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.
Can you share your 32 line config?
execute pathogen#infect()
syntax on
filetype plugin indent on
set list listchars=tab:>-,trail:-
set ff=unix
set autoread
set number
set relativenumber
set linebreak
set tabstop=2
set shiftwidth=2
set expandtab
set ignorecase
set smartcase
set timeoutlen=1000 ttimeoutlen=0
let $BASH_ENV = "~/.bash_aliases"
color desert
set cursorline
augroup linehighlight
autocmd!
autocmd InsertEnter * set nocursorline
autocmd InsertLeave * set cursorline
augroup END
:hi CursorLine cterm=NONE ctermbg=darkblue ctermfg=white
:hi Normal ctermbg=blackRe: Tmux and Vim – better together
#223Earlier quoted context omitted.
Same boat. I use Atom with vim keybindings now and I feel much more productive than when I rolled with straight vim + tmux. Great tools, but there are much better options these days.
Why does Atom feel more productive?
Re: Tmux and Vim – better together
#224Earlier quoted context omitted.
Pretty much everyone knows the price of admission to using tools like Vim and Emacs is the time investment in config and learning the quirks. What the OP is saying that this doesn't have to be a perpetual state. Once you invest effort early on getting it right you often don't need to touch it, beyond a few tweaks now and then. The maintenance burden definitely declines over time. Then all you need is a storage soluti…
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.
Re: Tmux and Vim – better together
#225Re: Tmux and Vim – better together
#226Earlier 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.
Re: Tmux and Vim – better together
#227Earlier quoted context omitted.
Pretty much everyone knows the price of admission to using tools like Vim and Emacs is the time investment in config and learning the quirks. What the OP is saying that this doesn't have to be a perpetual state. Once you invest effort early on getting it right you often don't need to touch it, beyond a few tweaks now and then. The maintenance burden definitely declines over time. Then all you need is a storage soluti…
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.
Re: Tmux and Vim – better together
#228Earlier 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.
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 yo…
Re: Tmux and Vim – better together
#229All 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 wish I could have had some sort of true-integrated-vim-key-bindings, none of the vim-bindings plugins feel as productive, but editor as a whole has a lot more features for a lot less work.
Re: Tmux and Vim – better together
#230Earlier quoted context omitted.
Your tone and absolutism is getting you down voted like crazy. You're placing the IDE experience on a pedastal and it's really not warranted. IDE's can have lots of problems, speaking as 15 year enterprise java developer. The primary problem is hiding complexity from the developer, which is obviously good and bad. For example, IDE's typically maintain an internal representation of a project, which can get out of sync…
Yea you're right I've overstated my position. Don't really see how vim is useful for excploring a codebase.