Martin Kühl

Results 73 comments of Martin Kühl
trafficstars

> Not really. It looks like it RAL doesn't wait for anything to load, and just goes ahead and loads PATH in front of direnv. i might be missing something...

output of `esbuild --help` before: ![terminal white before](https://user-images.githubusercontent.com/505/160072370-77ea780c-8114-42a4-a947-6dc84fb97477.png) and after: ![terminal white after](https://user-images.githubusercontent.com/505/160072396-e0820766-19df-4ae5-9323-911338b9d787.png)

hmm actually i think #CCCCCC has better contrast against other colors :thinking:

screenshot before: ![inlay hints before](https://user-images.githubusercontent.com/505/160070355-1a2b70ba-c579-4ff1-94ef-6241063ee407.png) and after: ![inlay hints after](https://user-images.githubusercontent.com/505/160070373-bb6aff11-f57c-4309-9501-e0d0fd44e582.png)

i also use fontconfig to e.g. choose a default monospaced font or enable features on fonts. this currently means that flatpaked applications use different fonts and features than i configured.

@vibragiel if #1021 is a duplicate then this is unrelated to pleroma you may also want to include the error message as text here so other people can find it

here's vscode with the theme border (noticeable as a thin line around the status bar) ![VSCode](https://user-images.githubusercontent.com/505/203420300-da04646e-0ea7-43f4-8a68-95e8f35f05ed.png) maybe i'm confused as to which apps actually use libadwaita but here's gnome text...

> The libadwaita apps on your screenshots have a border too, but the difference is that it's semi-transparent and drawn over the window contents. ohh i see, thank you for...

i've switched to dark mode for a while now and the border around libadwaita apps is much more noticeable, so now i'm not sure if removing it from this theme...