all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: emacsclient not working on RHEL 6.8 (non-sudo) [master branch]
Date: Thu, 6 Dec 2018 14:29:23 -0500	[thread overview]
Message-ID: <CAFyQvY3Yo8ON08pOPAqnJiOQ=-y=zt7kMkXj-h5XFkRdPm-==Q@mail.gmail.com> (raw)
In-Reply-To: <ae98e017-3c69-1cdc-0a0b-7608fdf1ea18@cs.ucla.edu>

On Thu, Dec 6, 2018 at 1:52 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> Thanks, I reproduced the problem and installed the following patches.
> The first should fix the bug. The second should fix some display
> glitches I noticed while fixing the bug, where emacsclient wrote to the
> terminal even though it was started with a trailing '&'.

Hi Paul,

Many thanks for fixing this issue! This breakage made emacs completely
unusable using my emacsclient .. & flow. But now I confirm things to
be working once again after building using the b1d7f19 commit.

Just for reference, I am using this bash script as a wrapper to launch
emacsclient: https://ptpb.pw/QGes/bash

Being C-illiterate, I am astounded how my bug report verbiage result
in the fix in https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=2f985977f691a37a6d45298128b88d0cefcc93a1.

I don't understand the fix or the commit message at all. But thanks
again for resolving one of my RHEL 6.x specific issues once again!



      reply	other threads:[~2018-12-06 19:29 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
2018-12-05 19:17   ` Kaushal Modi
2018-12-06 18:52 ` Paul Eggert
2018-12-06 19:29   ` Kaushal Modi [this message]

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='CAFyQvY3Yo8ON08pOPAqnJiOQ=-y=zt7kMkXj-h5XFkRdPm-==Q@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.