Re: Teaching emacsclient to act as a pager, and more

[Stefan Monnier <monnier@iro.umontreal.ca>]

> Couldn't we still do that anyway, even if current Emacs does not
> misbehave when getting FDs? As long as it's opt-in.

Sure, but we'd still need a `ancillary_data' bit then.
BTW, another solution to the overarching process would be:
- in emacsclient, mknod a named pipe, and then pass all input to that
  pipe and similarly pass all its output to stdout.
- pass that named pipe as plain text to the Emacs daemon.
- extend make-pipe-process to also work on named pipes.

Or simpler:
- emacsclient connects to emacs daemon in pretty much the normal way.
- then (after warning the emacs daemon appropriately), turn the
  emacsclient into a simple proxy which reads from its stdin and passes
  that straight to the daemon's socket (and vice versa for the daemon
  socket's output).

This last strategy has the potential to be usable/useful even through
TCP connections.


        Stefan