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.
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.
Posted 02-26-2013 at 07:37 PM bythe dsc (linux-related notes)
Updated 02-26-2013 at 07:39 PM bythe dsc
Just create a folder "~/.compose-cache".
Or better yet, at least in a semi-philosophical level, have your startup script to create "/dev/shm/.compose-cache" every time, and just create it once, and a soft link to your home folder. No unnecessary access to your disk, writing to and reading from memory instead. Which is often assumed to be better for several cache-type usages, both for performance and (supposedly) for the lifespan of your hard disk*. Some people...
Posted 01-28-2013 at 10:21 AM bythe dsc (linux-related notes)
Updated 01-28-2013 at 06:10 PM bythe dsc(fixing some stuff, redirection didn't work that way)
On KDE you can set "keepshape" on "systemsettings", but apparently there's no way to do it in any other DE. The proper way to have "keepshape" working does not seem to work on Debian Wheezy (setting it on xorg.conf.d/50-wacom.conf). The "standard" alternatives are a static xorg.conf, and perhaps figuring hal/udev rules, which I don't know how to do.
Another way to do it is via xsetwacom, explicitly setting the active area along the lines of:...
Posted 11-21-2012 at 12:48 PM bythe dsc (linux-related notes)
If you like mplayer's native GUI, and you're about to install Debian testing (currently Wheezy), avoid using packages from deb-multimedia as much as possible.
To me it seems that the problem is actually with ffmpeg (deb-multimedia's), but I'm not willing to test it. I think it somehow interferes with mplayer-gui/gmplayer.
Just a few days ago I had an Wheezy install where I had gmplayer working, but very inconsistently, I would double click some video file and in five...
I thought that the only way to do such type of loop in Bash would require something like "n=$(($n+1))" within the loop, with the loop being conditioned to "n" adding up to whatever you want, such as "until ((n==30)) ; do". But you can actually do "for i in {1..20} ; do <whatever> ; done". That's somewhat similar to Basic's "for i=1 to 20 ; whatever ; next i".
But it won't work with variables for the starting and ending numbers....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.