This is a short compilation of 6 bulk processing command line examples from 6 of our previous articles about bulk images converting, resizing, reducing (file size), rotating, and flipping. Here we mention only the title and the command lines, without the explanations (but we give a link to the corresponding article), for every action of processing below. For those don't know, the command lines here are basically just bash looping commands combined with ImageMagick's convert command lines.

If the previous post talked about converting, this post gives examples about resizing. ImageMagick has a -resize option to help you resizing images by percentage value. Combining ImageMagick's convert -resize command with bash looping resulting in bulk resizing.

This short tutorial shows how to convert multiple files from PNG to JPEG format (and vice versa) using ImageMagick command lines and bash looping. Including explanation to make it easier to understand. This is much more easier than doing it manually one by one.

This article is a more 10 examples continuation from the Episode 3 of our GNU sed command lines the series. This article covers how to combine sed with bash looping with delay time and sed line printings in general. This covers some examples about how to count line numbers, printing the first/last line, in single and multiple files. This article mixes some of the previous examples so if you miss something here we suggest you to read them first.

GNU sed (stream editor) is a clone of UNIX sed command line program from GNU operating system. GNU sed is almost always included in every GNU/Linux distribution (e.g. Ubuntu). While the most of computer users edit a text file only with a real time text editor like Notepad, UNIX family users can edit a text file by a stream editor like sed. This article gives you the examples of stream editing for text file(s) with GNU sed. Because of it is GNU sed it is universal, so if you don't use Ubuntu (but at least you use any GNU/Linux distro), you can practice all of these command lines correctly. If you use another family of sed (e.g. UNIX or BSD one), probably you will need to adapt some commands because they have some differences.