From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14841@debbugs.gnu.org
Subject: bug#14841: Frames created invisible have their visibility parameter set to t
Date: Mon, 29 Jul 2013 00:08:52 +0200 [thread overview]
Message-ID: <CAAeL0SQBT6+V_sm7EFsYuL-iG6BmsEbNmDxURKxc4gdc4Tp3rw@mail.gmail.com> (raw)
In-Reply-To: <83wqodzll1.fsf@gnu.org>
>> > So can we decide that the patch can be committed?
>>
>> Yes, go ahead, please.
>
> Done as trunk revision 113555.
Unfortunately, this patch causes another bug that I didn't detect at the time.
emacs -Q --eval "(setq initial-frame-alist '((minibuffer)))" -f
toggle-debug-on-quit
Not always, but in most cases this will loop. Interrupting with Ctrl-G
produces this backtrace:
Debugger entered--Lisp error: (quit)
sleep-for(1)
frame-notice-user-settings()
#[0 "\306 ... "]()
funcall(#[0 "\306 ... "])
normal-top-level()
next prev parent reply other threads:[~2013-07-28 22:08 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 15:14 bug#14841: Frames created invisible have their visibility parameter set to t Juanma Barranquero
2013-07-11 15:33 ` Eli Zaretskii
2013-07-11 15:39 ` Juanma Barranquero
2013-07-11 16:29 ` Eli Zaretskii
2013-07-11 16:54 ` Juanma Barranquero
2013-07-14 16:52 ` Eli Zaretskii
2013-07-14 17:02 ` Juanma Barranquero
2013-07-19 13:04 ` Juanma Barranquero
2013-07-20 12:56 ` Eli Zaretskii
2013-07-20 13:01 ` Juanma Barranquero
2013-07-20 13:39 ` Eli Zaretskii
2013-07-20 14:54 ` Juanma Barranquero
2013-07-20 15:48 ` Eli Zaretskii
2013-07-20 16:09 ` Eli Zaretskii
2013-07-20 16:57 ` Juanma Barranquero
2013-07-20 17:37 ` Eli Zaretskii
2013-07-23 23:36 ` Juanma Barranquero
2013-07-20 16:35 ` Juanma Barranquero
2013-07-20 12:53 ` Eli Zaretskii
2013-07-20 12:55 ` Juanma Barranquero
2013-07-24 16:50 ` Juanma Barranquero
2013-07-25 19:17 ` Eli Zaretskii
2013-07-25 19:35 ` Eli Zaretskii
2013-07-25 20:17 ` Juanma Barranquero
2013-07-26 0:11 ` Juanma Barranquero
2013-07-26 6:32 ` Eli Zaretskii
2013-07-26 9:37 ` Juanma Barranquero
2013-07-26 10:01 ` Eli Zaretskii
2013-07-26 10:01 ` Eli Zaretskii
2013-07-27 12:43 ` martin rudalics
2013-07-27 13:03 ` Eli Zaretskii
2013-07-27 13:30 ` martin rudalics
2013-07-27 15:31 ` Eli Zaretskii
2013-07-28 8:40 ` martin rudalics
2013-07-28 14:59 ` Eli Zaretskii
2013-07-29 7:54 ` martin rudalics
2013-07-29 15:26 ` Eli Zaretskii
2013-07-29 16:58 ` martin rudalics
2013-07-29 18:37 ` Eli Zaretskii
2013-07-30 9:12 ` martin rudalics
2013-07-30 15:31 ` Eli Zaretskii
2013-07-30 16:16 ` martin rudalics
2013-07-30 14:11 ` martin rudalics
2013-07-30 15:52 ` Eli Zaretskii
2013-07-31 8:33 ` martin rudalics
2013-08-06 8:56 ` martin rudalics
2013-07-28 22:08 ` Juanma Barranquero [this message]
2013-07-29 16:36 ` Eli Zaretskii
2013-07-26 6:31 ` Eli Zaretskii
2013-07-26 9:37 ` Juanma Barranquero
2013-07-11 16:54 ` Glenn Morris
2013-07-11 16:55 ` Juanma Barranquero
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=CAAeL0SQBT6+V_sm7EFsYuL-iG6BmsEbNmDxURKxc4gdc4Tp3rw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=14841@debbugs.gnu.org \
--cc=eliz@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 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).