Search
664 results for “simonmic”
-
(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.
-
(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.
-
(In future, if osh/ysh get some make/just-inspired features or libraries (seems quite possible), the pendulum may swing back to using shell only.
-
I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.
Here's one for showing a near-term transactions forecast:
# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)
-
I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.
Here's one for showing a near-term transactions forecast:
# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)
-
I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.
Here's one for showing a near-term transactions forecast:
# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)
-
I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.
Here's one for showing a near-term transactions forecast:
# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)
-
I'm using `just` eg to manage developer/maintainer task scripts for #hledger, and to manage personal finance/time/task scripts.
Here's one for showing a near-term transactions forecast:
# show forecast transactions predicted recently and soon
@forecast *ARGS:
hledger print -I --auto --forecast=-15days..+15days tag:generated "$@"(Forecasting explained: https://hledger.org/dev/hledger.html#forecasting)
-
You can achieve some of these things with make, if you work hard enough, and ensure you have the right version, but it's more complicated, more fragile, less portable, and harder for others to understand.
-
You can achieve some of these things with make, if you work hard enough, and ensure you have the right version, but it's more complicated, more fragile, less portable, and harder for others to understand.
-
You can achieve some of these things with make, if you work hard enough, and ensure you have the right version, but it's more complicated, more fragile, less portable, and harder for others to understand.
-
You can achieve some of these things with make, if you work hard enough, and ensure you have the right version, but it's more complicated, more fragile, less portable, and harder for others to understand.
-
Why I’m using `just` for script management after many years with make/shell:
- you can easily list recipes with their docs
- recipes have robust argument handling
- easier and smoother integration with scripting languages
- much fewer idiosyncracies
- more portable (one version, more likely to work on Windows)
- makes things more robust
- frees up vital head space.You have to install it; and you lose the ability to depend on other outputs, for now.
-
Why I’m using `just` for script management after many years with make/shell:
- you can easily list recipes with their docs
- recipes have robust argument handling
- easier and smoother integration with scripting languages
- much fewer idiosyncracies
- more portable (one version, more likely to work on Windows)
- makes things more robust
- frees up vital head space.You have to install it; and you lose the ability to depend on other outputs, for now.
-
Why I’m using `just` for script management after many years with make/shell:
- you can easily list recipes with their docs
- recipes have robust argument handling
- easier and smoother integration with scripting languages
- much fewer idiosyncracies
- more portable (one version, more likely to work on Windows)
- makes things more robust
- frees up vital head space.You have to install it; and you lose the ability to depend on other outputs, for now.
-
Why I’m using `just` for script management after many years with make/shell:
- you can easily list recipes with their docs
- recipes have robust argument handling
- easier and smoother integration with scripting languages
- much fewer idiosyncracies
- more portable (one version, more likely to work on Windows)
- makes things more robust
- frees up vital head space.You have to install it; and you lose the ability to depend on other outputs, for now.
-
In which I share comparable make/bash scripts and a justfile, including some nifty scripts; and touch on why I've adopted just after many years with make and bash:
https://news.ycombinator.com/item?id=38811688 -
https://updown.io/bc6u is a status page for https://hub.darcs.net . I've increased the frequency from 5m to (temporarily) 15s to see if the (hourly ?) cron restarts are detectable.
Incidentally, I'm a happy https://updown.io customer, it's awesome.
-
Lots of #darcs toots I see ! 👍
After receiving some patches, I worked a little on https://hub.darcs.net tonight. It has been running basically maintenance free (touch wood) for years, a goal of mine. It turns out I last compiled it with GHC 8.0 in 2018.
The dev instance https://hub-dev.darcs.net is now up, running latest code (30 new patches) and compiled with GHC 8.10.7. It uses the same repos and db as prod, so you should be able to use it for real work. Testing welcome!
-
I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness. -
I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness. -
I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness. -
I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness. -
I'm a longtime bash user using osh as my default shell for a year or so now, with only minor noticeable issues. I haven't yet had a need to invest time in the still-being-designed ysh.
I feel osh is the killer feature of the Oils project - 1. a truly compatible, cleaned up, principled bash replacement, with 2. optional knobs you can turn to gain more correctness and power, and 3. the promise of easy interop or migration to the next-gen ysh language, providing future-proofness.