This will minimise the time your fish have to spend in overcrowded containers and poor water conditions. I see no reason why this shouldn't work with Aquamacs as long as you use a compatible emacsclient version on the remote.Stage 1 : Start by taking down the aquarium last when packing, and putting it up first on arrival. Emacsclient 22 and older are not compatible.Īnd, finally, finally, I don't know if tramp works, but this blog post gives you the scripts that do, I think, essentially what I outline above, and it does use tramp: Aquamacs 2.x is based on Emacs 23, and as such, the emacsclient must be of version 23.x. Maybe emacsclient will work that way.įinally, make sure you use compatible emacsclient versions. If you inspect it, you'll see some ports, so I would simply try leaving it in place, but tunneling the local port to the remote, and creating a "fake" server file (try ~/.emacs.d/server/server on a standard unix machine) with the port numbers you choose to use on the remote end. The server file, on Aquamacs, is "/Users/dr/Library/Application Support/Aquamacs Emacs/server/server". 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:
#How to use aquamacs 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)?.Previous message: Aquamacs(mac) + remote emacsclient(linux)?.Aquamacs(mac) + remote emacsclient(linux)? David Reitter david.reitter at Aquamacs(mac) + remote emacsclient(linux)?
0 kommentar(er)
