From: Kaushal Modi <kaushal.modi@gmail.com>
To: Emacs developers <emacs-devel@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: emacsclient not working on RHEL 6.8 (non-sudo) [master branch]
Date: Wed, 5 Dec 2018 12:36:04 -0500 [thread overview]
Message-ID: <CAFyQvY01B738Z_H7cr==O9Nj=RxnyO7apebqBGs9CJKMVqm+QQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY0g=sL6nRKkbq7ay_40nkuAkPyCq=5chvn93wYnqzPsDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1655 bytes --]
next prev parent reply other threads:[~2018-12-05 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 16:57 emacsclient not working on RHEL 6.8 (non-sudo) [master branch] Kaushal Modi
2018-12-05 17:36 ` Kaushal Modi [this message]
2018-12-05 19:17 ` Kaushal Modi
2018-12-06 18:52 ` Paul Eggert
2018-12-06 19:29 ` Kaushal Modi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY01B738Z_H7cr==O9Nj=RxnyO7apebqBGs9CJKMVqm+QQ@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.