Since KDE6 akregator defaults to a very narrow, center-justified display of articles. Akregator seems to use the grantlee library for formatting and it’s possible to modify the behaviour by editing the CSS in /usr/share/akregator/grantleetheme/5.2/normalview.html, but of course the changes get lost when akregator is updated.
How is it possible to change the default formatting per user and have the changes ‘stick’ after an update?
1 Like
Did you tried to copy the file(s) into ~/.local/share/akregator/… and then check if the changes are respected by akregator ?
1 Like
That’s the solution.
Akregator looks for the files under ~/.local/share/akregator/grantleetheme/5.2 first, so copying them there works. Unfortunately if akregator finds the files under ~/.local/share it doesn’t bother to look for them under /usr/share so it doesn’t seem to be possible to save just the changed values: the whole file needs to be copied.
This worked until Akregator 23.05. In Akregator 24.08 they’ve changed the system again and the grantlee files have gone, so the question remains: how is it possible to change the default formatting without resorting to patching the sources?
Probably should have been “We’re stopping people using non-“exposed” css styles that are exposed under ~/.local/share by the nature of KDE’s customisability… Oh, and in a few minutes, (Deduplicate style · KDE/akregator@d6cc3d1 · GitHub) we’ll dedupe the css out of the non-exposed templates to make it even easier for people to er, not create custom styles…”
As for themes - oh, yeah - they are totally good to go - dark theming coming up!
You up doo-doo creek without a paddle…
You might be able to work round it by specifying your own browser, and some greasemonkey to modify what it is sent, but as you suspect, ripping out that commit is probably going to be the way to go until something happens like allowing you to specify a css file…
In the meantime, you might want to go count your unicorns.
Is it just me or is there a push to internalise things that were formerly available under .local - be it by “accident” or on purpose… I recall several menus that became unmodifiable since the former “desktop” files were internalised preventing removal / overriding of unwanted “defaults” to think of one recent one - Spectacle’s “Export” to think of one - yeah great - so many export options… I only ever use 1 of them, I only have an account on 2 of them and neither are ever at the top, and the order seemed to be random… So I stopped using that feature entirely (partly due to the issue with losing undelete URLs if you weren’t happy with a column of popup notifications) and have a script watching the save-directory.
Yay, progress… Spacebar heating, anyone?
Looks like KDE is taking the Gnome route and increasingly ‘dumbing down’ their software.
I’ve found a workaround: patching style.css in the source, but it’s very annoying to have to jump through hoops to do something as simple as getting a useable article display. The whole point of using CSS is to make things customizable.
Durr, yeah - much better idea than reverting that…
Yeah - surely they could leave the css external.
File a bug report.
Yes, a bug report is my next step.
See that there is already a bug report with a good example use-case for the ability to customise the “default” (forced) layout.
Cross your fingers!
The bug report has number 488176 on bugs kde org, in case anyone else wants to view it (you can also add yourself to the cc list to receive updates), without having to search for it.
Also, is it just me, or is the text display getting narrower over time? There are barely ten words in a row now.