From: "BillJosephson" <billjosephson@hotmail.com>
Subject: Re: fatal font problem with emacs
Date: 28 Oct 2006 11:11:50 -0700 [thread overview]
Message-ID: <1162059110.456641.280210@h48g2000cwc.googlegroups.com> (raw)
In-Reply-To: <mailman.228.1161768081.27805.help-gnu-emacs@gnu.org>
Peter Dyballa wrote:
> Am 25.10.2006 um 10:14 schrieb BillJosephson:
>
> > I don't see .xinitrc. But, I don't know what to do with all this.
> > Where
> > to go next, so to speak.
>
> You have somewhere a template for ~/.xinitrc on your system, maybe
> in /etc/X11/xinit ...
>
> When the X server is launched it looks for ~/.xinitrc. If the file
> exists it executes it. By this means you can correct and extend the
> font path, set other time constants or repeat rates or acceleration
> for keyboard or mouse, launch useful X clients and particularly
> choose a Window Manager.
>
> The UNIX help system, i.e. the man and apropos (or man -k) commands,
> can explain more. More resources can be found on the Internet.
>
> If you don't want to learn so much, you can check the look of a font
> in X11 with xfd (or xfontsel) and then invoke GNU Emacs with 'emacs -
> fn <your choice of font> &'. Or you simply filter the output of
> xlsfonts. This way you can find whether the fonts reported exist on
> your system. If they don't, you can select another one to pass on the
> command line.
>
> --
> Greetings
>
> Pete
>
> "A mathematician is a machine that turns coffee into theorems."
Thanks again Pete. I appreciate your help, and will try one more
question. To summarize, I can control what fonts emacs wants to use,
and I can check to see which fonts are on the system. By googling the
terms you mention, I can learn more about how to do this. This is a
great help, thanks very much.
If I wish to take the approach of obtaining the fonts that emacs seems
to want but can not find, where would I go for that?
Again, I sure appreciate your help....
next prev parent reply other threads:[~2006-10-28 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-22 2:25 fatal font problem with emacs BillJosephson
2006-10-22 23:41 ` Peter Dyballa
[not found] ` <mailman.137.1161560471.27805.help-gnu-emacs@gnu.org>
2006-10-23 1:48 ` BillJosephson
2006-10-23 8:55 ` Peter Dyballa
[not found] ` <mailman.147.1161593726.27805.help-gnu-emacs@gnu.org>
2006-10-25 8:14 ` BillJosephson
2006-10-25 9:21 ` Peter Dyballa
[not found] ` <mailman.228.1161768081.27805.help-gnu-emacs@gnu.org>
2006-10-28 18:11 ` BillJosephson [this message]
2006-10-28 19:48 ` Peter Dyballa
[not found] ` <mailman.355.1162064979.27805.help-gnu-emacs@gnu.org>
2006-10-29 2:40 ` Tim X
2006-11-02 17:59 ` IsraelMendezMartinez
2006-11-04 16:13 ` BillJosephson
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=1162059110.456641.280210@h48g2000cwc.googlegroups.com \
--to=billjosephson@hotmail.com \
/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.
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).