Re: Bizarre behavior of emacsclient on OS/X

[Bruce Korb <bruce.korb@gmail.com>]

Problem solved.  To use emacsclient successfully you must not only
figure out which
temp directory to use, you must also use the correct client because
the distributed
default "emacsclient" won't talk to the emacs fired up via the
application's icon.  SO:

> ec=$(find /Applications/Emacs.app -name emacsclient)
> tmpdir=$(getconf DARWIN_USER_TEMP_DIR)
> uid=$(id -u)
> $ec -s $tmpdir/emacs$uid/emacs ${1+"$@"}

Maybe this could be made a little easier?
Like emacs squawking that some unknown message came in on the socket
and emacsclient testing the possibilities for TMPDIR?

Thank you!!

On Wed, Jun 5, 2013 at 10:03 AM, Bruce Korb <bruce.korb@gmail.com> wrote:
>> $ getconf DARWIN_USER_TEMP_DIR
>> /var/folders/22/_6n21qmj3rgfqtrqy2nd81d8898tm8/T/
>> $ id -u
>> 278162056
>> $ f=$(getconf DARWIN_USER_TEMP_DIR)/emacs$(id -u)/emacs
>> $ file $f
>> /var/folders/22/_6n21qmj3rgfqtrqy2nd81d8898tm8/T//emacs278162056/emacs: socket
>> $ emacsclient -n -s $f myfile
>> $
>
> I'm writing because:
>
> 1. emacsclient does not default to the same temp directory, and
> 2. when I force it to use the correct temp directory, the emacs daemon (server)
>    does *not* open "myfile".
>
> How do I chase down the cause?