From: Paul Pogonyshev <pogonyshev@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: non-default default face
Date: Fri, 17 Jun 2005 00:57:06 +0300 [thread overview]
Message-ID: <200506170057.06304.pogonyshev@gmx.net> (raw)
In-Reply-To: <200506170026.38912.pogonyshev@gmx.net>
I wrote:
> > On X, the simplest and fastest way is with ~/.Xdefaults, like this:
> >
> > Emacs*Font: -*-courier-medium-r-*--*-140-*-*-*-*-iso8859-1
> >
> > (That's for a 14 point font. I assume you meant a 10.5 point font,
> > which would be 105 in tenths of points.)
>
> Works great.
Actually, it doesn't. After this, tabs become too short and code is
not lined up properly. When the same font is set via customization,
tabs have the proper width. A bug?
Paul
prev parent reply other threads:[~2005-06-16 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 19:40 non-default default face Paul Pogonyshev
2005-06-16 18:46 ` Kevin Rodgers
2005-06-16 21:30 ` Paul Pogonyshev
2005-06-16 21:57 ` Paul Pogonyshev [this message]
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=200506170057.06304.pogonyshev@gmx.net \
--to=pogonyshev@gmx.net \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).