follow system theme

[vredesbyyrd]

First, thanks for all your work on this fork. It's unfortunate that the upstream repo has fizzled out.

I'm using marktext on Niri. Gnome is also installed. But the autoSwitchTheme preference does not work on my setup. ie, toggling gsettings set org.gnome.desktop.interface color-scheme prefer-{dark,light} is ignored.

If i understand correctly that setting is only read on startup? It would be really nice if marktext could watch the 'color-scheme' variable during runtime and apply the theme according, without a restart.

I'm not sure how the "autoSwitchTheme" preference chooses which light/dark theme to set? i'm assuming it's hardcoded?

[Tkaixiang]

Hi just to confirm, what you mean is that:
After starting up, you change the System Theme, and Marktext does not follow to change to light/dark mode?

[vredesbyyrd]

Correct. For example. Start marktext -> change System Theme to prefer-dark -> marktext does not change theme, still light-mode.

I believe that is expected behavior at the moment, though? So I posted this here as a conversation starter for a nice-to-have feature as opposed to a bug report. It would be nice if Marktext could watch for System Theme changes during runtime and update it's light/dark mode accordingly, without a restart. Typora allows for configuring a theme for light mode and a theme for dark mode and it watches for system changes.

To clarify. Separate from the requested "runtime theme autochange" feature, setting the "Adjust theme at startup" preference to true does not work on my system. eg, System Theme = prefer-dark -> start marktext -> marktext opens with light theme. I could file a separate bug report for that need be.

I may dig into this myself. I'm just not familiar with marktext code yet.

Much appreciate your response and time. I just read your message about being away until December.

[vredesbyyrd]

Also, i tried to start marktext with the --debug flag with hopes it would return some useful information for us, but get an error:

 marktext --debug                                                                                                                                                                                                                
electron: [DEP0062]: `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` and `node --inspect-brk` instead.

[vredesbyyrd]

I think I have a fix. Going to test it a bit more and than i'll make a pull request or describe the changes here.

[Tkaixiang]

Great! Looking forward to your PR 😄