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

"warning: failed to get scripting definition" #55

Closed
blissdev opened this issue Jun 22, 2019 · 5 comments
Closed

"warning: failed to get scripting definition" #55

blissdev opened this issue Jun 22, 2019 · 5 comments
Labels
question Request for information or help, not an issue

Comments

@blissdev
Copy link

$ yabai
2019-06-22 16:23:11.127 yabai[555:8381] warning: failed to get scripting definition from /System/Library/CoreServices/Dock.app; it may not be scriptable.
yabai configuration loaded..

Does this indicate installing the sa-additions failed? I did run the command without error.

macOS 10.14.5

@koekeishiya
Copy link
Owner

This warning is just because there is no .sdef file within the Dock.app "folder".
This file is supposed to define an interface for applications that provide an API such that external software written by other people can call functions or otherwise interact with a running instance of the application. (see e.g Spotify as an example).

The Dock.app provides no such definition, and that is what this warning is about.
It is not related to how we use the Scripting Bridge framework for code injection.

Hopefully this clears up some misconceptions regarding this warning.

For people who are interested in more information, search for"sdef", "scripting bridge framework", "scriptable applications" on google/apple docs.

@koekeishiya koekeishiya added the question Request for information or help, not an issue label Jun 22, 2019
@koekeishiya
Copy link
Owner

koekeishiya commented Jun 24, 2019

@dominiklohmann

Maybe we should mention something about this warning as well in the wiki somewhere? I've given a few attempts at trying to silence the warning before we issue the load command, but I cannot seem to find a way to silence it..

@dominiklohmann
Copy link
Collaborator

Noted.

Did you try temporarily redirecting stderr to /dev/null while loading the scripting addition using freopen, unless --verbose is set?

@koekeishiya
Copy link
Owner

No need to mention it, apparently I was just doing some dumb mistake last time I attempted to temporarily redirect stderr to /dev/null

@dominiklohmann
Copy link
Collaborator

Noted. 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Request for information or help, not an issue
Projects
None yet
Development

No branches or pull requests

3 participants