Memasang Inkscape 0.92 di Ubuntu 14.04

Ilustrasi yang dibuat menggunakan inkscape. (sumber: https://inkscape.org/en/~artelnjeru01/%E2%98%85about-092-2-good )

Baru-baru ini, inkscape merilis versi stabil terbarunya, yakni versi 0.92. Jika kita menggunakan distribusi GNU/Linux, pembaruan versi biasanya kita lakukan melalui kanal pembaruan yang sesuai dengan distribusi yang kita gunakan. Semisal, kali ini kita kan melakukan upgrade ke versi 0.92 pada distribusi Ubuntu 14.04 (Trusty Tahr).

Baca lebih lanjut

Freezing VIM

This is happen when I press Ctrl + S in your VIM. Cause VIM do not response any input. Means, VIM do not print (but still save) anything you typed. Even when you try to kill them (sending kill signal to VIM).

You can get back your VIM into “normal” condition by pressing Ctrl + Q. And viola.. VIM now print everything you typed before.

The reason is, as Michael Mrozek explained, pressing Ctrl + S will trigger xoff that will disable screen painting. This screen painting will be reenabled by  pressing Ctrl + Q (trigger xon).

Congratulation.
Thank’s to Stackoverflow and all.

Redirect error to standard output

Assume we are executing a program and want to read the error. Usually the error output is just running up fastly and then left you at the last error only. So, we need to display it per page. But How. Because Linux send the error output in different ‘channel’ then normal output (called standard output).

Example

The error come out from this program execution will run to the end rather than displayed correctly per page.

$ ./some_script.sh | more

What you do above is actually display the standard output. So you cannot catch the error, even they still printed in screen.

Redirect to file

Yes, instead of display directly in screen, you can save (read: redirect) the error output to screen. This is what normally I do. Because I can read it later.

$ ./some_script.sh 2> error.$(date +%Y%m%d-%H%M).log
$ more error.20160101-0920.log  # the filename is example only

But, for some reason, we need to display it directly. What we can do is something like this

$ ./some_script.sh 2>&1 | more

The command above is to send the error output to standard output (2>&1) and then pipe it to more (you can use less for more interactive navigation). Using more (or less) is my recommended way, due to the output can be very-very long.