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: Thu, 6 Dec 2018 14:29:23 -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 1544124726 14270 195.159.176.226 (6 Dec 2018 19:32:06 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 6 Dec 2018 19:32:06 +0000 (UTC) Cc: Emacs developers To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Dec 06 20:32:02 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 1gUzNR-0003YO-SX for ged-emacs-devel@m.gmane.org; Thu, 06 Dec 2018 20:32:02 +0100 Original-Received: from localhost ([::1]:42709 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUzPY-0003QB-LA for ged-emacs-devel@m.gmane.org; Thu, 06 Dec 2018 14:34:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47688) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gUzLX-0007Qv-7E for emacs-devel@gnu.org; Thu, 06 Dec 2018 14:30:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gUzLW-00084I-AM for emacs-devel@gnu.org; Thu, 06 Dec 2018 14:30:03 -0500 Original-Received: from mail-lj1-x241.google.com ([2a00:1450:4864:20::241]:37959) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gUzLW-00083e-1R for emacs-devel@gnu.org; Thu, 06 Dec 2018 14:30:02 -0500 Original-Received: by mail-lj1-x241.google.com with SMTP id c19-v6so1464999lja.5 for ; Thu, 06 Dec 2018 11:30:01 -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 :cc; bh=z9pffYEn6MOHR1N22wedkC2K5byKv1l96sKoFDB5un8=; b=CuXAX8AExDkUwydipQtRESHYHKo3oAt9TfkVhwotggUo+YEomh83WXNC4tuxjmG7pl ptfnMpagTl2xforoaU5CQ5JhAPDAmOq/xio/ffut3GuwrWElGq2BpuohrLX1tb21y5ci xe1hPqE1ETVcyuebQFFEmw7BuEGX5XY4lDpPXmUgYGMfOMOm60cIhhaustuwj97GOHT5 WoUB+NAEzIcsPQXymAWm8K4Hy7EsFmzBQ5xE6EbOMIcy4w5QdmGy/nCKfPj2WxDvYi8W EqavKllC86pwgkYnoxYU22b6opo6Cwy5+TYsroGfknw5G8p8GLkHqQ1/B459VG8dUMEa ia9g== 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:cc; bh=z9pffYEn6MOHR1N22wedkC2K5byKv1l96sKoFDB5un8=; b=DNXrDr4HK4tytWqmRutulTluJbAVQciPlERH3g5HBPdyQN76gICsfXR/LrOp4kTMcq SRSbi4n0QUdLHETPA7jxBBYxDqijNrdUh3yb3CzQth2NZd3oXlgpyUjO7HmiWRmdRX0g Wi+9ucdql0ighAAkEm/Y7EDJNx1usYxHBApfHZhbTk/59sNt/3xjuMJ0qXR2hAOxpj0Z Bvp6WQW3BYs0/j6zGNDlqwFPgL3+DZcLNIy27F66uxLkXvu0xqk2chC8FLSL5b1016AG J3Yq2H+RqBbE6QKs/lYpCAnJI0e2YahOXKPbY0hl9s+QqprJJVzkOpKieqNgueiQUgW3 0zdg== X-Gm-Message-State: AA+aEWYWLrQtHVUcJ5/8e8aMaJImW4gW9YJTvxTiAYmhtWvKJI2Mav32 7a3SuaaPjx/l1UUWx02WfnFqseCpgM7cip9wzTE= X-Google-Smtp-Source: AFSGD/V+AzDRwlU5pbYndxwJTZ6nd8/shwzvVIGUcXGO7Rjda7q3sVNMSoXSx4VzVnrxh9jAllsBWWEhN8WRBh4YNpo= X-Received: by 2002:a2e:94ce:: with SMTP id r14-v6mr19326518ljh.34.1544124600293; Thu, 06 Dec 2018 11:30:00 -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::241 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:231695 Archived-At: On Thu, Dec 6, 2018 at 1:52 PM Paul Eggert 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!