unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>, emacs-devel@gnu.org
Subject: Re: macos.texi updated
Date: Mon, 10 Oct 2005 21:31:30 -0400	[thread overview]
Message-ID: <873bn8n8vc.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <991DC775-381E-4B96-BBC6-B3701CCD6EAD@cogsci.ucsd.edu> (Adrian Robert's message of "Fri, 07 Oct 2005 10:53:22 -0400")

>> I'm not against the introduction of a new font specification style,
>> but I think it is mainly for developers and power-users.  Emacs
>> already has a mechanism that enables users to specify fonts in a
>> simpler way at the face level.

> You're right..  But the population of "power users" in this case for
> whatever reason seems fairly large (just subjective impression), and the
> requirement to learn XLFD (to compose a fontset, or whatever else) and
> partake of the pleasures of asterisk-counting seems onerous.

This has nothing to do with power users.  It's simply that until Emacs-21,
XLFD was the standard way to specify fonts in Emacs, and that until recently
XLFD was the standard way to specify fonts in other X11 apps as well.
That's a lot of historical baggage.  Creating yet another syntax will not
reduce this baggage by one bit.

The fact is that there is a new syntax and people do use it, tho a lot of
people still use the old one.

> In addition, I've been integrating the Cocoa port's font handling with
> xfaces.c, and can say it's onerous for developers.

Yes, this part probably needs to be redesigned for Cocoa/OpenStep/xft/w32,
but it has nothing to do with the user-level interface.  The internal
interface should simply not use a syntax but data structures instead.


        Stefan

  parent reply	other threads:[~2005-10-11  1:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21  8:21 macos.texi updated YAMAMOTO Mitsuharu
2005-09-22  6:12 ` Steven Tamm
2005-09-22 10:20   ` YAMAMOTO Mitsuharu
2005-09-22 15:22   ` Stefan Monnier
2005-09-25 14:20     ` Adrian Robert
2005-09-28  8:30       ` YAMAMOTO Mitsuharu
2005-10-07 14:53         ` Adrian Robert
2005-10-09 18:16           ` Richard M. Stallman
2005-10-10 19:53             ` Adrian Robert
2005-10-11 14:44               ` Richard M. Stallman
2005-10-11 17:22                 ` David Reitter
2005-10-12 16:24                   ` Richard M. Stallman
2005-10-18 18:29                 ` Adrian Robert
2005-10-20  4:55                   ` Richard M. Stallman
2005-10-24 12:24                     ` Adrian Robert
2005-10-25 15:59                       ` Richard M. Stallman
2005-10-11  1:31           ` Stefan Monnier [this message]
2005-10-11  8:01           ` YAMAMOTO Mitsuharu
2005-10-11 17:10             ` Adrian Robert
2005-09-22 20:42 ` Jesper Harder
2005-09-23  4:46   ` YAMAMOTO Mitsuharu
2005-09-23  7:00     ` Cheng Gao
2005-09-25 19:45     ` Jesper Harder
2005-09-23 18:12 ` Richard M. Stallman

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=873bn8n8vc.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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).