I’m still learning AppKit, but couldn’t you enumerate the sharing services and display them in an Emacs buffer?
Also, why not bridge Objective-C directly from elisp?
Ah yes to both :) The post is low-effort trickery. No need to check out sources, recompile, etc. yet functional enough.
but couldn’t you enumerate the sharing services and display them in an Emacs buffer?
@calvin Try v0.25 or this change: https://github.com/xenodium/dwim-shell-command/commit/20e782b4bf1ea01fecfce3cc8ac4c5a74518cd80
I don’t use Emacs, but neat!
For Objective-C bridging, other than to add it if it’s not there, it would mean being able to call these APIs directly from elisp, by having things like i.e. objc_msgSend - it’d run in-process and avoid calling a compiler.
objc_msgSend
I’m still learning AppKit, but couldn’t you enumerate the sharing services and display them in an Emacs buffer?
Also, why not bridge Objective-C directly from elisp?
Ah yes to both :) The post is low-effort trickery. No need to check out sources, recompile, etc. yet functional enough.
@calvin Try v0.25 or this change: https://github.com/xenodium/dwim-shell-command/commit/20e782b4bf1ea01fecfce3cc8ac4c5a74518cd80
I don’t use Emacs, but neat!
For Objective-C bridging, other than to add it if it’s not there, it would mean being able to call these APIs directly from elisp, by having things like i.e.
objc_msgSend- it’d run in-process and avoid calling a compiler.