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.
The syntax of "ln" requires full path information of the "source" file. Therefore, if you issue something like "for file in *.foo ; do ln -s ./$file /other-folder/somewhere/$(echo $file | sed s/foo/bar/) ; done", the produced symlinks will be empty.
To avoid that, the command must be:
for file in *.foo ; do ln -s $PWD/$file /other-folder/somewhere/$(echo $file | sed 's/foo/bar/') ; done
Posted 08-25-2013 at 11:18 PM bythe dsc (linux-related notes)
Updated 08-25-2013 at 11:22 PM bythe dsc
It may be a little bit unsafe to have "rm something" commands in your bash history, if you also have the history easily accessible through up and down keys.
The following line will make bash history ignore "rm" and "shutdown":
Code:
export HISTIGNORE="&:rm *:shutdown *"
I don't know the syntax, but it works.
Some people have add there an expression to make bash's history ignore any line starting with...
I'm not suggesting it's really preferable in any situation or in any specific situation, I just found myself in a "what the hell" point and thought it worth a try, and it worked.
I was just thinking that it would be nice that for slideshow videos there was a variable frame rate, and turns out that it exist. I've found that the program handbrake can handle that easily, so I decided to install. Unfortunatelly it's only on Debians unnofficial multimedia repository, which can...
It will display full paths smaller than 30 characters entirely, but for longer paths it will get only the first characters of the whole path, and the fist characters of the last folder in the full path.
I used to like the condensed variant of Deja Vu, which is the default font (in the regular variation) for many linux distributions/DEs I guess. I've always disliked the regular variant, I find it too wide, while the condensed is very nice to look at. It's quite a hassle to actually use it everywhere though, either the font is buggy, or the apps that read it are buggy. I think it's the former as other fonts with two "nested subtypes/variants" work (such as liberation). The GUI settings...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
