danrot

joined 1 year ago
 

The shell history is cluttered with useless commands if stuff like tokens are included. Shell variables allow to exclude such content from the history.

[–] danrot@kbin.social 1 points 10 months ago

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.

[–] danrot@kbin.social 1 points 10 months ago (2 children)

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.

 

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.

[–] danrot@kbin.social 2 points 10 months ago

Doesn't it also use case and esacand a few others? Such a weird language^^

[–] danrot@kbin.social 1 points 11 months ago (1 children)

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).

 

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.

 

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.