all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: other-frame-window.el --daemon mode bug?
Date: Mon, 27 Nov 2017 21:41:59 +0200	[thread overview]
Message-ID: <83a7z75x14.fsf@gnu.org> (raw)
In-Reply-To: <87fu8zzhhl.fsf@withouthat.org> (message from Thorsten Bonow on Mon, 27 Nov 2017 19:47:18 +0100)

> From: Thorsten Bonow <thorsten.bonow@withouthat.org>
> Date: Mon, 27 Nov 2017 19:47:18 +0100
> 
> emacs -Q --daemon
> 
> Connect to the server:
> 
> emacsclient -c -n
> 
> In the '*scratch*' buffer enter and eval:
> 
> (require 'other-frame-window "/path/to/other-frame-window.el")
> (other-frame-window-mode t)
> 
> 'C-x 9 b' is supposed to open a buffer (defaults to the "*Messages*" buffer) in
> another frame.  On pressing return, Emacs becomes stuck in the minibuffer.  The
> command times out after a while and can be interrupted with 'C-g', but no frame
> is created.
> 
> After firing up Emacs with 'emacs -Q', everything works as expected.
> 
> Can someone please confirm this?

Confirmed.

> The library comes as a GNU package, not included in my Emacs[1].  In case it's
> a bug, can I just report it as an Emacs bug?

As someone who gets to read, triage, and then handle at least some of
those bug reports, I'd prefer that you first reported this to the
author of the package.

(A cursory look I took seems to indicate that the problem is with the
way this package selects a frame to switch to: it attempts to select
the initial frame created by the daemon, which is not usable for
displaying anything.  But I might be missing something.)

Thanks.



  parent reply	other threads:[~2017-11-27 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 18:47 other-frame-window.el --daemon mode bug? Thorsten Bonow
2017-11-27 18:56 ` Stefan Monnier
2017-11-27 19:41 ` Eli Zaretskii [this message]
     [not found] ` <mailman.4690.1511811741.27995.help-gnu-emacs@gnu.org>
2017-11-27 20:06   ` Thorsten Bonow

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=83a7z75x14.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.