From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: [elpa] master b843370: * packages/other-frame-window/other-frame-window.el: New single-file package.
Date: Mon, 17 Aug 2015 17:17:09 -0500 [thread overview]
Message-ID: <864mjxtva2.fsf@stephe-leake.org> (raw)
In-Reply-To: <jwvr3n2qac2.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Mon, 17 Aug 2015 10:07:46 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> If I do C-x 5 f, a new frame opens if needed (if I have only one frame to
>> begin with).
>> But if I do C-x 9 f, the buffer opens in a second frame only if I have 2
>> frames to begin with. If I had just one frame open, C-x 9 f seems to do
>> nothing. Is that by design?
>
> No. The design is for C-x 9 f to behave pretty much exactly like C-x 5 f.
> But indeed, I can reproduce here (with -Q) the problem you describe, so
> the problem is not in your config.
Hmm. It works here:
emacs -Q
In *scratch*:
(package-initialize)
(require 'other-frame-window)
(other-frame-window-mode 1)
C-x 9 f ~/.emacs.d/elpa/other-frame-window-1.0.1/other-frame-widow.el
Opens in a new frame.
I'm on Windows 8, Emacs built with Mingw 64 bit.
The require step should not be needed; it's missing an autoload cookie.
--
-- Stephe
next prev parent reply other threads:[~2015-08-17 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150814050452.7700.48557@vcs.savannah.gnu.org>
[not found] ` <E1ZQ7Aj-00020t-09@vcs.savannah.gnu.org>
2015-08-14 17:01 ` [elpa] master b843370: * packages/other-frame-window/other-frame-window.el: New single-file package Stefan Monnier
2015-08-15 17:39 ` Stephen Leake
2015-08-15 21:50 ` Stefan Monnier
2015-08-17 13:19 ` Kaushal
2015-08-17 14:07 ` Stefan Monnier
2015-08-17 22:17 ` Stephen Leake [this message]
2015-08-18 5:15 ` Stefan Monnier
2015-08-18 10:04 ` Stephen Leake
2015-08-19 17:48 ` Stefan Monnier
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=864mjxtva2.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--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.