sixdripb 4 months ago • 100%
yeah, the firefox situation is indeed still confusing. you make a good point. deleting the stock one and installing the flathub one + ffmpeg-full(flatpak) seems the most straight forward solution for hardware decoding. but as you said still fairly confusing.
I do still think ublue is more confusing to understand, personally
sixdripb 4 months ago • 100%
nope, since fedora 38 this button enables full access to flathub. it also lets you install proprietary nvidia drivers from gnome-software with one click. hardware decoding via ffmpeg also works for flathub apps that require it.
sixdripb 5 months ago • 66%
uhh on fedora just enable third party repos during initial setup and you’re good. its insanely easy
sixdripb 5 months ago • 100%
the article was based on the workstation release
sixdripb 5 months ago • 100%
no problem at all, I will try to get it in whenever it is solved, I’m in no hurry :) thx
sixdripb 5 months ago • 100%
aw I missed the release. maybe we can get it in for the fall release. ( personally I would prefer to get it in under the right license, than in a new one or in a grey-area). thanks for reaching out back then, it would be crazy to me if people had access to this icon in neovim etc.
Linux Gaming
Mangohud randomly stopped working with Steam Flatpak
sixdripb 6 months ago • 100%
same experience, thank you for asking
I could not understand if I messed something up myself or not
sixdripb 6 months ago • 100%
@hasecilu@lemm.ee I will wait for the license issue to resolve, seems better?
sixdripb 6 months ago • 100%
oh yea that would be cool, let me see if i can do it
sixdripb 6 months ago • 100%
aw ok.. you never know ig heh
sixdripb 7 months ago • 100%
thankyou! btw, since you're a billion dollar corp can you send me a check? cheers
sixdripb 7 months ago • 100%
hell no, full tux is the best, these are just simplified icons. but thanks for the compliment!!
sixdripb 7 months ago • 100%
he won't stop me.. (e: /s)
sixdripb 7 months ago • 100%
thank you, the build-your-own thing is great, i have chosen the CC BY-SA 4.0.
sixdripb 7 months ago • 100%
thank you for pointing me to this, i have choosen this license and added it.
thank you also @RmDebArc_5@lemmy.ml
sixdripb 7 months ago • 100%
i did go overkill with the simplification, so its easy to see other things. but at small sizes i feel it works better.
https://gitlab.com/sxwpb/minimal-tux-icons These are only meant to help for cases where the full tux is too detailed to display, see examples in the linked README. But the shape also works well for single fill cases, like in the keychain example. I wouldn't want these to be used when the full tux could be displayed in all its glory instead. ~~One issue I have is I do not know how to license these properly, I wouldn't want them to show up in a trademarked logo or anything, but I would still want them to be freely usable as tux icons anywhere. What do you think?~~ I have chosen the [CC BY-SA 4.0](https://creativecommons.org/licenses/by-sa/4.0/?ref=chooser-v1) license, thank you for helping me!
Hello all, as someone who mainly prefers dark themes but also enjoys black text, I created this semi-light neovim color scheme. https://gitlab.com/sxwpb/halfspace.nvim The goal was having a theme that uses black text but avoids the eye melting of most light themes. In fact the background color is #808080, which is the midpoint of a monitors brightness. Using such a background comes at a hefty cost of text contrast, thus all chosen syntax colors are kept pretty close to the best possible contrast here which is black text. Let me know what you think and I know lots of people absolutely despise this type of color combination which I understand, so please be kind in that case. happy vimming
sixdripb 9 months ago • 100%
hmm have you tried to restart your shell after installing debugpy?
if running lua= vim.fn.exepath('debugpy-adapter') from nvim command mode doesn't return the path, something prob went wrong with your debugpy install, as neovim can't see the adapter. maybe try reinstalling debugpy from mason, quit nvim and reopen it in a new shell and see if can detect it.