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.
Remove rxvt. I don't see a point still using a software last updated 14 years ago, that does not provide any unique feature as far as I know. Yes it's lighter than xterm, but does that still matter nowadays? Anyway there is no lack of reasonably light X terminals, shipped in Slackware or available @ SBo.
Incidentally seeing the rationale for patching it as was done recently in Slackware I checked that typing
Code:
printf '\033[-2147483648L'
does not crash any other X terminal shipped in Slackware that I know.
Now why mlterm? because it is the only X terminal that properly handle all languages of the world, including complex scripts and provides right-to-left rendering including bidi. I know it's available @ SBo, but several billions potential Slackware users would be happy to get it out of the box
Also mlterm is actively maintained (the latest stable version 3.8.1 has been released on 2017-04-29) and it seems to be usable also with a framebuffer (I didn't try yet).
Last edited by Didier Spaier; 05-05-2017 at 05:23 PM.
For example, putting something like this in ~/.Xresources comes in handy for irc links.
Code:
URxvt*url-launcher: /usr/bin/firefox
URxvt*matcher.button: 1
URxvt*matcher.pattern.1: \\bwww\\.[\\w-]\\.[\\w./?&@#-]*[\\w/-]
! Open images in FEH
URxvt*matcher.pattern.2: \\bhttps?:\/\/[\\w-.]*\/[\\w./?&@#-]*.(jpg|JPG|jpeg|png)
URxvt*matcher.launcher.2: feh $0
! Open video links in mpv
URxvt*matcher.pattern.3: \\bhttps?:\/\/(www.youtube|youtube|youtu|vimeo|twitch).(com|be|tv)\/(watch\\?v=([\\w-]*)|v\/([\\w-]*)|([\\w-]*))
URxvt*matcher.launcher.3: mpv $0
! Open gifs in imagemagick
URxvt*matcher.pattern.4: \\bhttps?:\/\/[\\w-.]*\/[\\w./?&@#-]*.(gif)
URxvt*matcher.launcher.4: animate -loop 0 $0
! Open some links in mpv
URxvt*matcher.pattern.5: \\bhttps?:\/\/[\\w-.]*\/[\\w./?&@#-]*.(mp4|ogv|flac|webm|ogg)
URxvt*matcher.launcher.5: mpv $0
I always build without perl, but either way I'd like to see rxvt-unicode included by default. One of us could rebuild if necessary. And I am glad to know I am not the only rxvt-unicode user!
I always build without perl, but either way I'd like to see rxvt-unicode included by default. One of us could rebuild if necessary. And I am glad to know I am not the only rxvt-unicode user!
+1 Would also love to have rxvt-unicode included by default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.