The shell history is cluttered with useless commands if stuff like tokens are included. Shell variables allow to exclude such content from the history.
I am not exactly sure what you mean by that... But the main advantage is that the command does not have to be executed manually everytime you change something. Instead entr recognizes when something changes and re-executes the command for you.
Ah, you are talking about systemd, wasn't aware of that... I imagine that to be much more complicated for many use cases. E.g. running a unit test (as I describe in the article) isn't something I would use systemd for. Setting up a path and a service seems more complicated than using entr, and it is probably also harder to get to the output as well.
That's true, but the syntax is different then. In this blog post I cover fish, and I didn't intent to say that this cannot be done in other shells (and I think I never said so).
I was refactoring a feature and wanted to know which options were used for a certain attribute in a XML file. I decided to level up my CLI skills for that.
Making the shell history more useful by using shell variables (danielrotter.at) en
The shell history is cluttered with useless commands if stuff like tokens are included. Shell variables allow to exclude such content from the history.
Automatic command execution on file changes with entr (danielrotter.at) en
Sometimes you want a command to be automatically executed as soon as a certain file changes. There is a small tool called entr, which helps with that.
Applying design patterns: The builder and factory pattern in a DI context (danielrotter.at) en
Creating objects is a very basic task. Although this seems like a simple problem, it can be improved by using patterns like builder and factory.
Web Push Book (web-push-book.gauntface.com) en
Web push book provides all the information you need to learn about the web push API.
Execute commands for multiple files using fish (danielrotter.at) en
Quite often I want to execute the same command for multiple files. It is quite easy to achieve that using the fish shell, once you get the hang of it.
Finding used values of XML attributes using the command line (danielrotter.at) en
I was refactoring a feature and wanted to know which options were used for a certain attribute in a XML file. I decided to level up my CLI skills for that.