From: Boruch Baum <boruch_baum@gmx.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 33219@debbugs.gnu.org
Subject: bug#33219: 25.2; crontab -e doesn't connect to existing emacs daemon
Date: Tue, 27 Nov 2018 15:47:34 -0500 [thread overview]
Message-ID: <20181127204734.z2lbq7jnwi6pihxj@E15-2016.optimum.net> (raw)
In-Reply-To: <aein0j5aia.fsf@fencepost.gnu.org>
Thanks for pointing out the bug; I've forwarded your mail to that bug thread.
On 2018-11-27 00:56, Glenn Morris wrote:
> Boruch Baum wrote:
>
> >> > However, in other uses of emacsclient via $EDITOR (eg. mutt, newbeuter,
> >> > w3m) the client does find the socket file and does connect to the
> >> > existing daemon.
> >>
> >> Then I'm confused as to how this is supposed to be an Emacs issue.
> >
> > Well, it is emacsclient that is reporting that it can not operate as
> > expected when called by a core *nix utility. Think of the alternative:
> > if I file a report against 'crontab', those guys will correctly tell me
> > that they just use the $EDITOR value, that emacsclient _is_ being
> > launched, and the error happens within emacsclient.
>
> I'm saying that you need to investigate why crontab and mutt behave
> differently.
>
> For example, perhaps "crontab -e" does not pass TMPDIR to the spawned editor:
> https://bugs.debian.org/19237
>
> I verified by doing:
> M-: (getenv "TMPDIR")
> in the Emacs spawned by crontab that this is indeed the case.
>
> So yes, I think it is a crontab issue.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2018-11-27 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 21:44 bug#33219: 25.2; crontab -e doesn't connect to existing emacs daemon Boruch Baum
2018-11-01 16:25 ` Glenn Morris
2018-11-01 17:31 ` Boruch Baum
2018-11-27 5:56 ` Glenn Morris
2018-11-27 20:47 ` Boruch Baum [this message]
2018-11-28 20:11 ` Glenn Morris
2018-11-27 20:46 ` bug#33219: " Boruch Baum
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=20181127204734.z2lbq7jnwi6pihxj@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=33219@debbugs.gnu.org \
--cc=rgm@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.