\u00c1lvaro Ram\u00edrez has a nice post on opening a file in the macOS Xcode editor from Emacs. There’s nothing unusual about that, of course, but Ram\u00edrez’s wrinkle is that he wants Xcode to open at the same line the Emacs point is on.<\/p>\n
It’s reasonable to ask why a devoted Emacser like Ram\u00edrez would want to open Xcode at all. The answer is that he’s more pragmatic than I am. I consider leaving Emacs a fail; something that I should try to find a fix for. Ram\u00edrez, as I say, is more pragmatic. Although he much prefers working in Emacs, he’s willing to use other tools if they’re more appropriate. Although he mostly uses Emacs for his iOS development, there are certain situations\u2014debugging, for instance\u2014where he feels Xcode is a better solution.<\/p>\n
He’s long used Bozhidar Batsov’s crux<\/a> to open the file he’s working on in Emacs in the Xcode editor. The problem was that it opened at the top of the file rather than at the line he was looking at in Emacs. It turns out, though, that you can call Xcode from the command line and specify the line to open the file at.<\/p>\n Ram\u00edrez, of course, used his dwim-shell-command<\/a> framework to implement this<\/a> but it would be trivial to adopt to plain Elisp if you’re not a dwim-shell-command user. You should also check out the comments in the reddit post<\/a> about the method. There are some other useful ways of integrating Emacs and Xcode workflows.<\/p>\n","protected":false},"excerpt":{"rendered":" \u00c1lvaro Ram\u00edrez has a nice post on opening a file in the macOS Xcode editor from Emacs. There’s nothing unusual about that, of course, but Ram\u00edrez’s wrinkle is that he wants Xcode to open at the same line the Emacs … Continue reading