|
From: | David Reitter |
Subject: | Re: emacsclient 22 and 23 incompatibility |
Date: | Sat, 1 Aug 2009 13:04:56 +0200 |
On Aug 1, 2009, at 12:55 PM, David Kastrup wrote:
It's a pity that this doesn't work out-of-the-box, given that not all platforms use an install procedure that will update a centrally installed emacsclient program along with the new Emacs main application.All platforms supported by Emacs do AFAICT. If there are install procedures outside of the control of the Emacs maintainers which don'tdo the right thing, I don't see why it would be a good idea to bend overbackwards to support them.
Oh, I must have been missing out on something. Could you please explain how the Nextstep port does that?
According to what I know:"make install" installs a .app in the nextstep folder, which is then supposed to be moved by the user wherever they want on their file system. The emacsclient binary is inside the .app and not copied to anywhere in PATH. That is why the existing 22 emacsclient binary (which is in PATH) stays in place and gets called by other applications such as "Skim" in order to communicate with Emacs, which fails.
[Prev in Thread] | Current Thread | [Next in Thread] |