as mentioned by (an) other comment(s), you should add Kakoune under text editors, perhaps with the text:
Kakoune
A modal terminal text editor based on Vi. Kakoune is based on selection before action and is committed to the unix Philosophy.
and when talking about descriptions, I don’t have a problem with the descriptions being subjective in tone, but could you remove the word “master race” from the Vim description ?
while I understand the history of using “master race” in tech related discussions, I think the nazi history overrules that by a long shot. Even if it didn’t have the history it did, the word emanates eugenics.
otherwise, I think it is a nice list and a good initiative :))
Well it’s there at least. Hmm. I don’t know a whole lot about windows but you can certainly get back to those boot options you saw before by pressing shift while booting, which will open the GRUB options. I’d give the windows boot manager another shot from there.
If that ends up working you can change the grub settings to wait for input instead of automatically booting pop. If that doesn’t work then something is probably wrong with windows and I would just try reinstalling since it sounds like you don’t have anything on there yet.
at this point i am considering uninstalling Pop and getting win10 first because linux actually has sensible ways to dual boot even on the same drive. that’s probably what i’ll have to do.
Apparently I’m wrong and Pop_Os uses systemD-boot not GRUB, which is surprising to me because unless things have changed I’ve always thought of systemD-boot as being underpowered for a lot of use cases.
this is indeed, pretty damn weird. I’m going to go with uninstalling pop os, and getting windows first on the smaller drive, then getting either KDE Neon or Linux Mint on the bigger one. kinda sucks, i wish i couldve just installed but it doesn’t seem like there is anything i can do. thank you so much for the help, comrade. rat-salute
I use rEFInd, which auto-detects my Windows boot partition. Though I had the Windows installation before the Linux one.
Systemd-boot should be able to detect a bootable Windows too. I don’t remember the specifics. It works out of the box on my laptop. Google “systemd Windows boot”.
Alternatively, maybe something went wrong with the Windows install and you nees to do the Windows repair USB stick thingy. Do you have a Windows recovery partition?
Ah I think Windows does this “helpful” thing where it installs its bootloader into the ESP of any drive if it’s already present rather than the drive you explicitly told it to install onto.
You didn’t have anything in it yet, right? Unplug all other drives and then re-install Windows onto the drive. It should work as expected after that.
IIRC Pop!_OS sets the systemd-boot timeout super short; you have to hold a key after the firmware is done or something to get to it reliably or simply increase the timeout (1s is enough, I have it set to that on my systems). systemd-boot should give you the option to boot any windows installation though, it can auto-detect them.
There is a niffty Boot manager called Refined. This is what I use even though I installed Windows after Linux and had many kernel panics, but it does the job well since it scans your boot drive every time you Power on your machine. Here is a link. Just download the CD-ROM version, put it in ventoy, boot from it, and the rest is easy. You already are a linux user, you can figure it out.
I also advise you to disable Windows updates if you can, and I mean all updates, because they can mess the boot order. If you use Windows to play games and games only.
Edit: You can also install it from your distro package manager if you can access your system.
My two cents; install uBlue’s Microsoft Surface Images. Here you can find the (WIP) documentation on how it differs from other uBlue images. I’m sure the following lines should pique your interest:
“Replaces the stock Fedora kernel with the Surface kernel
My personal take on what uBlue is, would be that it’s how Fedora would love to ship their Atomic variants if they could ship everything without worrying about those things they can’t (like hardware acceleration, codecs etc). Furthermore, uBlue even has device-specific images; which is just fantastic if you happen to own such a device.
Last, but definitely not least; it’s the best platform in which the transition to Ostree Native Container has been realized. As such, this allows some very unique ways to maintain a distro. For example; if something broke (for whatever reason) on vanilla Fedora Atomic, then… well, you (the uBlue-user) wouldn’t even have noticed it. Because that breakage simply never hit your device. Instead, uBlue’s maintainers noticed the issue -> somehow applied changes to the image so that the image doesn’t ship the issue (by either not shipping the breakage inducing update of the specific package or by shipping the workaround/fix with the image) -> the very next time you update your system (which happens automatically in the background by default) you just go on with your life as if nothing had happened in the first place 😅. So, in a sense, your system is managed such that breaking changes/updates don’t hit you; while they do hit non-uBlue users.
And I haven’t even touched upon how uBlue enhances tinkering or how it allows one to manage (a fleet of) self-customized images etc.
https://github.com/babarot/gomi - replacement for the rm command that has a trashcan, so if you accidentally delete something important you can just restore it
Also, I think you should add a note that ranger should be installed from git because most distros package version 1.9.3 and that is 4 year out of date and has lots of bugs that have been fixed in the git master branch
woops my bad, I mean to link this github.com/…/wayland-x11-compat-protocols it’s a repo of going to be protocols, to fill in the gap instead of pretending the issue doesn’t exist
I did and quite frankly it’s trash, XDG portals are a clunky and quite frankly terrible and poorly thought out api. I’m not the only one that disagrees with this sentiment as multiple people are trying to get protocols like ext-screencopy-v1 for screen recording and ext-foreign-toplevel-* for window management upstreamed into wayland so that xdg portals aren’t necessary for these use cases. I don’t mind the reliance on pipewire too much, but I too think that It shouldn’t be necessary for screen capture.
IMO It is one of nate’s worst takes of all time if not the worst. Usually I agree with most things he writes, but not this, xdg-portals is a travesty, pipewire is nice and all, but I don’t see why we should need an entire media system for basic screen capture capabilities. and clearly im not alone on this sentiment
And that’ll shake out in the time it takes for X11 to go away. I get what you’re saying, although I don’t share your opinion about portals from a user perspective: I’m just happy that Firefox finally uses the Plasma file picker.
I have a couple of issues with portals. One is that we’re putting too much eggs in the basket of something that is designed for containers. XDG portals Have rejected features that people have requested because they don’t want to expose that functionality to a container and they are allergic to permission prompts apparently.
I also have other issues with the portals for instance video capture. It requires you to have a camera portal. It requires you to have a desktop capture portal. It also requires you to have an app to app, video, portal, which doesn’t exist yet. All of these things require pipewire pretty much in most cases, so why can’t we just have a single pipewire portal? It may not scale well in the future, but it doesn’t scale well now anyways. If you want just a generic pipe wire stream, you’re not gonna be able to have it, you’re going to have to conform to one of the standards anyways. For a case in point example, the OBS pull request for Game Scope Capture is the perfect example of this over reliance in XDG portals.
I’m showcasing this just to highlight the fact that the XDG portals are incredibly poorly thought out, and I don’t think that it’s a reliable method for the future going forwards.
PS. Please pardon any oddities in this, I had to use speech to text, since my RSI is acting up.
I think having separate standard APIs for screenshots, screen capture, and video capture that aren’t married to one implementation makes sense.
I partially agree about the focus on containers/sandboxes. Yes, it makes sense to criticize that something designed for a different use case results in different trade-offs. But on the other hand, are the use cases really that different? We’re talking about standalone desktop apps, they need some common building blocks no matter if they’re containerized or not, right?
Otherwise I don’t know enough about the standards to comment there, you’re probably right!
I think having separate standard APIs for screenshots, screen capture, and video capture that aren’t married to one implementation makes sense.
The idea of a using a separate thing for it is fine, in itself, but necessitating it is an issue to me. There are a LOT of wayland compositors now, for all sorts of systems, each one also new needs a compatible xdg portals implementation (or whatever third party tool you like), in the case of xdg portals this also means pulling in things like dbus. It actually becomes a lot to build a “Minimal but fledged out” ecosystem. something which should otherwise be possible.
we’re talking about standalone desktop apps, they need some common building blocks no matter if they’re containerized or not, right?
sure but then you have xdg-portals denying actually useful a11y protocols because they “don’t want to expose it to containers” -_- apparently they never heard of a permissions system? but this also highlights why the wayland ecosystem right now is so poor for select individuals (and why they get heated when told that they need to swap to wayland)
I don’t like the idea of configuring pm (or anything else) using a programming language. So I would try nix first if I feel that I need it. However I don’t.
The ultimate output of Nix is one set of data, usually the description of a derivation (~= package). You cannot cause arbitrary side-effects with it like writing to files or making network requests with it.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.