I'm not opposed to video, but if stuff gets lost in the written version that's more a statement on poor exec written communication skills than video being better than text.
People ingest info differently, and being able to communicate the same info in multiple ways should be table stakes at that level.
FWIW, my .screenrc is 4 lines. My .tmuxrc is 26 lines, and all it tries to do is get a behavior comprable to screen. Ie, using the same ctrl-a,
supporting ctrl-ac without needing to release ctrl before the second character, allowing titles to pass thru tmux to the title bar, etc.
> all it tries to do is get a behavior comprable to screen
So, veering from the tmux defaults to change them to the screen defaults takes more work in tmux than in screen? Go figure! I never would have guessed. (Hint: It's easier in screen because they are the defaults)
I've never used tmux and I find your post to be biased towards screen. tmux isn't being touted as a 'drop-in replacement' for screen, but that seems to be how you are evaluating it.
The problem with a native vim window is that it doesn't give you much affordance in terms of UI, you can't collapse files that have a lot of matches, hard to remember options and syntax for regex/case sensitivity, etc.
The collapsing sounds like a valid complaint. The rest falls on deaf ears for this vim user.
I would expect most vim users to feel the same since those complaints are either considered features or the common barrier to entry that vim has anyway. Am I wrong?
You can consider it a matter of preference, I suppose. I prefer having a GUI file browser over NERDTree for similar reasons as I outlined before. VimAck has the same line of thinking behind it.
reply