more precisely, uniq produces output in the same order as the input to it, just collapsing runs / run-length encoding it

I know we haven't seen a human-written README or technical post on a company blog in maybe the last year on this site, but posts like this being at #1 are a reminder that we can still go lower.

Oh, I think there's still a long way to go before we reach the bottom.

> choice of ONE Linux distro

fwiw the asahi kernel and patches are usable from other distros just fine; i've done it on nixos in the past and the linked blog post shows some stuff running on gentoo

Sounds like a bunch of extra work and potential bugs/issues compared to “download iso, install iso”

how's the battery life / what's your usual workload

famously knuth was trying to (and pretty much did) solve digital typesetting not create a nice piece of hci so this is all as it should be or at least as might be expected

Staying in his lane, living his best life—dropping incredible things to humanity ever now and then. I had to check since I hadn’t thought about it for… a decade apparently, but looks like TAOCP 4B came out a couple years ago.

if only it were 10%

even the things you mention in your post paint a picture of a difference that for a lot of usage patterns is much more significant than just the last 10%

COPY is often a usable alternative.

> Expreg (teeesitter expand region)

reminds me of combobulate (which i haven't tried but think looks cool) but sounds much more light/limited

I think that is an accurate assessment! It's actually the reason I prefer it. I only wanted the ability to expand to treesitter text objects and then contract that selection if desired. I almost wrote it myself but then found that plug-in.

Slightly off topic here but do you (or anyone) happen to know how to get old Eglot behaviour back of showing entire types and parameter information instead of only the first line? It has been bugging me whole week and I cannot seem to find any fix for this.

Are you referring to the eldoc help text in the echo area at the bottom? Hard to know without more specifics, but maybe one thing to check might be the value of eldoc-echo-area-use-multiline-p. I have mine explicitly set to `nil` because I find the default eldoc behavior of constantly resizing the echo area to fit more information to be very distracting. I instead have a keybinding to call `eldoc` (an alias for `eldoc-print-current-symbol-info`) on demand, which opens a side split that shows the full symbol information.

Yes I am talking about the help text in echo area. In newer versions apparently they only show a single line by truncating the eldoc-doc-buffer content(not super sure on this but they do truncate to 1 line). eldoc-echo-area-use-multiline-p does not work for that sadly.

Apparently this was changed only recently. I am surprised not many people know/talk about this change. Still looking for a fix.

Edit: I do agree it is annoying but for unknown codebases it helped me a lot.

I also like to view entire doc even jumping. I created some Eglot additions here https://github.com/cxa/eaglet which have an option to enable this behavior if it would help.

one tiny famous painting from a cop-enforced distance of god knows how much while an enormous painting full of stuff stands right opposite it

I imagine the curators did this to entertain themselves. I thought it was a great juxtaposition when I visited.

oh, totally

what i intended to point out was that regrettably few people actually pay any attention to the nozze di cana despite it being both more accessible physically and worthy of interest

sometimes you just happen to be a mathematical object

Perhaps everyone is a mathematical object and I'm just a little more self-aware