Re: debug connecting to emacsclient

[Sven Bretfeld]

Hello Harry

Harry Putnam <reader@newsguy.com> writes:

> However when I ssh in from remote host and say emacsclient ~/myfile

That's not correct. You have to specify an additional parameter. If you
connect via ssh (thus in a shell), you have to type 'emacsclient -t'. If
you have a graphical environment, you have to type 'emacsclient -c'.
There is no need to specify a file. 

> I get an interminable message `waiting for emacs....'

Do you have more than one Emacs version installed? If you are, for
example, under Debian or Ubuntu, Emacs 23 will probably come from the
emacs-snapshot package. If you, then, type 'emacsclient -c' you will
invoke the client of Emacs 22. But Emacs 22 has no server running, so
the client waits for ever. You can do two things:

a) Make a symbolic link from /usr/bin/emacs to the emacs-snapshot
flavor, or

b) invoke the client with 'emacsclient.emacs-snapshot -c'

An additional hint: You should consider to run emacs as a daemon. I have
the following entry in my startup menu under GNOME: 'emacs-snapshot
--daemon'. This starts Emacs in the background right after the system
comes up. If I need Emacs, I always start a client: F2
'emacsclient.emacs-snapshot -c' (of course I have an icon for this). The
advantage is, that the client starts within one second. You can close it
without losing your buffers. Gnus remains open and everything else too.
MultiTTY is wonderful. For example, I have defined a Key that opens a
client with a small framesize. Whenever I find an interesting book in
the internet, I invoke this small client right next to the browser and
quickly hack the data into my bib-file, which is already open in the
daemon instance. 

Hope that helps,

Sven