Re: emacsclient horribly broken

[Richard Stallman]

    > 1) emacs -f server-start with server-use-tcp set to off throws an error
    >    (cannot bind to socket: address already in use). If server-use-tcp is
    >    enabled, the error disappears - so "old-style" local socket use is
    >    currently broken.

Does this mean that the emacs server is now broken in the primary mode
of operation (using Unix sockets) on GNU/Linux?  It sounds that way.

    Moreover, I resent the "troublesome" bit of your comment. All in all,
    the emacsclient/server patch is quite small, and most issues have been
    related to simple configuration issues that I had no way to test (and
    said so) and that have been trivially fixed.

Is that really true?