it just had less brackets and <> symbols when they were done.
Hence making the parser more inefficient than XML?
The wheel is Open Domain and does not belong to anyone.
So I looked at the thing and it looked kinda reasonable.
how many things do I have to read
Well unfortunately, when using Arch, you will, at some point end up requiring to read a lot of something.
If that makes you hesitate, but you still feel like giving it a try, I'd say one good way is, install Arch using the Arch ISO method and go to https://wiki.archlinux.org/title/Installation_guide and read that once before and then, while installing.
I’ve had Arch get borked, but never to an unrecoverable state.
gotta love arch-chroot for that.
No matter what went wrong or how wrong it went, if you have the time, you can find out.
And pretty easily too, as long as you keep some logs.
Papaya over here. Apples would be too expensive.
That looks like buttons in the thumbnail, on the left of the visualisation.
I'd say that's enough to call it UI.
Description, because "alt text" can't show it well:
{
emit differentFiles (ckFile.absoluteFilePath(),
otherFile.absoluteFilePath(),
FileCompareWorker::FileComparisonParams{FileComparisonParams::FileNameMatch,
(ckFile.size() > otherFile.size()) ? FileComparisonParams::File1IsLarger
: FileComparisonParams::File2IsLarger});
}
After Alignment
{
emit differentFiles (ckFile.absoluteFilePath(),
otherFile.absoluteFilePath(),
FileCompareWorker::FileComparisonParams{FileComparisonParams::FileNameMatch,
(ckFile.size() > otherFile.size()) ? FileComparisonParams::File1IsLarger
: FileComparisonParams::File2IsLarger});
}
pops into my head semi-regularly
Isn't that called "trauma"?
You'd want that, but a lot of programs do that, both in Windows and Linux.
e.g. The .directory files with the [Desktop Entry] spec by freedesktop.org
Dolphin has the option to enable/disable the feature
gut push --force does not work.
But I added "force"!
sudo gut push --force still not working.
Of course I don't try to understand the error output. I just see that it is not working.
I have a multiboot system.
One of the installed OS's does not use the NVMe SSD installed on the motherboard at all.
At the time of taking the screenshot, all the SSD partitions are unmounted, so apart from detection, the SSD is mostly unused.
For the unmounted and unused HDDs, I just use hdparm -Y, but there seems to be nothing in terms of that for the SSD.
And even though I appreciate the additional heat in winters, this is going to be too expensive for me. I'd rather burn some cheap Nichrome than my data storage device.
I checked out a Debian forum thread and from that, I checked the following:
❯ sudo nvme get-feature /dev/nvme0 -f 2 -H
get-feature:0x02 (Power Management), Current value:0x00000004
Workload Hint (WH): 0 - No Workload
Power State (PS): 4
Showing it is already in the lowest power state.
Update: I probably checked that at the wrong time before. Did so again after Sleep and realised the Power State was 0. So just need to make sure the Power State went back to 4 after wake.
I have no active cooling setup for the SSD from my side. This becomes relevant soon.
Checking the SSD temps (using the same widget as in the image), the temperature on Sensor 2 starts out at ~40°C (after a normal reboot) and slowly increases to >50°C as shown at the start of the graph. Power State (PS) is still 4.
Running KDE partitionmanager, which probably does some reading to check the partition information, at 50°C stage, causes a temperature drop, as shown in the image.
Running KDE partitionmanager right after reboot, when the temperature is increasing very sloowly, seems to do nothing significant.
PS: 4, so I have the culprit.partitionmanager after that causes it to go back to PS: 4So we have a solution! All I need to do is run partitionmanager on wake. nlol jk
Motherboard: MSI MAG X570S TORPEDO MAX (MS-7D54)
SSD: Samsung 980 512GB (correct firmware, bought long before the fakes started coming out)
Until he actually had to use it.
Took 2 hours of reading through examples just to deploy the site.
Turns out, it is hard to do even just the bash stuff when you can't see the container.
YAML definitely felt less intimidating to me than XML, when I first saw them.
But the YAML examples also had much less information in them than the XML ones.
But not having to type all those brackets definitely helps. In case of XML, I am always looking to just get a GUI going for it instead, because typing it out feels cumbersome (I'm from C++)