I use Ayu Dark theme, and I have noticed that background colors in git conflicts are a bit too bright:
The weird color choice persists across themes (with the example of Catppuccin Mocha):
Same issue, now in Catppuccin Mocha
The colors are normal if I make sure no conflicts are present in the opened repository, switch theme to Catppuccin Mocha, and introduce conflicts again. (I'm unsure if switching themes is really needed). The colors somehow fix themselves:
Switching back to Ayu Dark does not break colors:
But restarting Gram does (and the result is the first screenshot, which is how I got these, with a series of restarts and theme-switching)
system information
Gram: v2.1.2 (Gram)
Memory: 60.7 GiB
Architecture: x86_64
GPU: AMD Radeon Graphics (RADV RENOIR) || radv || Mesa 26.1.2
Installed from nixpkgs on NixOS 26.11pre1011622.a799d3e3886d (Zokor)
I use Ayu Dark theme, and I have noticed that background colors in git conflicts are a bit too bright:
The weird color choice persists across themes (with the example of Catppuccin Mocha):
The colors are normal if I make sure no conflicts are present in the opened repository, switch theme to Catppuccin Mocha, and introduce conflicts again. (I'm unsure if switching themes is really needed). The colors somehow fix themselves:
Switching back to Ayu Dark does not break colors:
But restarting Gram does (and the result is the first screenshot, which is how I got these, with a series of restarts and theme-switching)
## system information
Gram: v2.1.2 (Gram)
Memory: 60.7 GiB
Architecture: x86_64
GPU: AMD Radeon Graphics (RADV RENOIR) || radv || Mesa 26.1.2
Installed from nixpkgs on NixOS 26.11pre1011622.a799d3e3886d (Zokor)
<!--
Wiki: https://codeberg.org/GramEditor/gram/wiki/Feature-Requests
Docs: https://gram-editor.com/docs/
Chat: https://slidge.im/gram/#/guest?join=gram@rooms.slidge.im
This issue tracker is mainly for tracking and dealing with bugs.
- If you want to make a feature request or have an idea for improvements, please
create a page on the Wiki instead of opening an issue.
- If you have a question about how the software works or how to configure it,
check the wiki guides or the documentation, or join the chatroom and ask there
first. If the question turns out to be a missing feature, create a feature
request. If it's a bug, come back and create an issue.
If your issue really is a bug that you've found:
- Is it caused by hardware, for example missing support for your particular
graphics device? If so, you are probably the person best suited to solve the
problem since you are the one able to reproduce it. Start by trying to work out
as much about the cause of the issue yourself, and include as much detail as you
can in the issue. See the guide to debugging crashes in the documentation for
more information on retrieving logs or using a debugger with Gram.
- Is it a packaging problem, like missing builds for Windows, missing packages
for your architecture or support needed for a particular Linux distribution?
Just like in the previous case, you are probably the one most able to fix the
problem yourself. There is a mirror of the repository on Github only so that we
can run Github Actions on platforms that we don't have runners for on Codeberg.
Contributions to improve the workflows for both Forgejo and Github are welcome.
For any other issues, try to investigate the problem before creating an issue.
This is a code editor, you as a user of this editor is presumably a coder. Don't
let your preconceived notions about what you are capable of limit you in
familiarising yourself with your tools. Everyone benefits if you become able to
resolve the issues you encounter yourself.
Thank you <3
/ one grumpy toad with limited time on this earth
-->