GNU bug report logs - #31048
27.0.50; With -daemon, "emacsclient -c" on a modified file fails to display frame

Previous Next

Package: emacs;

Reported by: Bruce Stephens <bruce.stephens <at> isode.com>

Date: Tue, 3 Apr 2018 16:11:02 UTC

Severity: normal

Found in version 27.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Bruce Stephens <bruce.stephens <at> isode.com>
Cc: bug-gnu-emacs <at> gnu.org
Subject: Re: 27.0.50;
 With -daemon, "emacsclient -c" on a modified file fails to
 display frame
Date: Thu, 07 Nov 2019 19:20:52 +0200
> From: Bruce Stephens <bruce.stephens <at> isode.com>
> Date: Tue, 03 Apr 2018 17:10:25 +0100
> 
> On GNU/Linux (with gtk+), after "emacs -Q -daemon", if I do "emacsclient
> -c /tmp/foo" (for some existing /tmp/foo) then exit that frame (so the
> server still has /tmp/foo in a buffer but has no visible frames), then
> "touch /tmp/foo" and try to repeat "emacsclient -c /tmp/foo" the
> emacsclient hangs and no frame is displayed.
> 
> I would expect a frame to appear with "Revert buffer from file
> /tmp/foo?".
> 
> The commit that caused the change seems to be the following one, and
> reverting that fixes the hang (and returns the behaviour I was
> expecting):
> 
> commit 49fc040077b33bd1e78ee425575e76329b772a41 (tag: bad, refs/bisect/bad)
> Author: Aaron Jensen <aaronjensen <at> gmail.com>
> Date:   Fri Feb 16 17:43:04 2018 +0200
> 
>     Don't flash previous buffer when connecting with emacsclient

Thanks, I've now reverted that commit.  Please see that your problem
is solved.




This bug report was last modified 5 years and 195 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.