unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jason Rumney <jasonr@gnu.org>
Cc: David Abrahams <dave@boostpro.com>,
	emacs-pretest-bug@gnu.org, 2504@emacsbugs.donarmstrong.com
Subject: bug#2504: 23.0.90; new-frame => "no font backend available."
Date: Sat, 28 Feb 2009 17:12:06 -0500	[thread overview]
Message-ID: <jwvprh2xldc.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <49A94BEB.80304@gnu.org> (Jason Rumney's message of "Sat, 28 Feb 2009 22:36:27 +0800")

>> I think MacOS Emacs isn't very resilient to customizations for other
>> platforms that should be ignored.  For example, my
>> 
>> default-frame-alist
>> 
>> is 
>> 
>> ((menu-bar-lines . 1) (font-backend . "xft") (font . "Bitstream Vera Sans Mono-10.5") (tool-bar-lines . 0))
>> 
>> But `M-x new-frame' causes emacs to report "no font backend available"
>> without opening a new window.
>> 

> This is no different than setting (font-backend . "garbage") on any
> platform. If you have platform specific settings in your .emacs which you
> want to share between platforms, then you need to make them conditional.

We could make it easier for the users by ignoring invalid font-backends,
so a single setting can work on all platforms.


        Stefan







  reply	other threads:[~2009-02-28 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28  0:55 bug#2504: 23.0.90; new-frame => "no font backend available." David Abrahams
2009-02-28 14:36 ` Jason Rumney
2009-02-28 22:12   ` Stefan Monnier [this message]
2009-03-01  0:45     ` David Abrahams
2019-10-31 18:03   ` Lars Ingebrigtsen

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=jwvprh2xldc.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=2504@emacsbugs.donarmstrong.com \
    --cc=dave@boostpro.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=jasonr@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).