Earlier quoted context omitted.
On a production server? You're doing it wrong.
what's the alternative?
Just learn the default key bindings.
Using tmux properly
211–218 of 218 posts
Re: Using tmux properly
#212Earlier quoted context omitted.
A friend suggested remapping the Screen command key to ` (backquote), and it changed my life. Maybe it's because I grew up using Esc key combos a lot (terminals with broken/missing meta keys), but it feels natural to treat it like another modifier key there on the left edge of the keyboard.
I did that as well, and it was Great and Good and obviously the Right Thing — right up until I pasted in a some shell code which used `` instead of $(). Never again. These days I use C-z for tmux. It works, and C-z z is easy enough to type when I want to put something in the background.
I just switched from C-z to C-q and couldn't be happier. C-z was fine, but I realized it was a really unergonomic stretch. With caps lock as ctrl, C-q is only a slight movement of my ring finger.
Re: Using tmux properly
#213Re: Using tmux properly
#214Earlier quoted context omitted.
What is better with avy?
https://github.com/abo-abo/avy AFAICT it's a superset of ace-jump, with some better thought out commands and better ways to call them.
There is only one command I use so I don't see what else I would need from such a plugin.
Re: Using tmux properly
#215Yesterday I was helping a friend setting a box with no graphical session: I fired up tmux in the linux virtual terminal and then proceeded to realize without my tmux.conf I couldn't do a thing because I have always been using entirely different keybindings from the default. This is the problem with too much customization. Learning to use the default configuration may be difficult but it's probably worth the effort, f…
This is more tmux' fault for having terrible default keybindings (and settings) and I'd rather not waste my time learning and configuring them. That's where byobu comes in.
Re: Using tmux properly
#216Earlier quoted context omitted.
"having non-standard configuration is inherently more complex" I disagree. It can be more complex, but it is not at all inherent. If I configure my shell, my editor, my whatever software to work more like other software I use (keybindings, etc), I can actually make it less complex for me, because copying over a few config files on those rare occassions I need to is much faster than trying to learn a whole new set of…
fish shell dev here. > People have different preferences on how things work, and some of the choices on how to do things are mutually exculsive. Yes! But asking the user to manually configure the system is a lame way to accomodate those preferences. It's better if the software can learn from the user. For example, if the user runs a certain command frequently, don't wait for the user to define an alias, just suggest…
Fair enough. I'm all for having the program do some intelligent prompting of the user, as long as it doesn't become annoying (like Microsoft's "Clippy" :-D).
There is a sweet spot with most software between being buried in a sea of options and having no options you can configure at all. I tend to gravitate toward having a sensible set of defaults and letting the user configure them otherwise if they want. Having options grouped together can be good too (like keybindings -- vim vs emacs style bindings for example).
I also like the idea of customization through functions/scripting rather than just giving the user a choice between N options. That's another area where a set of sensible defaults can be good -- defaults in that case, which can be programmed around.
BTW, thanks for responding here. Always nice to get feedback from the developers of a piece of software directly. I really haven't looked at fish for years (though I'm certain I checked it out a while back). I'll give it another look to see if there's something there to catch my interest.
Sorry I didn't see your response until today, I was busy the last couple of days and just got back to it.
Re: Using tmux properly
#217After experimenting with mosh, tmux, screen, etc I've finally found my ideal ssh setup. At work I do development on my Mac and run builds on a cloud desktop. My Setup: 1. Unison for file-sync ( https://www.cis.upenn.edu/~bcpierce/unison/ ) 2. iTerm on Mac 3. AutoSSH for more durable SSH sessions (ex. close laptop & reopen at home) - http://www.harding.motd.ca/autossh/ 4. tmux -CC command to attach to tmux session wit…
Ironically, you got me interested in trying out Unison, but the download links are broken :(
Re: Using tmux properly
#218Earlier quoted context omitted.
what are those 3 settings on vim ? I assume line numbers is one of them, which are the other 2 ?
For many people, line numbers are the first thing they set up - I never understood that. I customize vim quite heavily, and have tried showing line numbers, but all they do is take up 4-5 characters of precious window width! I can see the current line in bottom right, and when I want to go to a line, I use `45gg`. TL;DR people are different.
I've never really gotten into absolute line numbers, but relative ones are a godsend for me since I use j, d, et al a lot but can't really eyeball how many lines away something is once it gets to be more than 2 or 3.