- > What were you expecting? That your character ranges in ls would match mine?
I would expect the command to work in any directory. Try a few different directories on your computer and you'll see that it won't work in some of them.
- This is what I get:
ls -l | cut -c 35-41 6 Nov 1 6 Nov 6 Nov 1 6 Nov 1 - Can these flags be used to extract the N-th column (say, the size) of every line from ls -l output?
- > That’s typical usage of Awk, where you use it in place of cut because you can’t be bothered to remember the right flags for cut.
Even you remember the flags, cut(1) will not be able to handle ls -l. And any command that uses spaces for aligning the text into fixed-width columns.
Unlike awk(1), cut(1) only works with delimiters that are a single character. Meaning, a run of spaces will be treated like several empty fields. And, depending on factors you don't control, every line will have different number of fields in it, and the data you need to extract will be in a different field.
You can either switch to awk(1), because its default field separator treats runs of spaces as one, or squeeze them with tr(1) first:
ls -l | tr -s' ' | cut -d' ' -f3 - > once you develop a good enough utility library for it.
What happens when everybody comes to the job with their own utility library and start working on the same codebase?
Would you like it if you had to get up to speed with several utility libraries your coworkers developed for themselves?
A common set of tools, like the Unix commands, makes it easier for people to collaborate. They were put in an official standard for a reason.
- The 2 minutes wasted to write it doesn't move the needle, but the time that their present and future teammates will waste on reading it might.
It costs me more effort to read and understand a screenful of unfamiliar code than the equivalent "sort -k 1.1" or "uniq" while skimming through a shell script. This adds up.
- I think touch screen itself limits the possibilities to create UIs usable with minimum attention. You have to look at it to find the right area to press. All those buttons, knobs, sliders, etc., imitate the real thing, but only in 2D. Can't rely on feeling to find the right control, unlike with physical designs.
It's not the only culprit, of course. There's still room to at least design a layout that is predictable, and with buttons that are easily reachable.
Some UIs make me think the designer was an alien invader in a human body. It thinks nobody can tell, but when it designs a UI that can only be called "intuitive" if you have 7 fingers, the 2-nd and 5-th longer than the others, and the 3-rd one a tentacle... I got you, motherfucker!
- The top comment is hilarious:
> The next Ubuntu release will be called Grateful Guinea-Pig
- This reminds me of ClearCase and its MVFS.
Builds were audited by somehow intercepting things like open(2) and getenv(3) invoked by a compiler or similar tool, and each produced object had an associated record listing the full path to the tool that produced it, its accurate dependencies (exact versions), and environment variables that were actually used. Anything that could affect the reproducibility was captured.
If an object was about to be built with the exact same circumstances as those in an existing record, the old object was reused, or "winked-in", as they called it.
It also provided versioning at filesystem level, so one could write something like file.c@@/trunk/branch/subbranch/3 and use it with any program without having to run a VCS client. The version part of the "filename" was seen as regular subdirectories, so you could autocomplete it even with ancient shells (I used it on Solaris).
- How? Readline macros?
- > If it happens a second time? A stern talk from their manager.
In my experience, the stern talk would probably go to you, for making the problem visible. The manager wouldn't want their manager to hear of any problems in the team. Makes them look bad, and probably lose on bonuses.
Happened to me often enough. What you described I would call a lucky exception.
- "Trunk" was the default in multiple VCSes before git arrived.
- > SML [...] appears to idiomatically represent them as functions of a single tuple parameter
Tuple is not special, though. Functions accept a single argument of any type.
To use the argument in the function body you can name it, or you can use any valid pattern to destructure it and bind parts of it to local variables.
Tuple is just one of the valid patterns. Coincidentally, it looks like argument list with positional arguments in many other languages. You can also use a record, which makes it look like "keyword arguments". You can also use patterns of custom types.
All the above is still about the single "argument" case, the single value that is "physically" passed to the function. Pattern matching is what makes it possible to bind parts of that value to multiple local variables in the body of the function.
- > that roadmap is also not accessible to screen readers
It also has terrible navigation on mobile, even for sighted users. I gave up after a few seconds of trying to use it.
alias grep='grep --exclude-dir .\* --exclude .\*' grep -r --include \*.foo bar- Maybe git-bug[1]?
- > Though most of the software do the right thing by checking if the standard output is an actual tty (isatty) to avoid colors when redirecting to something else (e.g. socket, fifo, etc).
NO_COLOR is orthogonal to the isatty suppression.
NO_COLOR ensures that colors are off even when stdout is not redirected.
For example, when you have poor vision, poor quality display, or sit near a window, (or worse – a combination of these) the colored parts of the output might have lower contrast, low enough to make them impossible to read.
- I think by "Bluesky services" PP meant atproto services, like PDS. Not social networks.
- Tinfoil Chat does that (and more).
- > not an amazing user experience to have to share a random string to your friends
It doesn't have to be that way, at least in theory.
They can nerf accounts without verified phone numbers to be unable to reach verified accounts. And delete idle unverified accounts sooner, to combat potential DOS.
People who believe their phone number will be used to deanonymize them, can just use an account they keep unverified, and exchange IDs via other channels. It's harder, but for these people it will be worth it.
The rest of us can verify our phone numbers, and enjoy the easy discovery. (The way it is now.)
Machine-created, unverified, spam accounts will have to brute-force address space way bigger than that of phone numbers, and still only be able to reach other spam accounts, or an occasional very privacy-sensitive user.
I have no idea whether the above is technically possible, though.
- INSTALL is also a standard location, for the commands that are related to building and installing the software.
- "Miscommunication" is a very charitable interpretation.
For certain people, this behavior is a pattern. You give them an inch, they take a mile.
- You can get pretty far with software-only tweaks to your existing keyboard instead.
I've settled on keyd[1], after using XKB and interception-tools for a while.
- Governments are more scared of "online", because their shenanigans could be exposed instantly, and to many more people than with the "tech" available before (speaking in person, or paper letters).
Freedom to speak in person is like a fist; freedom to post online is like a gun. They don't want us to have guns, obviously.
- > But Ghostty is competitive in all three categories
Being at the bottom is not what I call competitive.
- Do you mean that it should be invoked exactly as "systemctl ps", for convenience?
I think the functionality is already there:
systemctl --type=service --state=running - > Also if your visa allows back-to-back entries that's exactly what I'll do. Nowhere does it say that there's a limit, therefore it's not "abuse".
Also if the law says you should pay taxes, that's exactly what you should do. Nowhere does it say that there's an exemption for people paying their food and rent ("injecting" $500), therefore you should pay (taxes).
If it's too long, it gets truncated, though.