emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

customize-rouge output with emacs -q --no-site-file


From: Lennart Borgman
Subject: customize-rouge output with emacs -q --no-site-file
Date: Fri, 4 Feb 2005 17:03:07 +0100

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 via email to

[Prev in Thread] Current Thread [Next in Thread]