eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

225
active users

#less

0 posts0 participants0 posts today

Linux tip: you can edit files from within less by pressing "v". This will launch your default editor.

If you do not have a default editor specified, you can specify one by adding the following lines to your .bashrc:

# set default editor
EDITOR=/usr/bin/vim

Substitute vim for whatever editor you prefer. (Which is obviously vim :)

#Linux#Bash#vim

(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."

The #MastoPrompt for Thursday 5 December 2024 is:

#less

The poem or story can include the prompt word or be about the prompt word.

@ me, if you like, or just include the #MastoPrompt tag (to allow people to follow or filter their feeds), or keep your work to yourself - all the options are good as long as you're writing.

If you're including an image please do include alt-text so I can boost your post.
#Writing
#SmallPoem
#Poetry
#Fiction
#MicroFiction
#SmallStories

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?