From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: emacsclient not working on RHEL 6.8 (non-sudo) [master branch] Date: Wed, 5 Dec 2018 14:17:07 -0500 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Trace: blaine.gmane.org 1544037630 21265 195.159.176.226 (5 Dec 2018 19:20:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 5 Dec 2018 19:20:30 +0000 (UTC) To: Emacs developers , Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 05 20:20:26 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gUcif-0005QV-Gi for ged-emacs-devel@m.gmane.org; Wed, 05 Dec 2018 20:20:25 +0100 Original-Received: from localhost ([::1]:36359 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUckm-0002zx-5V for ged-emacs-devel@m.gmane.org; Wed, 05 Dec 2018 14:22:36 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUciQ-0001OB-Uf for emacs-devel@gnu.org; Wed, 05 Dec 2018 14:20:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUcg8-0000Rt-CT for emacs-devel@gnu.org; Wed, 05 Dec 2018 14:17:49 -0500 Original-Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]:44622) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gUcg7-0000QQ-5S for emacs-devel@gnu.org; Wed, 05 Dec 2018 14:17:48 -0500 Original-Received: by mail-lf1-x12a.google.com with SMTP id z13so15570570lfe.11 for ; Wed, 05 Dec 2018 11:17:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=dJsPHWEQtr9Y+5atufMqefwdKnP4YvkGtZ7Gw9YyTcw=; b=lfsZk5g8f9YNZEr2ZB6cphfly0WbfuHO+wl5dC/o727YHZl2D6pdMgZXfPfj14pLsU Zp4V7fHbhwGmfQCAk7BMXmVCwyV28/xt0XJ7u5d9ZkmK4t8xJd4kW/7uek3UE/fwzxMB ivCUbMTVU+gvlU8YeLujQTkGxSNaOKn+rrZVBtrNOK+lpEFGy4pCdu8jCkfkEVYPUoWx eaa/z8TuIMItBD6XJ8Lb4Sj/+YuCg1Y4YpYtXBWYX6+OhjIF6RaxueIV04/nUI61inaN ddLboaQ+9wE+e2hM0P/YGWGxqW0hSB2mMTM16xg7uVbqioYUoy1r1SAyNsoyEEdh1/b8 QUJw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=dJsPHWEQtr9Y+5atufMqefwdKnP4YvkGtZ7Gw9YyTcw=; b=Qgv8RxYIIaTvFjBdu8RENDcAiYjHjlx69mGKu4lwZU+G63zNJYhoafNARTbG6pINeX hQTlgwEnzf051zJD171ynM4EM8yu5cid+RkVqlb7IDunMBWmqSLOYi4Ue2RKOAMYn16N OgAUG/Gc7B5lUFDFpcurGoVlC49J89QQH/Tu/z76sRNeXpe+UjvXQIS0sI6PJqwJx58t bXnfwm6lJeCX7ipLesgVvVJhPfEw/43xHScmfsomwhuHnG79lG2t1F058TjdFBfU6PiQ 8U5clibi4/POwuwlL+u05wMYtTu1G3hg3igef3WfPBa9R0EXaw3jNZ/yhmkeiGYjM1bq A9ew== X-Gm-Message-State: AA+aEWZgiJY6JaeHlY6ouklhtDoZO9ArIit+ySU4h63lDxPvmBBqbvbf oEqQpJ+yHPRUWJq/6tKRd9uDeKODAsvR8P1kPqot8ZtZ X-Google-Smtp-Source: AFSGD/X5NpuQSGiEZOsJ2hNHWXMvAdHmS4cFpXmEfIAdR1BEXHyyu/NlMc2RIU/NR4846kVo0PfyD6ypUEEv4+orYfg= X-Received: by 2002:a19:f510:: with SMTP id j16mr14287761lfb.35.1544037465311; Wed, 05 Dec 2018 11:17:45 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::12a X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:231645 Archived-At: These issues go away if I rebuild emacs using the 9-day old commit f3328f995ee316cffa1a86117e6da2ba299d2c90 [1], before any of the changes happened to emacsclient.c. [1]: https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=f3328f995ee316cffa1a86117e6da2ba299d2c90 -- Kaushal Modi On Wed, Dec 5, 2018 at 12:36 PM Kaushal Modi wrote: > > Some more information .. > > Earlier "emacsclient -c&" used to work. Now doing that auto-suspends that process and on doing fg, I get "broken pipe". > > But "emacsclient -c" seems to be working (without that &). But then I need to block a new terminal for each new emacsclient invocation (with or without -c) .. > > Also, I fixed a regression in one of the 3rd party Elisp packages that got updated in last month. > > After that, instead of "broken pipe" error, I now see "*ERROR*: Assertion failed: (eq (match-end 0) (length string))" > > That error is originating from servel.el: > > ===== > (condition-case err > (progn > (server-add-client proc) > ;; Send our pid > (server-send-string proc (concat "-emacs-pid " > (number-to-string (emacs-pid)) "\n")) > (if (not (string-match "\n" string)) > ;; Save for later any partial line that remains. > (when (> (length string) 0) > (process-put proc 'previous-string string)) > > ;; In earlier versions of server.el (where we used an `emacsserver' > ;; process), there could be multiple lines. Nowadays this is not > ;; supported any more. > (cl-assert (eq (match-end 0) (length string))) > ===== > > I get that assertion error if I do "emacsclient -c&". But if I do just "emacsclient -c", a new Emacsclient frame launches fine.