Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose ~/config/gtk-4.0 with read only permissions for all flatpaks #131

Closed
n3thshan opened this issue Jan 16, 2025 · 2 comments · Fixed by #136
Closed

Expose ~/config/gtk-4.0 with read only permissions for all flatpaks #131

n3thshan opened this issue Jan 16, 2025 · 2 comments · Fixed by #136

Comments

@n3thshan
Copy link

n3thshan commented Jan 16, 2025

Background

KDE uses its own gtk 4 configs to make gtk4 apps look more consistent with plasma. One issue with exposing them globally with read only is that Kate (or other text editors) may not be able to write/edit the file unless they are explicitly given write access to. The following screenshot best explains this.

Before After
Image Image

Notice how the corners are less rounded just like normal KDE apps when the gtk-4.0 is exposed! It is a minor cosmetic change, yet impacts the intuitiveness of the desktop IMO. I also believe by doing so, it makes the accent color of gtk 4 apps the same (or atleast somewhat) as Plasma's. Hope this would be considered.

@RealVishy
Copy link
Collaborator

One issue with exposing them globally with read only is that Kate (or other text editors) may not be able to write/edit the file unless they are explicitly given write access to.

Do they need write access for anything? Does it provide any extra functionality.

@n3thshan
Copy link
Author

n3thshan commented Jan 17, 2025

@RealVishy the only ones i can think of would be to use custom gtk4 themes and/or change the accent colour to a custom one via a text editor. But then again since this is KDE i doubt most users would do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants