SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So I remember running Terminator (yet another terminal program) back in 2015 or so on my (at the time) debian system. I'd stumbled onto an old screenshot and decided to try it again. OK: Terminator has Psutil as a dependency.
Right: so I put Psutil in. The slackbuild mentioned python 2 and 3 but the line for python 2 errored out. Right: it's for slackware 14.2 which older and staler than debian oldstable and nobody uses python 2?. So I got it to install for python 3. OK, whatever. Success. Next step.
Then, Terminator itself. It installs itself no muss no fuss, neatly as you please. Great. Into the python 2 directories. Oh. Well, there were no error messages so it must be fine, right?
Can I have a hint please? Either I need to trick (and I'm not feeling tricky today) Psutil into installing as python 2 or trick Terminator into installing into python 3, right?
I am using the same "gnome-terminator" Didier suggests, (on -current) with (python3) psutil and (python3) configobj. Works fine for me, at least on current.
I am using 2.1.1 see info below and all that's needed is to version bump the old slackbuild and tweak to python3 (and possibly a few other very minor changes) - this is running on current.
I am using 2.1.1 see info below and all that's needed is to version bump the old slackbuild and tweak to python3 (and possibly a few other very minor changes) - this is running on current.
Well, after playing around on current for a bit and having to use a terminal for more than just "testing", it turns out that I cannot stand the way that when you type in a command that is longer than the window, you can no longer see part of it as it scrolls off to the left.
If someone knows how to change this behavior, please let me know.
For now I have switched to ROXTerm. Which has been revived by the original author and is really nice as well.
@Skaendo. You do know you can enter backslash and continue typing the command on the next line, don't you?
Code:
$ echo a b \
> c
a b c
Yea, too much work. It's OK, I would much rather move away from GTK than bow to the GNOME devs. On top of that, ROXTerm has less dependencies. Like none for building on current.
Edit:
Yes ROXTerm uses GTK, but not intrusively like with headerbars and left-scrolling commandlines. It is optional I believe. If or when it does, I will find ssomething else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.