Closed knausj85 closed 4 years ago
Testing a few permutations, it looks like this combination of files is the culprit.
So maybe some sort conflict between the two? If vscode.mac.talon
is removed, vscode.py will be present and function on cold start.
This issue appears to be caused by the naming convention of the files.
vscode.mac.talon
vscode.linux.talon
vscode.win.talon
vscode.py
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.
mac.talon
linux.talon
win.talon
vscode.py
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 instance