-
Notifications
You must be signed in to change notification settings - Fork 0
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
Custom python-defined context not present in registry.contexts on cold start #83
Comments
Testing a few permutations, it looks like this combination of files is the culprit. So maybe some sort conflict between the two? If |
This issue appears to be caused by the naming convention of the files.
If any one of the vscode.{platform}.talon files are present, the vscode.py context is not present on startup. If I rename the files as such, the vscode.py context is present.
|
oh, I don't know why you'd name it vscode/vscode.mac.talon anyway |
it's sort-of convenient for readily finding all vscode-related things in most any app (e.g., windows explorer). |
fixed in 1365 |
v1357, OSX
This python-defined context for vscode doesn't appear in registry.contexts in the repl on cold start of talon
https://github.com/knausj85/knausj_talon/blob/95c91c034e584bc7344cbd7eb735ec1d08e7f93e/apps/vscode/vscode.py#L14
As such, title tracking for code.language doesn't function for VSCode, as it leverages the
win.filename
&win.file_ext
actions now. With Talon running, modifying and saving vscode.py will result in the context appearing, and then things work as expected.Cold start registry.contexts
After saving or moving the file:
user.knausj_talon.apps.vscode.vscode
is missing in the first instanceThe text was updated successfully, but these errors were encountered: