From: npostavs@users.sourceforge.net
To: Alex 'QWxleA' Poslavsky <qwxlea@gmail.com>
Cc: 25521@debbugs.gnu.org
Subject: bug#25521: 26.0.50; After (make-frame '((name . "foo"))) (select-frame-by-name "foo") doesn't see the frame
Date: Tue, 24 Jan 2017 18:35:25 -0500 [thread overview]
Message-ID: <87pojct4jm.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87a8agrwwx.fsf@gmail.com> (Alex Poslavsky's message of "Tue, 24 Jan 2017 23:05:34 +0200")
Alex 'QWxleA' Poslavsky <qwxlea@gmail.com> writes:
> The following, used as ~/.emacs.d/init.el:
>
> (require 'org)
>
> (defun qw ()
> (interactive)
> "Create a new capture frame helper-function"
> (make-frame '((name . "foo")
> (width . 120)
> (height . 25)))
> (select-frame-by-name "foo")
> (org-agenda))
>
> works on emacs24, but not on a current git, build 24 Jan 2017. The
> error-message is: select-frame-by-name: There is no frame named ‘foo’
>
> I left everything else, but it doesn't look helpful.
I guess this is more fallout from my recent fix for #24091 [1: 6a788d2].
The following simplification of your `qw' function works for me:
(defun qw ()
(interactive)
"Create a new capture frame helper-function"
(select-frame (make-frame '((width . 120)
(height . 25))))
(org-agenda))
1: 2017-01-20 23:36:26 -0500 6a788d2fc18c23dcfc5d0352649b2f690e9cbff7
Don't wait for frame to become visible
next prev parent reply other threads:[~2017-01-24 23:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 21:05 bug#25521: 26.0.50; After (make-frame '((name . "foo"))) (select-frame-by-name "foo") doesn't see the frame Alex 'QWxleA' Poslavsky
2017-01-24 23:35 ` npostavs [this message]
2017-01-25 3:37 ` Eli Zaretskii
2017-01-25 3:31 ` Eli Zaretskii
2017-01-25 6:47 ` Alex (QWxleA)
2017-01-25 23:43 ` npostavs
2017-01-26 11:40 ` Alex (QWxleA)
2017-01-26 14:37 ` npostavs
2017-01-26 15:48 ` Alex (QWxleA)
2017-01-27 2:02 ` npostavs
2017-01-27 7:56 ` Eli Zaretskii
2017-06-30 3:08 ` npostavs
2017-06-30 6:09 ` Eli Zaretskii
2017-06-30 6:52 ` martin rudalics
2017-09-01 3:13 ` npostavs
2017-09-01 6:56 ` Eli Zaretskii
2017-09-01 13:02 ` martin rudalics
2017-09-01 13:41 ` npostavs
2017-09-01 15:45 ` martin rudalics
2017-09-26 2:54 ` Noam Postavsky
2017-09-27 8:11 ` martin rudalics
2017-09-27 12:13 ` Noam Postavsky
2017-09-29 8:33 ` martin rudalics
2017-09-29 12:48 ` Noam Postavsky
2017-09-29 18:19 ` martin rudalics
2017-09-29 22:47 ` Noam Postavsky
2017-09-29 13:39 ` Eli Zaretskii
2017-10-14 2:14 ` Noam Postavsky
2017-10-14 8:36 ` martin rudalics
2017-10-15 18:22 ` Noam Postavsky
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=87pojct4jm.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25521@debbugs.gnu.org \
--cc=qwxlea@gmail.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).