At this stage of our Bash basics series, it would be hard not to see some crossover between topics. For example, you have already seen a lot of brackets in the examples we have shown over the past several weeks, but the focus has been elsewhere.

For the next phase of the series, we’ll take a closer look at brackets, curly, curvy, or straight, how to use them, and what they do depending on where you use them. We will also tackle other ways of enclosing things, like when to use quotes, double-quotes, and backquotes.

This week, we're looking at curly brackets or braces: {}.

Concerning about the features, we can list the following:

Theming and color schemes.
Configurable hotkey schemes.
GNU Screen style hotkeys available by default.
Full Unicode support including double-width characters.
Doesn’t choke on fast-flowing outputs.
Tab persistence on macOS and Linux.
Proper shell-like experience on Windows including tab completion (thanks, Clink!).
CMD, PowerShell, Cygwin, Git-Bash and Bash on Windows support.
Default Linux style hotkeys for copy (Ctrl+Shift+C) and paste (Ctrl+Shift+V).
Multi-platform support. It supports Windows, macOS and Linux.
Free and open source.

I recently worked on creating a Bash completion script for a project, and I enjoyed it very much. In this post, I will try to familiarize you with the process of creating a Bash completion script.

What is Bash completion?
Bash completion is a functionality through which Bash helps users type their commands more quickly and easily. It does this by presenting possible options when users press the Tab key while typing a command.

Here is my Katas for creating BASH programs that work. Nothing is new here, but from my experience pepole like to abuse BASH, forget computer science and create a Big ball of mud from their programs.
Here I provide methods to defend your programs from braking, and keep the code tidy and clean.

Overwhelmed with the response of last two articles of “Lesser Known Linux Article” series namely.

kolorowanie wyjścia w skryptach basha