Re: [PATCH] Generalize start-process with keyword args

[Stefan Monnier]

> I tend to agree with Stefan, as I find no documentation about the
> implication of no-conversion for ":coding nil" except in the C source
> code.  Maybe we could add the exception back if it turns out to be too
> confusing.

We should probably also declare that uses of nil in other similar
circumstances is deprecated (I actually don't know where are those
places where nil means "binary").

> +If @var{coding} is @code{nil}, the coding system chosen for decoding
> +output is @code{undecided}, meaning deduce the encoding from the
> +actual data.

Doesn't it also depend on coding-system-for-read and coding-system-for-write?

> +  tem = Fplist_get (contact, QCconnection_type);
> +  if (!NILP (tem))
> +    {
> +      if (EQ (tem, Qpty))
> +     XPROCESS (proc)->pty_flag = 1;
> +      else if (EQ (tem, Qpipe))
> +     XPROCESS (proc)->pty_flag = 0;

Please use `true' and `false' instead of 0 and 1.

> +      else
> +     report_file_error ("Unknown connection type", tem);
> +    }
> +  else
> +    XPROCESS (proc)->pty_flag = !NILP (Vprocess_connection_type);

Any reason why you nested the "if/elseif/else" inside the outer "if"
instead of having a 4-way "if/elseif/elseif/else"?
[ Either way is fine by me, I'm just being curious here.  ]


        Stefan