On Oct 11, 2005, at 10:44 AM, Richard M. Stallman wrote:
Since I use Emacs on Aqua, which does not expose XLFD anywhere, I can't speak directly as a user. But looking at the situation from the inside on the unicode-2 branch, it appears that there are several major places in the code that expect all of the information for specifying a font to be contained in a single string. At the elisp-wielding-user-visible level this manifests in what you pass to and get back from x-list-fonts, as well as any font-setting functions, setting font as a frame parameter, etc... I can't tell whether other platforms could use some other single-string-specifies-all format besides XLFD (not that this would be natural), or if other code in fontset.c and xfaces.c requires these names to be XLFD. All I know is that in the Cocoa port, I'm having trouble getting the full font machinery working without putting all font info into string names. In any case, both lisp code and user mailing list traffic for the Mac Carbon emacs contain numerous references to XLFD. E.g.: See for example: Anyway, I will drop this now due to an intense lack of interest from anyone else on this list ;), and come back when 22 is out and/or I have some code to show..
My point was that the XLFD is so concise and cryptic as to be a real hassle no matter what it's used for. I really don't see any typing savings for something like emacs -font '-*-courier-*-*-*--12-*-*-*-*-*-*-*' or even emacs -font '-*-courier-*-*-*--12-*' vs. emacs -font '{ font-family: courier font-size: 12pt }' If you're not cutting/pasting the font, counting out how many asterisks you need and deciding where to put the '12' are far more time-consuming than punching out the few extra characters for CSS-style. And if you are cutting/pasting, there's no difference, besides readability. But given that things are as they are, I see no reason to add a new syntax either if it's not needed for lisp customization -- using XLFD on the command line seems fine since users on the non-X systems rarely use command-line invocation anyhow. |
_______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel