Greg Pfeil

> I do think from now on further efforts should be in line with issuing the error to the _Messages_ buffer, while not breaking Emacs startup. Yeah, I have to...

> Thanks again. Awesome work! Thanks, really appreciate you being so on top of these. > I prefer to see your first commit merged first, just to keep things one...

Ok, this has been rebased. I updated the version and also improved some of the documentation of the affected variables. (Even though I rebased, I made the new changes in...

I tested both the `ns-do-applescript` and `osascript` approaches, but I’m not sure where `mac-do-applescript` comes from. If you let me know, I will mention it in the doc/comments and test...

If something like #74 gets in, I’d update this to include system & emacs-dist specific tests. E.g., testing `mac-do-applescript` detection and operation for `emacs-macport`, and `ns-do-applescript` testing on other Emacses...

I just discovered there’s an additional way to check the appearance on Emacs-macport: ```elisp (pcase (plist-get :appearance (mac-application-state)) ("NSAppearanceAqua" 'light) ("NSAppearanceDarkAqua" 'dark) (appearance (lwarn 'auto-dark :warning "Unknown system appearance “%s”"...

> this PR would solve another problem: by using the shell for `osascript`, when a tramp buffer is active, the shell used will be the remote one, which may not...

I updated this branch, re-targeted against the development branch, and added a bit of improvement around #58. I think this should go in after #60.

I‘m curious whether #74 fixes this for you. I’m also curious (regardless of whether you test #74) what your configuration looks like. E.g., ```elisp (use-package auto-dark :custom (auto-dark-dark-theme 'meh-dark) :init...

Another question I had somewhat related to this … I had considered unifying the `osascript` and `powershell` management under a single `auto-dark-allow-shell` variable, but one thing that stopped me was...