"Stefan Monnier" <monnier@IRO.UMontreal.CA> wrote:

>>>> Okay, I understand, we _would_ need to find good and emacs like method
>>>> to handle this potential problem, but what I would like to know first is,
>>>> if this patch has any chance to get into CVS.
>>> It seems perfectly reasonable to me.
>> This sounds great. So I will work on some security stuff and user
>> feedback, when this error occurs.
>
> I also like it (actually, in the past, I've suggested to obey $TMP
> so as to be able to use different sockets, but an explicit socket-name
> argument sounds much better).
>
>> Is there also a chance to get a patch into CVS which enables
>> emacsclient to read from stdin?
>
> Sounds good to me (especially for the -eval case).

Okay, I used the time to extend the first patch with a buffer overflow
check and I also added the feature to use stdin for input if:

1. -e or --eval is given on the command line
   (I think it does not make sense for filenames)
2. there is no argument after the options

RFC

crunchy