SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Note: Not looking to convert tmux users (tmux already has vert splits).
OK, for die-hard screen users still reading this, I built a 3,798-line patch against Slackware's screen 4.0.3 based on adaptations
of cherry-picked code from screen's development branch.
It introduces three new and inter-related features:
Vertical splits (C-a |) work much like horizontal splits (C-a S); operations such as focusing regions, resizing regions, killing
regions, etc. have not changed.
Display layout infrastructure
Those who've used horizontal splits on Slackware's screen already know they don't survive detach/attach cycles well. This
is where "layouts" come in. New layout commands include: new, name, load, save, autosave, next, prev, and attach (see
manpage). FYI, I have my display layouts survive detach/attach cycles by adding "layout new default" to my .screenrc;
As simple as that.
Window groups help organize large numbers of windows into subsets (e.g. thematic groups like coding, networking, etc.).
Groups can be created with: "screen -t GROUP_NAME //group".
I did this for personal consumption but others might find the new features as useful as I do.
So, I uploaded my work (all needed build files) to the Slack Depot.
thanks mancha, I think hardcore screen users (like I was) will appreciate.
waiting for version 4.1 (that would have included this function) I've built a snapshot from git a lot of time ago, but after a little I found tmux and switched to it permanently.
maybe it wasn't such a bad choice as some years has passed and 4.1 still isn't out...