From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: "Attempt to modify read-only object" error with set-frame-configuration Date: Tue, 25 Dec 2007 10:27:27 +0100 Message-ID: <4770CCFF.5050500@gmx.at> References: <47698DF5.2080106@gmx.at> <4770387D.2040102@gmx.at> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1198574962 20524 80.91.229.12 (25 Dec 2007 09:29:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 25 Dec 2007 09:29:22 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 25 10:29:35 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1J766Q-0004h7-E2 for ged-emacs-devel@m.gmane.org; Tue, 25 Dec 2007 10:29:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J7665-0007Ib-V1 for ged-emacs-devel@m.gmane.org; Tue, 25 Dec 2007 04:29:14 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1J7651-00068p-1K for emacs-devel@gnu.org; Tue, 25 Dec 2007 04:28:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J764y-00065E-Rp for emacs-devel@gnu.org; Tue, 25 Dec 2007 04:28:06 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J764y-00064p-Lz for emacs-devel@gnu.org; Tue, 25 Dec 2007 04:28:04 -0500 Original-Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1J764x-0002Gr-Az for emacs-devel@gnu.org; Tue, 25 Dec 2007 04:28:04 -0500 Original-Received: (qmail invoked by alias); 25 Dec 2007 09:28:01 -0000 Original-Received: from unknown (EHLO [62.47.36.201]) [62.47.36.201] by mail.gmx.net (mp016) with SMTP; 25 Dec 2007 10:28:01 +0100 X-Authenticated: #14592706 X-Provags-ID: V01U2FsdGVkX1+GodUgNGyGqdsLfT2NvVIvFyJREgFu9ipcvmGdD4 C7plprV6m9RwNo User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en In-Reply-To: X-Y-GMX-Trusted: 0 X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:85441 Archived-At: > I think this means that your previous patch and the one you suggest > here is not the correct solution. We must first understand what is > the problem with initial frame parameters on w32, and what causes that > problem. I think something like this patch is needed to avoid that the fringes creep into `initial-frame-alist' and `default-frame-alist'. Otherwise, customizing these is broken. And the fringes show up multiple times in `frame-parameters' due to the simple-minded (setq frame-initial-frame-alist (append initial-frame-alist default-frame-alist nil)) in `frame-initialize'.