Closed phillco closed 2 years ago
Question is whether to just make a os: mac
context that makes file_manager_current_path()
return window.doc
as a baseline, rather than having this file_manager_current_path_or_doc
.
I think that's the better behavior. I don't want to override any integrations that people have made that are more specific, but those should really have even more specific context matchers on them, right?
Question is whether to just make a
os: mac
context that makesfile_manager_current_path()
returnwindow.doc
as a baseline, rather than having thisfile_manager_current_path_or_doc
.I think that's the better behavior. I don't want to override any integrations that people have made that are more specific, but those should really have even more specific context matchers on them, right?
Makes sense to me. I have a custom implementation for Finder that uses AppleScript (and probably should use appscript) for example: https://github.com/nriley/knausj_talon/blob/50fac680e8ea8ad1771c0578c767f10bc0b735aa/apps/platforms/mac/finder/finder.py#L19
Yeah, we should probably check your custom file_manager_current_path
s in here.
This makes it easy to reveal the current folder or document (from the terminal, editor, etc.)