unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bruce Stephens <bruce.stephens@isode.com>
Cc: 31048@debbugs.gnu.org
Subject: bug#31048: 27.0.50; With -daemon, "emacsclient -c" on a modified file fails to display frame
Date: Thu, 07 Nov 2019 19:20:52 +0200	[thread overview]
Message-ID: <83o8xneh6z.fsf@gnu.org> (raw)
In-Reply-To: <80zi2k6zke.fsf@tinier.isode.net> (message from Bruce Stephens on Tue, 03 Apr 2018 17:10:25 +0100)

> From: Bruce Stephens <bruce.stephens@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@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.





  reply	other threads:[~2019-11-07 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 16:10 bug#31048: 27.0.50; With -daemon, "emacsclient -c" on a modified file fails to display frame Bruce Stephens
2019-11-07 17:20 ` Eli Zaretskii [this message]
2019-11-08 11:54   ` Bruce Stephens
2019-11-08 13:41     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83o8xneh6z.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31048@debbugs.gnu.org \
    --cc=bruce.stephens@isode.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).