--- Begin Message ---
Subject: |
Re: GREAT COLORS IN TEXT MODE! but default foreground colors not respected |
Date: |
14 Nov 2001 21:19:02 -0600 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 |
Subject: Re: GREAT COLORS IN TEXT MODE! but default foreground colors not
respected
To: Eli Zaretskii <eliz@is.elta.co.il>
Bcc: ortmann
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On 13 Nov 2001, Daniel Ortmann wrote:
>> The system setup file /etc/rc.conf as the following color
>> redefinitions: allscreens_flags="-m on VGA_80x50 brown black"
>> This is basically an "amber" foreground which is easy on the eyes.
>> When emacs starts up the foreground colors are apparently white and
>> an extrabright white, hard on the eyes.
>> SOMETIMES after a screen redraw my default colors show through.
>> Eventually enough keyboard actions are used and the colors go back to
>> harsh white on black.
> Sorry, I don't understand what are you saying, perhaps because I don't
> know enough about FreeBSD console magic in rc.conf.
It is simple; there is really almost nothing to "know". The variable
allscreens_flags gets passed to "vidcontrol" and runs something like
this: vidcontrol brown black
The standard foreground color is brown and the background black in text
mode, i.e. on the virtual terminal syscons console windows.
> When Emacs starts on the tty, it doesn't change the colors,
Well, it *does** change the colors in text mode. I think you meant to
say it does not *intent** to change them.
> because there's no way (AFAIK) to query the tty about the current
> colors. So the default Emacs display on a tty should normally use the
> same colors you had before invoking Emacs.
Right, it should. Well, that is perhaps not completely correct either
since my normal windows don't use all of the fancy and interesting
colors I now see.
> But you seem to say that Emacs comes up with non-default colors, even
> if you invoke "emacs -q --no-start-file", is that right?
I had not thought to try that ... (time passes)
... You've hit on the trail to the answer!
Ok, the "emacs -q --no-site-file" command shows my desired colors. The
variable window-system is still nil as expected. The customize-face
command shows 400+ lines of faces without a window-system, surprising
me.
I just added and "if" around some color defaults:
(if window-system
(let ((frame-parameters '((foreground-color . "gray55")
(background-color . "gray22")
(cursor-color . "coral")
(mouse-color . "lightgreen")
(border-color . "gray5"))))
(setq default-frame-alist
(append frame-parameters default-frame-alist))
(setq initial-frame-alist
(append frame-parameters initial-frame-alist)))
)
> If so, the only way I could explain this is that some command Emacs
> sends to the terminal during startup somehow has a side effect of
> changing the colors. Please try to find out what command is that
> (using open-termscript, as described in the "Checklist" node of the
> Emacs manual would be a useful technique here).
> But please do try "emacs -q --no-start-file" first, it's possible that
> sime of your customizations or site-wide defaults modify the colors.
You can close this problem out. It is a user error exposed by new emacs
text mode functionality.
Thank you!
--
Daniel Ortmann, 2414 30 Av NW, #D, Rochester, MN 55901
ortmann@isl.net (h) / 507.288.7732 (h)
dortmann@lsil.com (w) / 507.529.3887 (w)
--- End Message ---