unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: customize-rouge output with emacs -q --no-site-file
Date: Fri, 4 Feb 2005 21:51:21 -0600 (CST)	[thread overview]
Message-ID: <200502050351.j153pLL14720@raven.dms.auburn.edu> (raw)
In-Reply-To: <004501c50b07$6690f620$0200a8c0@sedrcw11488> (lennart.borgman.073@student.lu.se)

I believe that the patch below is the correct way to do what you are
trying to do.  It could at the very best be _part_ of a solution.  It
does not solve the other problems I referred to, only the "Erase
Customization" one.  As before, only provided _for experimentation
purposes_.  _Not_ meant to be installed in CVS.  When trying out code
experimenting with Custom, always make sure your .emacs, or whatever
your custom-file is, is properly backed up.

With this new code, I get 3 options after `emacs -q' and
`M-x customize-rogue":

debug-ignored-errors, default-frame-alist and user-mail-address.

I believe that I understand the last two as local peculiarities.
`debug-ignored-errors' is very special.

===File ~/startup-diff======================================
*** startup.el	28 Dec 2004 09:50:38 -0600	1.337
--- startup.el	04 Feb 2005 20:59:49 -0600	
***************
*** 785,790 ****
--- 785,797 ----
                   (cdr tool-bar-lines)
                   (not (eq 0 (cdr tool-bar-lines)))))))
  
+   (mapatoms
+    (lambda (symbol)
+      (and (default-boundp symbol)
+ 	  (get symbol 'standard-value)
+ 	  (put symbol 'standard-value
+ 	       (list (custom-quote (default-value symbol)))))))
+ 
    (let ((old-scalable-fonts-allowed scalable-fonts-allowed)
  	(old-font-list-limit font-list-limit)
  	(old-face-ignored-fonts face-ignored-fonts))
============================================================

  parent reply	other threads:[~2005-02-05  3:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 16:03 customize-rouge output with emacs -q --no-site-file Lennart Borgman
2005-02-04 19:14 ` Lennart Borgman
2005-02-04 21:57   ` Lennart Borgman
2005-02-04 22:17   ` Lennart Borgman
2005-02-04 23:48     ` Luc Teirlinck
2005-02-05  0:47       ` Luc Teirlinck
2005-02-05 17:39         ` Richard Stallman
2005-02-05  0:03     ` Luc Teirlinck
2005-02-05  0:06     ` Luc Teirlinck
2005-02-05 17:39       ` Richard Stallman
2005-02-05  1:56     ` Luc Teirlinck
2005-02-05  3:51     ` Luc Teirlinck [this message]
2005-02-05  9:08       ` Lennart Borgman
2005-02-05 14:51         ` Luc Teirlinck
2005-02-06 12:42           ` Richard Stallman
2005-02-06 19:54             ` Luc Teirlinck
2005-02-05 19:06         ` Luc Teirlinck
2005-02-05 19:52           ` Lennart Borgman
2005-02-05 21:16             ` Luc Teirlinck
2005-02-07 20:51   ` Richard Stallman
2005-02-07 21:27     ` Lennart Borgman

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=200502050351.j153pLL14720@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@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).