launcher VS mustang

That's why in Gnome, you need a shell extension instead of an app. Shell extensions are written specifically for Gnome, and the documentation sucks, so immediately you have way fewer options. BUT, guess what: PoP OS launcher is a Gnome shell extension (which is why it worked for you), and you can use that in any distro using Gnome, including Fedora. However, it is that it's part of pop-shell, so you also get the other UI customizations (mostly keyboard shortcuts for tiling that you can disable I think). It also requires setting up the back-end service to handle the non-ui side. Maybe there are Fedora packages for it that makes it easier (I don't use Fedora myself, so wouldn't know).

I might take a look at that. Is this the right repo?

Just to be clear, you are talking about the Pop Launcher and not the Cosmic Applications Launcher, correct? (since there may be some confusion around what the "Pop Launcher" is vs. the "Cosmic Applications Launcher" ... see https://imgur.com/a/XN34drv for images)

pop-launcher

This feature has been merged but not yet released: https://github.com/pop-os/launcher/issues/152

Pop launcher github: https://github.com/pop-os/launcher

You can open any website in your default browser using the "www" pattern, e.g. "www reddit.com" (note, no "." after the "www") github

You can get pop-shell and pop-launcher in fedora.

The last improvement was feat(service): prefer recently/often used applications in search which may have caused this.

In the cosmic launcher I use the plugin "recent" to open recent files. I would like to have a shorter keyword for this, like "fr" (for find recent). What is the best way to do this? I have looked at the readme for pop-os/launcher, but copying the system recent plugin to a new one at ~/.local/share/pop-launcher/plugins/fr doesn't work, and breaks the system version. When I remove ~/.local/share/pop-launcher/plugins/fr, then the system version starts working again.

It would be great for Rust to have a Linux target that doesn't use libc, but from what I've read, not many people are interested in this.

Found this as well: https://github.com/sunfishcode/mustang

Some discussion here: https://github.com/bytecodealliance/rustix/issues/76

On Linux there has been some attempts to get exactly this solutions, most notibly https://github.com/sunfishcode/mustang but the topic did not seem to fetch a prominent position on the supported feature list.

For Linux, Mustang already exists because Linux has a stable syscall API

Why bother with a libc at all, when you can skip it entirely on Linux!

Mustang is a project which is able to run some non-trivial programs written in Rust, such as ripgrep, without using any libc, on Linux.

Mustang is one way to take care of the tiny amount of "C" that runs before main().

This is more a Rust question than a Zig question. In Rust, the choice of a specific libc (or to not use a libc) is part of the "target", for example many hardware platforms have gnu/musl/none targets. See also relibc or mustang for pure-rust alternatives. Each libc alternative require some work to integrate into Rust.

There's a separate project for that, called Mustang. It's built on top of rustix and provides all those things. It's not super mature yet, but it is able to run ripgrep by itself: https://github.com/sunfishcode/mustang