Replacing a value in a config file is still easier in vim due to e.g. ciw
or ci"
being a thing.
Replacing a value in a config file is still easier in vim due to e.g. ciw
or ci"
being a thing.
Those are really long business hours
Depending on your country, these ads still need to be marked clearly as such. And for accessibility reasons, that mark will always be machine readable.
So blockers will be fine.
One can read, the other one can write
And it’s not a noun
Only thing to disagree here is 80 char limit, would go for 120 personally.
Also, IMHO, pipes should be at the beginning of the next line, not at the end of the previous one.
Makes cleaner commits and nicer diffs.
But that’s the proper way of eating ramen
Pausing and resuming is possible using curl as well
Why create anything new or different?
Or they vim bindings wherever possible, then those keys are a bit redundant and harder to reach
Just push to a new branch
NAT reflection maybe?
Still using bash occasionally while mainlining zsh, it’s just one of the most ubiquitous shells out there.
I’d rephrase your post title to “Use whatever shell you like, but try not to write Bash scripts”
At least scripts you want others to use… and you are going to be very grateful in the future when you might switch shells
is it that unique?
For me it just strikes a nice balance between a full tiler and a classic desktop UI.
And in my book, you don’t even need any extensions, the core product is fine as it is.
That seems l like a fine addition, although visually an explicit number being shown would be enough and even better imho.
crazy, in my world that’s pretty much full time