unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Subject: customize-rouge output with emacs -q --no-site-file
Date: Fri, 4 Feb 2005 17:03:07 +0100	[thread overview]
Message-ID: <00cb01c50ad3$5f978570$0200a8c0@sedrcw11488> (raw)

Below is a list of the variables that customize-rouge shows when emacs is
started with emacs -q --no-site-file. It contains on my pc 32 variables.

Many of them are maybe easy to fix?  Perhaps could Customize in some cases
just be told that everything is ok? Perhaps should the "standard value" in
some cases be set to do that? Could such fixes be done before starting
`site-run-file'? At this point the values should be set. Should the current
values at this point not be the standard values?

For some options (like blink-cursor) this seems to be the way to do it.
There is a comment in startup.el saying it can not be done in the defcustom.
The same seems to be the case for tooltip-mode. For other options it should
perhaps be done differently.


*** customize-rouge options with emacs -q --no-site-file:
baud-rate
blink-cursor
completion-ignored-extensions
current-language-environment
custom-unlispify-tag-names
debug-ignored-errors
default-frame-alist
default-input-method
encoded-kbd-mode
eol-mnemonic-mac
eol-mnemonic-unix
exec-path
file-coding-system-alist
find-file-hook
find-file-visit-truename
help-event-list
keyboard-coding-system
menu-bar-mode
minibuffer-history-case-insensitive-variables
minibuffer-prompt-properties
mode-line-format
mouse-wheel-mode
normal-erase-is-backspace
pop-up-frame-function
same-window-buffer-names
same-window-regexps
selection-coding-system
shell-file-name
site-run-file
special-display-function
text-mode-hook
tooltip-mode

             reply	other threads:[~2005-02-04 16:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 16:03 Lennart Borgman [this message]
2005-02-04 19:14 ` customize-rouge output with emacs -q --no-site-file 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
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='00cb01c50ad3$5f978570$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    /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).