deliriousn0mad

joined 1 year ago
[–] [email protected] 2 points 3 weeks ago

Oh alright, I do see the point now! I had the wrong idea about how it works. I get the need to have more guarantees on functioning packages

[–] [email protected] 2 points 3 weeks ago (2 children)

About that, I don't really see the appeal of Slowroll, except as psychological reassurance for those who would feel the need to update every time a snapshot comes out. I mean, I personally slow-roll on Tumbleweed all the time by only updating once a month, sometimes more and sometimes less like for this update. I'd be interested to know why you use it!

[–] [email protected] 1 points 7 months ago

Thank you, I didn't know about ydotool, I'll get it working on openSuse

[–] [email protected] 1 points 7 months ago (2 children)

That's a great workaround, could you share the command?

[–] [email protected] 22 points 7 months ago (1 children)

How do the Tumbleweed Folks among us deal with this?

We generally don't add many third party repos and we set repository priorities. If I understand this correctly, you are currently using official openSUSE packages and your upgrade is prompting you to upgrade them by changing vendor to this home:wolfi repo. If you want to keep the original packages, you just need to set priorities: in YaST 's "Software Repositories" page for instance, you can select a repo and see what its priority is (99 is the lowest priority, 1 is the highest). You could for instance put the official repos at 95 priority and the wolfi repo at 99. This way, packages will remain set on the official repos even if there are new versions on the other repo.

However, if you have packages that you want to get from the wolfi repo but are also in the official repos, with this method you will be asked to change those packages to the official repos, the inverse situation compared to your issue. You can tell the system to keep those packages from your chosen repo, I do it by choosing a version on the YaST Software page.

[–] [email protected] 4 points 8 months ago

I love how the division in Europe vaguely looks like the Protestant Reformation led to different prefix numbers (I know I know, Poland & co don't match)

[–] [email protected] 1 points 8 months ago* (last edited 8 months ago) (1 children)

I had the same annoyance and ended up uninstalling it, I'll look into remapping the up arrow too, I never liked the way ctrl-r works anyway. By the way, do you know how to delete a command from history in atuin? I found a bunch of discussions in development about this and some comments saying the function was added, but never mentioning the shortcut or command to delete

[–] [email protected] 12 points 8 months ago (1 children)

Oh COME ON. Where was this when my laptop died a month ago? I had to replace it asap and the previous kde slimbook was already out of stock. I got a great tuxedo, but this one is the same price and much better specs... I have the worst timing. Great news for everyone else though!

[–] [email protected] 2 points 8 months ago (1 children)

Beta? It isn't experimental, it was an official feature that is no longer supported (even if it still works perfectly).

[–] [email protected] 5 points 8 months ago* (last edited 8 months ago) (3 children)

As I said somewhere else, to get more compact tabs you can go to about:config and search for a setting called browser.tabs.tabMinWidth, I usually change the number to 20 (the default minimum width is like 70) and tabs are allowed to become roughly as narrow as in chrome. And if by "more compact tab bar" you meant how tall tabs are, there's the browser.compactmode.show setting, put it to "true" and then in the Firefox menu under More Tools → Customize Toolbars you can select "compact mode" in the "Density" menu on the bottom, which makes the tab bar and toolbars shorter

[–] [email protected] 22 points 9 months ago

This video is criticising Lunduke, it isn't made by him

[–] [email protected] 1 points 9 months ago* (last edited 9 months ago)

To mitigate this you can go to about:config (write it in the address bar) and search for a setting called browser.tabs.tabMinWidth, I usually change the number to 20 (the default minimum width is like 70) and tabs are allowed to become roughly as narrow as in chrome. It's a much simpler and stabler option compared to custom CSS

 

I use my own custom keyboard layout based on the US International layout that adds in all the symbols needed to write in all Latin script European languages, such as č, ħ, ð, ş, ł, l·l, ő, ů... Most are created via dead keys, others such as ø, æ, ə are added into the third and fourth levels (AltGr and Shift). I find it very useful as I write in different language and have to input a lot of names from all over the world for work. It's not optimized for any language, but is reasonably easy to use for all of them.

Originally I had used a keyboard layout creator on Windows, but when it came to recreate it on Linux I had to resort to editing system files: I mapped every key by duplicating and editing one of the layouts found in the /usr/share/X11/xkb/symbols/us file, gave it a new name and then edited /usr/share/X11/xkb/rules/base to add the name of the new layout. Logout, login again and there the new layout was, perfectly functional.

This system is not practical at all though, especially because some updates (not all) rewrite the files and revert my keyboard to normal US international, so I have to copy-paste the layout again. Plus, I don't know if xkb is one day going to be deprecated, as it is part of X11, leaving me without my layout.

Is there any "proper" way to create a layout and have it recognized by Plasma possibily without editing system files?

view more: next ›