[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33219: 25.2; crontab -e doesn't connect to existing emacs daemon
From: |
Glenn Morris |
Subject: |
bug#33219: 25.2; crontab -e doesn't connect to existing emacs daemon |
Date: |
Tue, 27 Nov 2018 00:56:29 -0500 |
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
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.