One of the downsides of being a Safari user is that the extension architecture doesn\u2019t support the functionality that other browsers do. In particular, where other browsers allow you to call out to Emacs when editing fields in the browser, this doesn\u2019t seem possible with Safari. That\u2019s too bad because I really<\/i> hate dealing with text outside of Emacs. None of my muscle memory works and all those editing habits and shortcuts I\u2019ve built up over the years can\u2019t be used.<\/p>\n
Happily, Abin Simon has a workaround<\/a>. He starts with how you\u2019d do it manually\u2014copy the text to the clipboard and paste it to an Emacs buffer, add to or edit the text, copy the edited text back to the clipboard and paste it into the browser buffer\u2014and automates the process. That turns out to be easier than you\u2019d think because he leverages Hammerspoon<\/a> to do the system part. The Emacs part is just a bit of simple Elisp.<\/p>\n This isn\u2019t as nice a solution as a browser plugin but it\u2019s a decent workaround. Simon\u2019s workflow is centered around interacting with Github but it\u2019s easily adaptable to other workflows.<\/p>\n","protected":false},"excerpt":{"rendered":" One of the downsides of being a Safari user is that the extension architecture doesn\u2019t support the functionality that other browsers do. In particular, where other browsers allow you to call out to Emacs when editing fields in the browser, … Continue reading