>>>> "Karr" == Karr, David
<david.karr(a)cacheflow.com> writes:
Karr> I'm not having much luck here.
OK, first try courier OBLIQUE (-*-courier-*-o-*), not italic.
Monospace fonts normally don't have italic versions (I should have
remembered that). If you don't have that, your X installation is
deficient. Seems unlikely. Check with xfontsel, though. If you have
it, try using an explicit specification of courier as family and
italic ON in Customize. AFAICT Customize is smart enough to fall back
on oblique if italic is unavailable. Set but don't Save it yet.
Restore your custom.el, restart, then customize. If that works, you
should be able to go back to using Custom for everything. (There's no
reason not to use Custom for non-faces.)
If that doesn't work, start xemacs -vanilla. Start a shell buffer.
Do some work in it (list directories or something). Make sure
font-lock is on. In my XEmacs 21.4.4, the family is courier, the
prompts are red, commands black, arguments blue, and output oblique.
What do you get? If you don't get that, maybe there is an issue with
your X server or X font server. If you do ...
Split the window with C-x 2. Do M-x customize-face RET
shell-output-face RET. You should have the shell buffer in one window
and the customize buffer in the other. Changes you make to the face
in the customize buffer should be reflected immediately on activating
the Set button. Use fonts you know you have versions of (eg, by using
xfontsel). Note that the checkboxes activate the specification for
italic, etc, but do not change their value. You need to change italic
from off to on by clicking on the word "italic".
In the customize window, visit your init.el file which I assume by now
contains a (set-face-font 'shell-output-face ...) expression. I hope
it's different from the font currently used for output in the shell
buffer, or you won't see anything change. Execute it with C-x C-e.
This should be reflected immediately in existing shell output in the
shell buffer.
Finally, do a global customization (with menu edit faces). This
sholdn't have different results from the one-face customization, but
I'd like to check. (Faces have complex inheritance relationships, so
it's possible that changing a lot of faces at once could mess
something up.)
Karr> I'm not sure exactly what you're suggesting in the
Karr> paragraph beginning "Sorry, untested suggestion ...".
I just meant that I should have known that the face would be undefined
if I had tested the recipe.
--
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091
_________________ _________________ _________________ _________________
What are those straight lines for? "XEmacs rules."