Deleting the bottles directories from the repos directory seems to fix it, thanks for the advice!

Update: Following your advice, I proceeded to delete the files for “bottles” from the repo folder in /var/lib/… and that seems to solve the issue! thanks for the help! :)

thanks for the tip about storage space, although I do seem to have 100 GB of free space so I do not think this is the issue?

However I noticed I have a filesystem /run/user/1000 it seems to be created by flatpak, and it has 1.6 GB of total space. Should this be a source of worry?

The other advice about deleting the directories does not seem to work either :(

I have not found any that match the criteria I mentioned.

Just to summarize it better, I want something that has:

• vim-like philosophy of editing, with keybindings, motions and the like
• does not struggle with supporting RTL languages like Arabic (the terminal world struggles with that unfortunately)
• allows rich formatting, such as using non-monospaced fonts, and having the possibility to make different rows of text have different sizes (such as headings being bigger)

tbh if I can find something with only the first two, I can sacrifice the third one. But I still can’t find anything like that.

Thanks for the pointers!

You might hit some challenges like how to handle style elements. For example:

<cursor>*bold*

Moving the cursor to the right of the b will take two key presses in nvim but would typically be one key press in a WYSIWYG editor.

I’ve thought about this actually, and Youre right it will require some handling. In the first version of the editor, I will still include the special characters, such as the * for bolding. But I will also style it and what’s after as bold.

I really like the render-markdown plugin, but my deal breaker was RTL language, since Arabic is a native language to me that I wish to write in vim.

what do screen recording softwares for wayland use under the hood then?

does OBS just do everything with ffmpeg, or does it introduce extra functionality?

You can do it for xmpp and Jitsi right?

So there is no way with Rsync (under ssh) to set settings (config file or other) that will apply to all clients !!??
So it’s the client that configure rsync and the server !? there is no way around ?!

You basically want to use the daemon but under ssh. I looked into this before, and I think it is possible but the command for it is weird and confusing. Wish I remembered it, but just commenting to say that I vaguely remember there’s a way (or maybe I’m hallucinating).

Which x86 SBC is that? I’m interested!

I wonder what other useful key bindings we are missing out on?

Does Podman work well when you have multiple rootless containers that you want to communicate securely in a least-privilege configuration (each container only has access to what it needs)? That is the one thing I couldn’t figure out how to do well with Podman.

deleted by creator

I think what you mean is abandoning self hosting right? Because self hosting Bitwarden would have similar issues if you don’t take the initiative to update.

Unfortunately bspwm is better. Binary separation allowed for just about any layout imaginable, but river does not.

Deciding Linux isn’t for you is one thing. Even deciding that you hate Linux is… Digestible. But what kind of internal self esteem and validation issues do you need to unironically participate in a community called “Linux sucks”?

Hating Linux is one thing. Putting in extra effort to justify to everyone that Linux is hate-able is a different kind of crazy.

Is explicit sync for nvidia in yet?

Which is great that we’re not talking about groups of people, but national lines on a map

We are actually talking about a group of people - banned from contributing to open source for being Russian. Read the post again before embarrassingly framing your sentences like a smartass.

Can you use your own words to demonstrate why my argument isn’t convincing? What’s not convincing is throwing around the word “whataboutism” and thinking that’s an argument.

No it isn’t. Read the comment I replied to.