Vim – Why and where am I getting these errors from?

If you have got this question in your mind, then you are in right place.

vim -V20  2>&1 |tee

You can give the debugfile as any file, where you would want to log the debug messages. This will log a lot of information in the debugfile, you can open the file, once you have got the error in the main vim window. After this, you can open the debugfile and simply search for the error that you were getting. Just look for the reason why this error is originated in the debug logs and then it should be pretty simple to fix that.

 

Enhanced by Zemanta

pigz -parallel gzip

Here is a short description of pigz:

pigz, which stands for parallel implementation of gzip,
is a fully functional replacement for gzip that exploits
multiple processors and multiple cores to the hilt when compressing data.

And for the installation:

sudo yum install pigz

With pigz, if you don’t have many things running on your multi processor machine then you will see a significant improvement when you are gzipping the files.

Enhanced by Zemanta

15 Linux Bash History Expansion Examples You Should Know

Screenshot of a sample Bash session, taken on ...
Image via Wikipedia

Here is a nice link on BASH History Expansion. There are lot of examples in this page and some of them might be quite useful. But here are my list of favourites:

!!

This is probably the most used one by me. This will repeat the last command. And this works even in conjunction with other commands like

sudo !!

And the second most used one is :

!$

This puts the last parameter of the last executed command. So, you could do something like:

ls a/very/long/path/with/file/name
vi !$
Enhanced by Zemanta