![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://sh.itjust.works/pictrs/image/bae905b8-0357-4d8f-aeee-8c3227e76c8c.png)
Topmost: Egypt, below that: Jordan, below that: Saudi Arabia, left: Isreal, right: Iran
Topmost: Egypt, below that: Jordan, below that: Saudi Arabia, left: Isreal, right: Iran
Yep, and align
isn’t a real property, either.
It’s a typo. The colon should be a semicolon. But since it’s the last declaration, it’s optional.
I never understood this logic
You’re looking for logic in a joke.
Do you question why Donald Trump, the pope and a kid are the only passengers on a plane that’s about to crash?
More like
Problem → new ProblemSolverFactory().createProblemSolver().solveProblem();
What you’re showing here is an extra processing step, but I wouldn’t call that manual.
Yes, it’s not manual by the dictionary definition, but it is an extra step. This is another meaning of manual in my particular bubble [Edit: that I didn’t think to specify].
But a much better idea would be to use
sensors -j
to get json output, intended for machine reading, and pass that tojq
.
This is my initial point, exactly. Dealing with objects is way easier than using the ‘default’ line-wise processing. Only Powershell made that the default, while in Linux you need to hope that utilities have an option to toggle it on – and then also have jq
installed to process the objects.
I look forward to seeing how you would do this in PS. As I said previously, I don’t know it at all, so I’m not sure what you’re comparing this to.
[Edit, since I forgot to answer your main point:] I don’t program in PS. I don’t like the verbosity. But I do think MS has a point in pushing objects as the prime unit in processing instead of lines.
For instance: Get the temperature of the “Composite” sensor from this output:
$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tctl: +37.1°C
BAT1-acpi-0
Adapter: ACPI interface
in0: 16.07 V
curr1: 1.80 A
amdgpu-pci-0500
Adapter: PCI adapter
vddgfx: 1.46 V
vddnb: 918.00 mV
edge: +35.0°C
slowPPT: 1000.00 uW
nvme-pci-0200
Adapter: PCI adapter
Composite: +28.9°C (low = -5.2°C, high = +79.8°C)
(crit = +84.8°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +37.0°C (crit = +120.0°C)
Without a cryptic awk incantation that only wizards can understand, that would be:
sensors | grep Composite | grep -Po 'Composite:.*?C' | grep -Eo '[[:digit:]]{1,2}\.[[:digit:]]'
Don’t you think immediately getting the property you’re interested in from an object is easier and more readable than first grepping some output to get the line you want and then removing the leading and trailing garbage on that line manually?
I thing PS scripting would be much more fun if the words weren’t so annoyingly long.
In the civilized world it’s not even illegal to lie to the police (as a defendant).
I wish I hadn’t forgotten that there’s an Emoji for every flag. Thank you.