unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: William Gardella <gardellawg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: emacsclient does not start: How to create a server file?
Date: Sun, 17 Mar 2013 23:02:08 +0000	[thread overview]
Message-ID: <87fvztljf3.fsf@gmail.com> (raw)
In-Reply-To: 1363539530398-281116.post@n5.nabble.com

Hi Stefan,

Stefan Husmann <stefan-husmann-zqRNUXuvxA0b1SvskN2V4Q@public.gmane.org> writes:

> Hello,
>
> when I try to open a file with emacsclient, I get 
>
> emacsclient -f ~/.emacs.d/se .emacs
> emacsclient: error accessing server file "/home/haawda/.emacs.d/se"
>
> If I do not specify the server file with -f, I get a similar message, but
> wit ~/tmp/server. The server files do not exist. How can they be created?
> And why is ~/tmp the default?
>
> I am on Arch Linux. My emacs is a selfcompiled version from the xwidget
> branch, but the behaviour also happens with an emacs from trunk with lucid
> gui.

Is the server already running?

If not, one good technique is to run emacsclient -a "" or have
ALTERNATE_EDITOR="" in your environment.  Either way, this will cause
emacsclient to start an emacs --daemon in the background and then
connect to it, rather than just exiting with an error that it can't find
the server.

I am not sure why ~/tmp/server is the default server file for you.
Perhaps it has to do with the prefix you used when configuring?

-- 
Regards,
WGG




  reply	other threads:[~2013-03-17 23:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-17 16:58 emacsclient does not start: How to create a server file? Stefan Husmann
2013-03-17 23:02 ` William Gardella [this message]
2013-03-17 23:29   ` Stefan Husmann
2013-03-17 23:37     ` William Gardella
2013-03-17 23:56       ` Stefan Husmann
2013-03-18 13:28       ` Stefan Husmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fvztljf3.fsf@gmail.com \
    --to=gardellawg-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).