i'd give all that away to instead have tab completing based on man page parameters descriptions or something.
So like zsh? https://pastee.org/uka5q
Terminology – a new terminal emulator
111–120 of 143 posts
Re: Terminology – a new terminal emulator
#112Re: Terminology – a new terminal emulator
#113Earlier quoted context omitted.
setw -g mode-mouse on setw -g mouse-select-window on setw -g mouse-select-pane on setw -g mouse-resize-pane on
Thanks. On a random note, why do all unix applications (generalising I know) seem to default to a super-minimal set of options? Surely the kind of people who get annoyed by mouse integration (and you can just ignore it) are the kind of people who can find out how to turn it on, whereas those of us who are using tmux for the first time want all the nice options turned on by default?
Although thank goodness for HN. Now I am aware of tmux mouse-mode and this makes things glorious.
Now I just need to figure out a slick way to take the tmux selection and connect it to X's primary clipboard and I will be happy.
Re: Terminology – a new terminal emulator
#114It looks cool and all, but I just want a Linux term than can log all output a file so I have a record of what I did. There doesn't seem to be any decent ones out there.
Re: Terminology – a new terminal emulator
#115Earlier quoted context omitted.
Only better if you are up for 500mb of dependencies and having to learn Haskell to configure your desktop.
Configuring XMonad is a very good reason to learn Haskell, among many others.
Re: Terminology – a new terminal emulator
#116Earlier quoted context omitted.
setw -g mode-mouse on setw -g mouse-select-window on setw -g mouse-select-pane on setw -g mouse-resize-pane on
Sadly this still leaves you with a rather crippled subset of the real thing. I.e. "copy mode" instead of proper scrolling, no native text selection, and very noticeable latency and glitches. It's the price you pay for emulating a 35 years old piece of hardware[1] inside an emulator of the same... [1] http://en.wikipedia.org/wiki/VT100
With tmux's copy-mode, you can even select text without touching your mouse, using e.g. vim-like movements. Which is amazing feature.
The fact, that the copy-mode doesn't jump back down with every change on stdout is also very nice feature.
If you want to work with standard linux clipboard, you still can - just hold shift and select like in almost any linux TUI application.
Re: Terminology – a new terminal emulator
#117I really, really like terminology (as i like Enlightenment), but i am waiting until it supports Tabs, the only thing missing for me. As to all the "uhh, i don't want additional stuff" comments: There is no reason a terminal emulator can look nice as long as it doesn't distract. And so far, terminology does a really good job! And good, does it look sexy.. ;) Keep up the development of terminology, one user here for su…
Re: Terminology – a new terminal emulator
#118i'd give all that away to instead have tab completing based on man page parameters descriptions or something.
Now if someone could integrate that with bash-completions =)
Re: Terminology – a new terminal emulator
#119I used to care a lot about tabs and pane splitting in the terminal emulator. Then I discovered terminal multiplexers: screen, then tmux. Now I don't want those features in the terminal emulator anymore, as they overlap and even conflict with the terminal multiplexer.
- Multi-plexing in the terminal
- screen/tmux
- multi-plexing in the WM
And it's pretty nice ! Written by hackers, for hackers.
Re: Terminology – a new terminal emulator
#120Earlier quoted context omitted.
I still like tabs. I'm often logged into multiple remote machines where, for me, a terminal emulator's tab represents a unique SSH connection and that tab then has tmux running on the remote machine. Otherwise, I'd be running tmux on my local machine, then want to run tmux on a remote machine, and nesting terminal multiplexers is not good.
I think that's a big differentiator in people's CLI preferences. When I see prompts that don't include $HOSTNAME, and people eschewing tabs for multiplexing in all cases I just assume they rarely manage remote machines.
also, using ^a^a to send commands to the nested tmux isn't so bad.. but to get to the third one down you need to use ^a^a^a^a as you need to send a ^a^a to the second one in..
for the fourth nest you need 8 ^a's, but again, it's a bit like code indentation, if you're 4 tmuxes deep, then there's a good chance you're doing it wrong
but still, it's nice to be able to do it if necessary