For this, the remote must have access to this file (created by the server), and this is where things get complicated. Set `server-host' to the right name or IP (of the server), and give emacsclient the -server-file option (or specify EMACS_SERVER_FILE). The emacs server must be told to use TCP rather than a local socket (set `server-use-tcp' variable according to emacsclient manual. The best way would probably be to instruct SSH to tunnel the connection (with this port) along with your regular terminal connection. That is, the IP must be public and the port open. Yes, in a pure-unix world, you'd use X, but that wouldn't give you Aquamacs.įor what you need to do, you need to have your local machine visible and accessible for the remote. So, basically, you want to work on some remote machine via SSH, but be able to edit files there using your local Aquamacs installation. But the emacsclient (-version 21.4) on the "remote" system, where the files are but no display, doesn't seem to speak network-ese: AQUAMACS EMACS HOW TO> I've figured out how to drive Tramp appropriately, that part's working. > - causing it to use a Tramp URL to access the actual file > - which connects back from the "remote" computer to my emacs-server > - ssh to the "remote" computer, and run something-like-emacsclient with no doubt some command args voodoo > - run Aquamacs on my "local" computer, the one with the keyboard and display > Sorry, I've found plenty of partial answers in the dox and on the web, but I can't quite thread them all together. On Sep 12, 2011, at 3:38 PM, Jack Repenning wrote: Next message: Aquamacs(mac) + remote emacsclient(linux)?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |