[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Eli Zaretskii
Subject: Re: Teaching emacsclient to act as a pager, and more
Date: Fri, 09 Sep 2016 22:26:28 +0300

> From: address@hidden
> Date: Fri, 09 Sep 2016 15:03:23 -0400
> > Looking at your patches, it seemed to me that you indeed need a pipe,
> > no?
> Not as far as I know - what in my patches suggests that I need a pipe?

A pipe is a set of 2 file descriptors between 2 programs, one of the
descriptors is used for reading by one program and writing by the
other, the other descriptor used similarly in the opposite direction.
Isn't that what you set up?

If not, then I must be missing something, so please describe the data
flow between emacsclient, emacs server, and the external program.

> I am just passing in the arbitrary file-descriptors that emacsclient has
> as its stdin/stdout. They are directly moved into the main emacs
> process, not tunneled over a pipe. Those file descriptors frequently
> would be pipes, but could be regular files or anything else. And given
> that I have these two arbitrary file descriptors, I need to manipulate
> them somehow - and I do that by passing them into make-fd-process to
> make a process object backed by those two arbitrary file descriptors.

I'm trying to see if a higher-level abstraction can be used here,
because passing file descriptors is too low-level and therefore less


reply via email to

[Prev in Thread] Current Thread [Next in Thread]