ash (and its successor dash found on other distros) is a POSIX-y shell rather than a sh clone, so it has all(? most?) of the POSIX feature set, whose syntax may indeed have been 'borrowed' from shells that came later than sh.
Not sure if there's a "parent" from which both ash and bash inherit the syntax or whether bash is the true source, but that doesn't really matter here.
All that said, it's worth checking to see if your system has a command on the PATH called [[. That has been one way that [[ support can be added to a system when the shell itself might not support it. Note that command names don't have to be alphanumeric like functions tend to be in a programming language (or other languages if you consider that the shell can be used for programming too), so [[ is perfectly valid!
If the underlying filesystem changes, say a copy operation, the file manager view does not update without a manual refresh by CTL+R. This leaves the view in a stale state, presenting false file information to the user, who might never know until they do something bad. This is a showstopper bug that’s been hanging around since forever.
I don’t know what you mean. If a open my Downloads folder and then download something, it shows up in Nautilus without refreshing anything
Batch rename. Good luck trying to rename a series of files ordered sequentially by number, if the number happens to start with any number other than one. A sequence from 2 to x is impossible to batch rename. Because regex in sed never worked either. No, wait. It’s always worked! For like, 50 years.
I mean at least there is a batch rename function unlike in windows
Why, when moving a collection of files or a directory within the same filesystem, does it actually perform a copy and delete operation, taking cpu and time, when the inode location could just be updated like mv does?
Again, I can’t reproduce it. I can move many GB instantly using ctrl + x and ctrl + v
The only thing that really annoys me with Nautilus is that you can’t type in the directory path you want to open except using ctrl + L. In the hamburger menu there even is an option to copy the path. Why not make one more to edit it? Or replace copy with edit, because when editing you can also copy it anyway
Having one program (process) talk to another is dangerous. Think of a stranger trying to come over to me and deliver a message. There’s no way I can guarantee that he isn’t planning to stab me as soon as he sees me.
That’s why we have special mechanisms for programs talking to other programs. Instead of having the stranger deliver the message directly to me, our mutual friend Bob (IPC Library, binder in this case) acts as an intermediary. This way at least I can’t be “directly” stabbed.
What’s preventing the stranger from convincing Bob to stab me? Not much (except for Bob’s own ethics/programming)
To work around this, we have designed programming languages (rust) that don’t work if there’s a possibility of it being corrupted (I would add “at least superficially”, but that’s not the main topic here). Bob was trained by the CIA in anti-brainwashing techniques. It’s really hard to convince Bob to stab me. That’s why it’s such a big deal. We now have a way of delivering messages between two programs that is much safer than before.
The only problem is that the CIA anti-brainwashing techniques (rust) tend to make people slow. So we deliver messages less efficiently than before. Good news is in this case we managed to make Bob almost as fast as before, so we don’t lose our own much while gaining additional security. The people who checked on Bob even made sure to have Bob do the exact same thing as before when delivering messages (using RB Trees), hence this evidence is most likely credible.
KDE gang rise up! Can’t stand GNOME and its design philosophy, in recent times it seems like it’s been trying its hardest to become the most off-brand macOS it can possibly be. Everywhere I look its more form over function. Urgh.
As a long time Linux user, if kernel broke anything for me, and it used to fairly regularly, I would just roll back to previous kernel. Fedora makes it easy, by default you can just boot into previous version by selecting it in grub menu.
File a bug, roll back, keep the bug report subscribed and only update after it’s fixed.
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.