From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: stephen@xemacs.org, jasonr@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Setting font to Lucida Grande on Mac OS X
Date: Mon, 22 Sep 2003 13:23:50 -0500 (CDT) [thread overview]
Message-ID: <200309221823.h8MINoI08026@raven.dms.auburn.edu> (raw)
In-Reply-To: <87y8wh2jpu.fsf@tleepslib.sk.tsukuba.ac.jp> (stephen@xemacs.org)
Richard Stallman wrote:
However, matching is
! implementation-dependent, and often inaccurate, when wildcards match
! dashes in a long name. It works best if you supply all 14 dashes.
The first sentence seems to imply that wildcards are so unreliable
that you should never use them. It is clearer to say
However, matching is
implementation-dependent, and can be inaccurate when wildcards match
dashes in a long name. For reliable results, supply all 14 dashes
and use wildcards only within a field.
and Stephen J. Turnbull replied:
The second sentence is a distinct improvement (especially as it
implies partial matching in a field, which often is useful, such as
...-jisx0208*-0 to catch names which specify the year of the
standard), but I recommend that the first sentence be left as is.
I believe the difference of opinion is limited to:
"often inaccurate" (Stephen's version) vs "can be inaccurate"
(Richard's version).
I believe that we all agree with what is meant to be communicated,
namely:
1. It is OK to try out, say:
M-x set-frame-font RET *-courier-medium-r-*-14-*
Why type fourteen dashes if you can get what you want with the above?
(This works for me.)
2. If you do
M-x set-frame-font RET -abisource-courier-bold-i-normal--17-*
and get the error message:
Font `-abisource-courier-bold-i-normal--17-*' is not defined
(as I do), then this does _not_ mean that there really is no such font.
In fact, after supplying the fourteen dashes I get the font:
-abisource-courier-bold-i-normal--17-135-90-91-p-100-iso8859-1
3. Always supply fourteen dashes for Elisp code, except when only
meant for personal use. All XLFD's I found in the Emacs
source code actually adhere to this rule.
To me, both versions suggest 1-3 above, even though Richard's puts
somewhat more emphasis on (1) and Stephen's on (2) and (3). To me the
difference does not seem terribly big. My patch currently contains
Richard's version, but I will wait at least 24 more hours before
committing it, so everybody can make further comments. (Of course,
further changes can also be made after I commit.)
Sincerely,
Luc.
next prev parent reply other threads:[~2003-09-22 18:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-14 22:43 Setting font to Lucida Grande on Mac OS X Sancho Neves-Graca
2003-09-14 23:10 ` Luc Teirlinck
2003-09-15 5:55 ` Andrew Choi
2003-09-15 15:09 ` Luc Teirlinck
2003-09-16 1:19 ` Sancho Neves-Graca
2003-09-16 3:54 ` Stephen J. Turnbull
2003-09-17 2:34 ` Luc Teirlinck
2003-09-17 12:23 ` Stephen J. Turnbull
2003-09-17 12:49 ` Jason Rumney
2003-09-17 16:55 ` Luc Teirlinck
2003-09-18 15:14 ` Richard Stallman
2003-09-19 11:01 ` Stephen J. Turnbull
2003-09-19 14:34 ` Luc Teirlinck
2003-09-19 15:11 ` Luc Teirlinck
2003-09-20 7:50 ` Richard Stallman
2003-09-20 12:04 ` Luc Teirlinck
2003-09-20 13:06 ` Luc Teirlinck
2003-09-19 15:34 ` Luc Teirlinck
2003-09-19 22:53 ` Luc Teirlinck
2003-09-20 21:27 ` Richard Stallman
2003-09-21 1:13 ` Luc Teirlinck
2003-09-20 21:26 ` Richard Stallman
2003-09-22 10:36 ` Stephen J. Turnbull
2003-09-22 18:23 ` Luc Teirlinck [this message]
2003-09-22 22:57 ` Luc Teirlinck
2003-09-22 23:08 ` Luc Teirlinck
2003-09-20 3:30 ` Luc Teirlinck
2003-09-18 11:05 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2003-09-14 23:09 Sancho Neves-Graca
2003-09-14 23:51 ` Luc Teirlinck
2003-09-14 23:55 ` Luc Teirlinck
2003-09-15 4:10 ` Luc Teirlinck
2003-09-15 4:34 ` Luc Teirlinck
2003-09-15 4:47 ` Luc Teirlinck
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=200309221823.h8MINoI08026@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=rms@gnu.org \
--cc=stephen@xemacs.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).