all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 4562@emacsbugs.donarmstrong.com
Subject: bug#4562: 23.1; Customize State button problems
Date: Mon, 28 Sep 2009 01:41:05 -0400	[thread overview]
Message-ID: <jwv8wfzbpgt.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <75988BB2DE8C4DE6A16228719FF4E6EF@us.oracle.com> (Drew Adams's message of "Sat, 26 Sep 2009 11:37:07 -0700")

> The State text says "CHANGED outside Customize; operating on it here
> may be unreliable.", which is untrue. This is immediately after using
> `emacs -Q'.

You misunderstand: "CHANGED outside Customize" doesn't mean "You changed
it", but instead it means "some Lisp code somewhere changed it without
telling Customize".  That Lisp code could be in your .emacs, but
not necesarily.  I hope this makes the rest of the behavior a bit more
understable (tho probably not completely clear since it seems some part
are indeed odd).

So what you have here is simply a bug where Emacs's startup code
modifies default-frame-alist without telling Customize about it.
IIUC it's not easy to fix it, because some of those changes are things
which shoujldn't be saved in the Custom version of default-frame-alist
(they are dynamically set at startup depending on your window-system
and/or command-line args).  I guess basically what it means is that
default-frame-alist shouldn't be a defcustom becaude we don't know how
to let Custom handle it correctly.


        Stefan






  reply	other threads:[~2009-09-28  5:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 18:37 bug#4562: 23.1; Customize State button problems Drew Adams
2009-09-28  5:41 ` Stefan Monnier [this message]
2009-09-28  8:54   ` Drew Adams
2011-07-13 13:57   ` Lars Magne Ingebrigtsen
2011-07-13 15:25     ` Drew Adams
2011-07-13 15:59     ` Chong Yidong

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=jwv8wfzbpgt.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=4562@emacsbugs.donarmstrong.com \
    --cc=drew.adams@oracle.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 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.