Rok so i thought i had figured out that installing lunarvim would be actually pretty basic:
brew install neovim
KDid you disable Bitlocker?
Ri'm not supposed to be installing stuff outside of distroboxes?
Kif Bitlocker is on you won't be able to repartition
Rbut all these neovim plugins want to do their own little things
Rshould i just install lunarvim into a distrobox ? will it be available to me in the base system ?
LYes bitlocker is off , I already disabled fast boot for windows
Kwell those two things aren't the same, but I'll assume you mean you did both.
LAnd like the video mention I shrunk the partition of my 4 tb ssd and I gave it 1 tb unallotment
LYes I did both
KI haven't watched the video, I don't own an Ally X. I just had bitlocker issues installing on an OG Ally so figured I'd mention it in case it was possibly the problem you had. Since it isn't, I've got nothing further. Hopefully someone else has some ideas.
DWin or command I guess
Rmeta/super/win/command sigh
Rterrible
Pif you package needs strict system integration you should just layer it no other way around, otherwise you can probably be fine doing it containers
Players are last resort
Palso it is a good idea to have all you dev enviroments in separate containers anyway
Ri use lvim in all my dev environments
Rwould i install lvim in each
L@Pryka do I need flash a new usb you think , I can’t think of any other ideas
Pdepends on your workflow tbh
LAlso when I partition the ssd I didn’t do a new efi
Pi like to keep python stuff and crates with rust separate and so on
Rneovim is a brew install would i install neovim in each to then add the lunarvim distro
Rthe containers can't see the neovim on the host right?
Pi would just setup neovim and lunarvim in container
Rthen do i have to be in the container to use lunarvim?
Pyou can export it to use outside
Rso i should uninstall neovim from brew ?
Pprobably, yeah
Rpytxis just crashed again
Psorry I never done it in that way, dual boot I mean.
PI have separate drives
Pfor immutable dualboot
THey guys?
TI got a weird error when installing Bazzite
Kcan't hurt to try. also confirm md5sums
TThe following error occurred while installing the payload. This is a fatal error and installation will be aborted.
The command
The command
ostree container image deploy --sysroot=/mnt/sysimage--image=/run/install/repo/bazzite-nvidia-stable --transport=oci --no-signature-verification exited with the code 1
PYouTubeMike's Tech Tips
In this guide we'll be removing the invalid fedora entry in the efi partition to get Bazzite and other atomic desktops to install after attempting to reinstall them. (fixed the audio)
Edit: Note that you might also get this error if you previously installed Fedora workstation or Nobara and you have kept your existing efi partition on the disk.
...
Edit: Note that you might also get this error if you previously installed Fedora workstation or Nobara and you have kept your existing efi partition on the disk.
...
Ptry this if you have fedora silverblue or another atomic fedora desktop before
Ttried Bazzite
PYeah but it was installed before?
PTry this tip from video, no harm anyway
Tnever
Tlet me re do the usb stick if not then will try again
Rok so i think the disconnect i'm having is thinking of the base system as my cli environment
Ri should just make a distrobox and do everything in that and use the base system to manage the base system
Rbut will i be able to access the container from gui apps installed with flatpak
KDepends on what you're doing
Kdistrobox enter box -- hello is as good as hello