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.
Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
Preliminary but works, even though I'm probably doing some stuff wrong/dumbly. Basically, "if input is idle for less than two minutes, then grep the active window, if it's the same active window for two times in three 30-second time-windows, count it as active ; after looping N times, show a rudimentary bar graph of how many times each logged window was used."
It would be nicer to actually transform the counting of each program in a percentage of the total, but it's good...
If you ever see yourself wanting to manipulate gxmessage dialogs/windows with wmctrl for some reason, you may notice the name of the window set by gxmessage itself is kind of ignored, depending on the parameters you'd use on wmctrl. It will instead still behave as if the window title was "Gxmessage," or yet "gxmessage.Gxmessage," depending on wmctrl parameters. Which is troublesome if you have more than one.
I thought it would be needed to grep the title from a...
Posted 12-31-2019 at 03:58 AM bythe dsc (linux-related notes)
It has split view, and can have a permanent filter field, at the same time it's faster to come about and perhaps even to navigate (that may be just an illusory impression).
It's still miles and miles away from KFM of KDE3, but I believe humankind will never again match that greatness. Sad that "trinity" never got as much adoption as Mate.
Have you ever seen or being interested in watching a video with some eerily poor framing source, like, the center of interest would be slides that are shown tiny as "a picture in picture" kind of thing? This script is the handiest tool to make them watchable, if the resolution is high enough:
Sed "default" delimiter is "/", or at least that's what most people use. I tipically find "|" more readable, so that's "my" default. Regardless, it can still be troublesome if you're dealing with paths and variables, it seems somehow the command will "break up".
Glenn Jackman posted on Stack Overflow:
Quote:
A pure bash answer: use parameter expansion to backslash-escape any slashes in the variable:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
