lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

66
active users

#less

0 posts0 participants0 posts today

(Possibly relevant to @b0rk 's interests)

So I hit a flag in diff, --unchanged-group-format. It does not show up in the manpage. It does not show up in --help. You can search both those channels for that string and you will not find it.

You know where it shows up first? If you Google it, you'll get an example in gnu.org/software/diffutils/man.

So why doesn't it show up in the manpage? Well, it does! If you read the entire manpage. With your eyes.

  -D, --ifdef=NAME                output merged file with '#ifdef NAME' diffs                                                                                                                                                                                                                                                                                                              
--GTYPE-group-format=GFMT format GTYPE input groups with GFMT
--line-format=LFMT format all input lines with LFMT
--LTYPE-line-format=LFMT format LTYPE input lines with LFMT
These format options provide fine-grained control over the output
of diff, generalizing -D/--ifdef.
LTYPE is 'old', 'new', or 'unchanged'. GTYPE is LTYPE or 'changed'.

"What do you mean it isn't documented? Of course it's documented. You did read every line and do some template-substitution in your brain, didn't you?"

This isn't advocating for not reading the manpage. If you really want to understand how the tool works, you read the whole manpage. And probably the source code. 😉

... but I don't want to understand how the tool works. I want to diff two files and not have the lines that are the same get emitted.

And I think a lot of application- and solution-generating computer people, most of the time, in most of their careers, are operating on that level of depth. Problems come in too fast and with too much variety. You absolutely go deep on some things. There is no time to go deep on everything.

So how do we address this (other than throw up our hands and say "Relying on Google's fuzzy search of the whole Internet and vibe-coding LLMs is the future actually")? I don't have magic bullets, but a "fuzzy search" mode in something like less that could take an input like --unchanged-group-format and twig that it if there's no exact match, it might be related to --GTYPE-group-format would be nice.

Maybe I should mock that up in emacs. Actually, I bet someone already put it in emacs. ;)

www.gnu.orgLine Group Formats (Comparing and Merging Files)Line Group Formats (Comparing and Merging Files)

‘We’re going to sell Grandad’s old house,’ Dad said.

‘No! It’s so much fun there!’ Cherry complained.

‘And Mum grew up there!’ Apple chimed in.

‘We don’t need another house. And where we live is more practical,’ Dad explained.

‘But there’s #less room to play here! Grandad’s house has a big backyard.’ Cherry insisted.

‘There’s also the magic woods out beyond the yard,’ Apple added.

‘Apple, don’t put ideas in your sister’s head. There’s no magic woods,’ Dad said sternly.

‘Well, actually...’ Mum’s eyes lit up.

With the sound of pursuit approaching, they reined in at a fork in the trail.

"Which way?" asked the barbarian.

The rogue pointed left. "This one. #Less of them'll follow."

"That's wrong," snapped the seer.

"Okay, you should know." The barbarian trotted right.

The rogue glanced at his remaining companion with suspicion. "Why was I wrong?"

"You meant 'fewer', is why."

Any people on here who have both experience with #ddd + #teamtopologies and #less or #fast?

It feels that stream-aligned teams and the fluid teams is a big conflict? And I'm wondering what kind of tradeoffs you've found when working with one or the other?

For example, how do devs build deep domain expertise in fluid teams?

Or if you do TeamToplogies, does it always mean that you might need to rework your architecture so teams can work on value and not just on individual components?

Elon Musk’s charity may bear his name, but it can’t seem to match his penchant for high-dollar spending.

According to a New York Times analysis of his charity’s giving in 2022, the #Musk #Foundation gave out just $160 million in grants
—a whopping $234 million #less #than the five-percent #legal #minimum it needed to distribute between 2021 and 2022.

It was the fourth-largest shortfall of any U.S. charity in 2022, the last year for which records are available.

The revelation was one of multiple in the Times’ report on Musk’s charitable giving, which has often benefited his own associates or those of his companies.

Musk reportedly filled some of the foundation’s coffers by donating Tesla stock, which he is allowed to claim as a tax deduction.

Not all of the charity’s donations have benefited his own interests, however:
The foundation donated more than $1 million to schools in Flint, Michigan, and a charity aimed at helping children there.

But where that foundation donates is still up to him and the foundation’s board—which includes just him and two other volunteers.

thedailybeast.com/elon-musks-c

The Daily Beast · Elon Musk’s Charity Often Benefits Elon Musk and Associates: ReportBy Corbin Bolies

I spent the last three days cleaning up and refactoring one of DokuWiki's core dependencies - the LESS compiler:
github.com/splitbrain/lesserph

It will probably take a few more days before it can be swapped in.

Personally I would love switching from #LESS to #SCSS but doing that without breaking hundreds of plugins and templates isn't easily done.

Maybe we can skip using a pre-processor completely in the future when #CSS nesting is approved and in major browsers...

GitHubGitHub - splitbrain/lesserphp: LESS compiler written in PHPLESS compiler written in PHP. Contribute to splitbrain/lesserphp development by creating an account on GitHub.

Pro tip: `less` can filter the lines it displays. Hit the “&” key and enter a search pattern. You’ll only see lines matching the pattern.

Want to only see lines that _don’t_ match the pattern? Prefix the pattern with an exclamation mark.

Super useful when looking at logs, for example.

The #less man page is definitely worth a read, it can do a bunch more stuff you might find interesting.

I'm in the middle of a small refactor in the frontend for a project I maintain. Just found out the size of font-awesome (54KB CSS + 2MB+ in fonts) while we only use **five** icons. I don't know a way of shrinking it to only the icons we need without doing it manually (which is a hassle for me and for everyone that would come after me). Anyone knows an easier way of doing this or an alternative font that provides it? #css #less #frontend #fontawesome