I’m here to stay.
It’s still not full CMYK. Only import and export gets true CMYK support, and editing is still RGB (but with CMYK print preview). They said full support is planned for the future, as they have too much to worry about at the moment. With 3.0 they lay the ground for future features.
Actually isn’t a Regular Expression, because the star operator * requires a preceding character or object to apply to. This is a wildcard for the shell style globbing, where a single star doesn’t require a second object.
I want to use Glim too, because the binary Blobs in Ventoy are bugging me a lot. But Glim is a bit limited still: README
My experience has been that the safest filesystem to use is FAT32 (surprisingly!), though it will mean that ISO images greater than 4GB won’t be supported. Other filesystems supported by GRUB2 also work, such as ext3/ext4, NTFS and exFAT, but the boot of the distributions must also support it, which isn’t the case for many with NTFS (Ubuntu does, Fedora doesn’t) and exFAT (Ubuntu doesn’t, Fedora does). So FAT32 stays the safe bet.
Those are two completely different programs. balencaEtcher is for flashing an ISO to the USB stick. Basically its like installing an operating system on your hard drive, but it installs it on the USB drive. It will make it bootable. If you want a different OS, you have to completely flash the drive and replace whats there.
Ventoy will also make the USB stick bootable, but it will not flash an operating system onto it. It’s more like a general launcher of ISO files. This means, you only install Ventoy once and then can drag and drop ISO files to a folder. If you boot Ventoy from USB stick, it will show a list of all available ISO files. Choose one and it boots into the distribution, like you would have flashed it with balencaEtcher.
The advantage of Ventoy is clear: Easy replaceable ISO files and having many to choose from withing a single installation. Filenames of ISOs doesn’t matter and they can be placed in sub directories in the ISO folder I think. Ventoy will just list all available ISOs you can choose and boot into. The disadvantage is, that some distributions or hardware might not work well with Ventoy, but that’s not my experience so far.
Here is a little bonus to have in mind: You can convert newline characters to null, then grep with option null, and at last convert null characters back to newline. Now I don’t think its useful in this case, but its good to know; therefore its a bonus information:
ps aux | tr '\n' '\0' | \grep --null-data ^root | tr '\0' '\n'
If I do ps aux | grep root, then the newline is preserved. So I’m not sure what exactly the problem is. There is a user option for ps, but it does not work with aux, ps --user root . You can ps ax --user root, but I’m not sure if this output is what you want.
Btw if you grep, then I recommend using ^user , so it only matches the beginning of each line (the actual username), as ps aux | \grep ^root (notice the backslash). Do you have an alias for grep? Try \grep instead. The backslash in front of the command will use the actual command and ignore your alias.
Redditors maybe?
I see. Well then my bad for misunderstanding this. To me moderators are Reddit staff working for free. But I see that the word “staff” was used literally.
See you in the oblivion. xD
In other news, grass is green.
I didn’t saw this news. My news only tell me that the rice bag fall over. It happens over and over again. Predictable, like Reddit.
Reddit is giving its staff a lot more power over the communities on its platform. Starting today, Reddit moderators will not be able to change if their subreddit is public or private without first submitting a request to a Reddit admin.
More power by having less power. I stopped reading here. Yeah, The Verge never disappoints. Edit: My bad. The Verge was correct this time. Guess if I read the article then I would understand.
grep by default uses Basic Regular Expressions. This means the ( and ) lose their special meaning and are matched literally. Either use a backslash version \( to have a group, or use Extended Regular Expressions with -E "(IN|OUT)" . In man grep under REGULAR EXPRESSIONS are some differences noted.
Nice. I assume it make sense, because the skins are all the same, just different styling for colors and images. Good to know (for future recommendations).
Audacious has a classic Winamp skin: https://store.kde.org/p/1008329/ (Note, I don’t use this program and cannot assist further.)
I fear these kind of mistakes will happen much more frequently in the future; thanks to AI tools.
Because Linux is just a kernel.
This is too short. Here is the long form: https://www.gnu.org/gnu/incorrect-quotation.en.html
I’d just like to interject for a moment. What you’re referring to as Linux, is in fact, GNU/Linux, or as I’ve recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX.
I like these self made scripts. Some ideas to improve this: a) instead ls, use find command if you want use its output as input in another program (will yield fullpath too), b) fzf has a preview functionality, which I like a lot to use when it comes to directories or script files. As for the run command, I’m not sure why you use xargs and what i3-msg is needed for. Here is an alternative way.
(Edit: I always forget that beehaw will convert my ampersand to &. Have this in mind if you read the below code.)
bash -c 'cd "${HOME}/.local/bin"; path="$(find . -maxdepth 1 -type f -executable -printf "%f\n" | fzf --preview "cat {}")" && "${path}"'
below same command in a bit more readable standalone script:
#!/usr/bin/env bash
cd "${HOME}/.local/bin" || exit 1
path="$( \
find . -maxdepth 1 -type f -executable -printf "%f\n" | \
fzf --preview "cat {}" \
)" && "${path}"
The biggest problem with fzf is, that scripts that need an argument are not covered here. One could either use the input string from fzf as arguments or like that, or an optional input after fzf selection.
I might be missing something here but I don’t know how other launchers could possibly make this a simpler process.
Shortcuts to launch an app directly in example. So my keyboard becomes my launcher.
I use bunch of different tools, including KRunner (on KDE) and previously Rofi. These type name and search tools for launching an app have the problem that you need to remember what name the tool was. For programs I use often this is not an issue, but not all applications have names good to remember and not all of them are used often. The associated description helps, but sometimes I don’t know what words to type.
Therefore I “need” the app menu with categories and favorites, to navigate with the mouse through. And the most used applications are usually assigned to a shortcut and my panel on the top. In short I use mostly all of these techniques as an application launcher (in that order):
Edit: Forgot to mention that some of the launchers I use are custom made scripts for the terminal.
haha in fact I was thinking of installing Windows 95 instead, because I wasn’t sure if Win 98 was too new. xD Its all just to play games.
I hope too, because there are plans post v3.0: https://developer.gimp.org/core/roadmap/