From: Richard Stallman <rms@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: lekktu@gmail.com, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: "Attempt to modify read-only object" error with set-frame-configuration
Date: Wed, 26 Dec 2007 00:28:42 -0500 [thread overview]
Message-ID: <E1J7Oos-0003q4-MS@fencepost.gnu.org> (raw)
In-Reply-To: <47702D13.8050806@gmx.at> (message from martin rudalics on Mon, 24 Dec 2007 23:05:07 +0100)
! (if (eq initial-window-system 'w32)
! (list (cons 'window-system initial-window-system)
! (cons 'visibility t)
! frame-initial-frame-alist)
! (list (cons 'window-system initial-window-system)
! frame-initial-frame-alist)))
Does that really need to be conditional on Windows?
If you specify visibility here on all systems,
that would be simpler. Would it break anything?
Please install your patch, correcting that if appropriate.
There is still a mystery why visibility's cons cell is pure
without this, but we may as well fix the bug.
If you want to figure out the mystery, then take out this change, put
a breakpoint at the start of the primitive that creates the frame, and
see if its args include a cons cell for visibility. If yes, is that
pure? If yes, where was it made? If it doesn't have a cons cell for
visibility, then step thru it and see where it puts visibility into
the alist and how.
next prev parent reply other threads:[~2007-12-26 5:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 21:32 "Attempt to modify read-only object" error with set-frame-configuration martin rudalics
2007-12-19 21:47 ` Andreas Schwab
2007-12-19 22:09 ` Stephen Berman
2007-12-19 23:18 ` Johan Bockgård
2007-12-19 23:59 ` Juanma Barranquero
2007-12-20 9:59 ` martin rudalics
2007-12-20 13:09 ` Juanma Barranquero
2007-12-20 16:02 ` martin rudalics
2007-12-20 17:11 ` Juanma Barranquero
2007-12-20 18:36 ` martin rudalics
2007-12-20 23:06 ` Juanma Barranquero
2007-12-22 19:06 ` Eli Zaretskii
2007-12-23 15:32 ` Richard Stallman
2007-12-25 21:01 ` Eli Zaretskii
2007-12-26 5:29 ` Richard Stallman
2007-12-24 22:05 ` martin rudalics
2007-12-25 4:11 ` Eli Zaretskii
2007-12-25 9:23 ` martin rudalics
2007-12-25 20:59 ` Eli Zaretskii
2007-12-25 21:50 ` martin rudalics
2007-12-26 5:28 ` Richard Stallman [this message]
2007-12-26 7:00 ` YAMAMOTO Mitsuharu
2007-12-26 8:49 ` martin rudalics
2007-12-26 21:26 ` Richard Stallman
2007-12-26 19:09 ` Bob Rogers
2007-12-24 22:53 ` martin rudalics
2007-12-25 4:07 ` Eli Zaretskii
2007-12-25 9:27 ` martin rudalics
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=E1J7Oos-0003q4-MS@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rudalics@gmx.at \
/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).