6 ms·
README.md is a good place to check: Compared to tmux To some extend, pymux is a clone of tmux. This means that all the default shortcuts are the same; the com
by paulddraper 11y ago
README.md is a good place to check:
Compared to tmux
To some extend, pymux is a clone of tmux. This means that all the default shortcuts are the same; the commands are the same or very similar, and even a simple configuration file could be the same. (There are some small incompatibilities.) However, we definitely don't intend to create a fully compatible clone. Right now, only a subset of the command options that tmux provides are supported.
Pymux implements a few improvements over tmux:
There is a completion menu for the command line. (At the bottom of the screen.)
The command line has fish-style suggestions.
Both Emacs and Vi key bindings for the command line and copy buffer are well developed, thanks to all the effort we have put earlier in prompt_toolkit.
Search in the copy buffer is highlighted while searching.
Every pane has its own titlebar.
When several clients are attached to the same session, each client can watch a different window. When clients are watching different windows, every client uses the full terminal size.
Support for 24bit true color. (Disabled by default: not all terminals support it. Use the --truecolor option at startup or during attach in order to enable it.)
About the performance:
Tmux is written in C, which is obviously faster than Python. This is noticeable when applications generate a lot of output. Where tmux is able to give fast real-time output for, for instance find / or yes, pymux will process the output slightly slower, and in this case render the output only a few times per second to the terminal. Usually, this should not be an issue. If it is, Pypy should provide a significant speedup.
The big advantage of using Python and prompt_toolkit is that the implementation of new features becomes very easy.
- melted 11y agoThat doesn't answer the question though. Why not just add all (or some) of the aforementioned stuff to tmux? Tmux is an established, widely used piece of software. Any improvements would be much more appreciated there.
- ymse 11y agoYou could say the same about screen vs tmux (or endless other software clones). Projects like these help drive innovation on both sides. Competition, if you like. Besides, Pymux is Python while tmux is C. I'm sure you can appreciate that adding a Python API to tmux would be non-trivial, both code-wise and politically.
- JustSomeNobody 11y agoBut what's the innovation? Adding the python API?
- toolz 11y agoNot everything has to innovate. I understand it would be more useful to you and I if it did innovate, but there isn't some prereq for posting to hacker news that your project has to be innovative. I personally find this project interesting to see, although I won't be using it.
- JustSomeNobody 11y agoThe comment I was replying to specifically mentioned it.
- hueving 11y agoSpend the 30 seconds required to read the ancestor comment explaining what it has enabled WRT prompt toolkit.
- gnuvince 11y agoLook at the list of features that pymux has that tmux doesn't.
- JustSomeNobody 11y agoThat's innovative? Ok, for some loose def of innovation.
- ta0967 11y agoyou seem to have confused innovation with invention. but that's beside the point. you seem to think that software needs to be either to deserve existance. looks like you're in the minority with that opinion, the rest of us is quite happy with iterative, gradual improvement. we consider it better than sticking with whatever the first shot at an implementation managed to hit.
- ossreality 11y agoAbsurd. Created something admittedly slower and cloned all of the rest of tmux's core functionality. Could've spent a week groking the tmux source code base, another to add the fish features and then an extra week to drink on the beach. Instead, there are still months ahead meanwhile 99.999% of tmux users will continue using tmux.
- jzd 11y agoBecause doing it in C might be a waste of time
- njharman 11y agoPure Python is the difference. It runs anywhere python runs. Same can't be said for a compiled C program. It's maybe not a "big" why, or one you care about.
- bch 11y agoI'm not following you -- are you saying that Python runs where C doesn't, or something else ?
- njharman 11y agoI'm saying Python is already installed in places that would require a lot of effort to port and compile C vs just running some.py file. "python some.py" is (in some cases) vastly easier than porting/compiling/signing C code.
- glesica 11y agoIsn't the Python interpreter implemented in C? How could Python run someplace that C can't?
- deadbeef404 11y agoI think he means the exact same Python script can be run directly on any environment that has Python installed if written correctly, in contrast to a C program which has to be recompiled on various environments to be able to run.
- wrenky 11y agoPython as a language is implemented on almost every platform out there- You can just take this source code and run it there, instead of compiling for the target hardware.
- njharman 11y agoOne of them is. And ability to interpret Python is requirement for any python program to be able to run. Being able to build and deploy a c lib is not. So, someone has made python run on Foo platform, lets say a watch. If I have a pure python program I can run it on that watch with no more fuss. If I have to rely on a c library then I have to get that ported to Foo platform, maybe dealing with developer keys and making "authorized" signed binary, etc, etc. Pure python is orders of magnitude easier. That is why "Pure Python" is a thing. Several standard libs come in pure python and C versions cause pure python is an advantage / requirement for some use cases. And speed is for others.
- foota 11y agoIt literally does. "The big advantage of using Python and prompt_toolkit is that the implementation of new features becomes very easy."