all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matthew McClure <matt@continuousdelta.com>
To: help-gnu-emacs@gnu.org
Subject: Re: emacsclient –alternate-editor= “Could not start the Emacs daemon”; "standard input is not a tty"
Date: Mon, 19 Aug 2019 08:10:49 -0400	[thread overview]
Message-ID: <CAEV-cEqcvLvBBqp+nvK6xAxWsK97CORWW+O4F0w361wmh8PCLg@mail.gmail.com> (raw)
In-Reply-To: <CAEV-cEp4J0669OUqRUJ4wDz=V-zMKPaoGfd9QrstcM4RDKVEWg@mail.gmail.com>

On Sun, Aug 18, 2019 at 12:03 PM Matthew McClure
<matt@continuousdelta.com> wrote:
>
> How might I tell emacsclient that it shouldn't need a tty to start the
> Emacs daemon?
>
> I'm using Emacs 26.2 from Homebrew Cask.
>
> I have a Keyboard Maestro macro intended to create a new Emacs frame.
>
> /usr/local/bin/emacsclient -n -c --alternate-editor=
>
> Keyboard Maestro shows the following message.
>
> /usr/local/bin/emacsclient: can't find socket; have you started the server?
> To start the server in Emacs, type "M-x server-start".
> emacs: standard input is not a tty
> Error: Could not start the Emacs daemon

Disregard my question.

The macro works after changing the script to:

```
PATH="/usr/local/bin:$PATH"
emacsclient -c -n --alternate-editor=
```

Keyboard Maestro uses a different environment from Bash in Terminal,
and `/usr/local/bin` wasn't in PATH. It was trying to start the Emacs
daemon using /usr/bin/emacs. On my machine that's version 22.1.1,
presumably included with macOS.

-- 
Matthew McClure
Continuous Delta
https://www.continuousdelta.com/



      reply	other threads:[~2019-08-19 12:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-18 16:03 emacsclient –alternate-editor= “Could not start the Emacs daemon”; "standard input is not a tty" Matthew McClure
2019-08-19 12:10 ` Matthew McClure [this message]

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

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

  git send-email \
    --in-reply-to=CAEV-cEqcvLvBBqp+nvK6xAxWsK97CORWW+O4F0w361wmh8PCLg@mail.gmail.com \
    --to=matt@continuousdelta.com \
    --cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.