Re: Unreadable buffer names in Emacs 23.2

[Android Eve]

Thank you, Tim. I did exactly as you suggested and it works very well.
Modifying .emacs via the Options menu (which is a totally new concept
to me...), resulted in appending the following 2 lines:

(custom-set-faces
'(default ((t (:inherit nil :stipple nil :background
"Black" :foreground "LightGray" :inverse-video nil :box nil :strike-
through nil :overline nil :underline nil :slant normal :weight
normal :height 90 :width normal :foundry "outline" :family "Lucida
Console")))))

I must admit that although I can't live without Emacs, I find it
frustrating to have to "fix" my .emacs every time I upgrade to a new
version. Is there a way to create a .emacs that will never break?
(i.e. forward-compatible)

On Aug 15, 12:43 am, Tim X <t...@nospam.dev.null> wrote:
> Android Eve <androi...@gmx.com> writes:
> > On Aug 14, 12:16 am, Tim X <t...@nospam.dev.null> wrote:
>
> >> Most likely, a custom setting for the
> >> minibuffer prompt and maybe an Xresource setting for the menu font.
>
> > OK - I found the offending lines in my .emacs (both statements need to
> > be commented out!):
>
> >      (setq default-frame-alist
> >        (cons '(font . "-*-Lucida Console-normal-r-*-*-12-*-*-*-c-*-*-
> > iso8859-1")
> >              default-frame-alist))
> >      (set-default-font
> >       "-*-Lucida Console-normal-r-*-*-12-*-*-*-c-*-*-iso8859-1")
>
> > Now I need to find out why.
>
> Something which may help is that if your using emacs 23 (or later), you
> can probably set your font from the options menu. Try that and see if
> you get a better result. Don't forget to save your options.
>
> The advantage of this approach is that you should only be presented with
> fonts that are available or which emacs can find. It will also result in
> a default face definition in your .emacs custom-faces section. You cold
> then use that to define the fonts in the frame alists if you want,
> however, it may not be necessary.
>
> Tim
> --
> tcross (at) rapttech dot com dot au