Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
02-05-2014, 12:37 PM
|
#1
|
Member
Registered: Aug 2012
Posts: 484
Rep: 
|
Where is Slackware's GNU Screen vertical split?
The answer is: right here!
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
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
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.
Enjoy.
--mancha
Last edited by mancha; 02-05-2014 at 01:14 PM.
|
|
|
02-05-2014, 12:53 PM
|
#2
|
LQ Guru
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,418
|
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...
|
|
|
02-05-2014, 04:40 PM
|
#3
|
Member
Registered: Oct 2011
Distribution: Slackware64
Posts: 364
Rep:
|
Very cool. I have also migrated to tmux, but really appreciate this screen update.
|
|
|
02-05-2014, 05:15 PM
|
#4
|
Senior Member
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,223
Rep: 
|
i3 wm is great for that
|
|
|
02-06-2014, 12:18 AM
|
#5
|
Member
Registered: Jun 2005
Location: Raleigh, NC, USA
Distribution: slackware
Posts: 88
Rep:
|
first class mancha. I've been using other patches for this, but did not look as clean. Much less did they have additional functionality. Thank you sir.
|
|
|
02-07-2014, 08:54 AM
|
#6
|
Member
Registered: Aug 2010
Posts: 353
Rep: 
|
First - Thank you very much, Mancha!
Second - this thread made me want to try tmux and so I did today.
It is nice - But - it has one big shortcoming. One can not write to any of the pseudoterminals created by tmux. Why? Because tmux does not update utmp.
From the tmux faq:
Quote:
Nobody has really come up with a clean, portable way to do this without making tmux setuid or setgid yet.
|
Huh?? gnu screen is not setuid on Slackware and it is able to update utmp just fine.
Code:
lrwxrwxrwx 1 root root 12 Feb 6 21:05 /usr/bin/screen -> screen-4.0.3
-rwxr-xr-x 1 root root 374988 Feb 6 21:01 /usr/bin/screen-4.0.3
How does gnu screen do that? I don't know.
gnu screen rocks!
Code:
username@hostname:~/ > tty
/dev/pts/3
username@hostname:~/ > write username pts/6
write: username is not logged in on pts/6
username@hostname:~/ > ps -aef | grep -E "16582|16588"
username 16582 1 0 20:36 ? 00:00:00 /usr/bin/tmux -f /home/username/.tmuxrc new-session -n something ~/some.program
username 16588 16582 0 20:36 pts/6 00:00:00 -bash
username 16645 16441 0 20:40 pts/3 00:00:00 grep -E 16582|16588
username@hostname:~/ >
|
|
|
02-08-2014, 11:33 PM
|
#7
|
Member
Registered: Aug 2010
Posts: 353
Rep: 
|
Here is the answer on how gnu screen is able to update "/var/run/utmp" - libutempter.
Now this begs the question - why isn't tmux using libutempter? And get it over with.
Time to get out my VIm. 
|
|
|
All times are GMT -5. The time now is 01:58 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|