Joseph Mingrone <jrm@ftfl.ca> writes:
> After starting an Emacs daemon, everything works as expected, but after some
> time (or event I'm unaware of), trying to open a file from a shell gives an
> error.

> % emacsclient some_file Waiting for Emacs...  *ERROR*: Wrong type argument:
> stringp, nil

> I can create new frames, so the daemon is alive and reachable, but the error
> is still reported.

> % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (new frame opens)

> Creating a new frame without the -n flag fails.

> % emacsclient -nc *ERROR*: Wrong type argument: stringp, nil (no new frame)

> How should I debug this?  Using (setq debug-on-error t) doesn't help.

> This is with the 5th pretest for 25, but the problem has been around earlier
> in the 25 branch.

After the problem has been triggered, this still works without an error.

% emacsclient -e '(find-file "~/some_file")'