GNU bug report logs - #33219
25.2; crontab -e doesn't connect to existing emacs daemon

Previous Next

Full log

Message #20 received at 33219 <at> debbugs.gnu.org (full text, mbox):

From: Boruch Baum <boruch_baum <at> gmx.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 33219 <at> debbugs.gnu.org
Subject: Re: bug#33219: 25.2; crontab -e doesn't connect to existing emacs
 daemon
Date: Tue, 27 Nov 2018 15:47:34 -0500

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.