all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jason Rumney <jasonr@gnu.org>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>, emacs-devel@gnu.org
Subject: Re: built-in variable `font-use-system-font' not bound
Date: Sun, 22 Nov 2009 21:16:33 -0500	[thread overview]
Message-ID: <jwvbpiu56pt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4B07B3F8.1020104@gnu.org> (Jason Rumney's message of "Sat, 21 Nov 2009 17:33:44 +0800")

>> Regardless of how things currently are (we currently have a big mess in
>> this respect), we should follow the following convention:
>> - if it's a feature specific to X11, W32, NS, ... then use a name that
>> starts with "x-", "w32-", "ns-", ...
>> - if it's a feature that makes sense everywhere, then don't use such
>> a prefix (even if it's only implemented for some of the backends).

> If we follow that convention, I think we need another prefix for
> functions/variables that are common across window systems that can be used
> in the test to avoid warnings/errors in cus-start.el for tty only builds.
> Currently we usually use x- for these, since historically most such features
> started on X and were ported to other window systems later.

So you mean features that only make sense for GUIs but not for
text-based terminals like ttys?  I can't think of any such feature
which couldn't be treated similarly to "a feature that makes sense
everywhere but hasn't yet been implemented in all terminal types".


        Stefan




      reply	other threads:[~2009-11-23  2:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-20 14:15 built-in variable `font-use-system-font' not bound Eli Zaretskii
2009-11-20 16:41 ` Jan Djärv
2009-11-20 17:19   ` Jason Rumney
2009-11-20 18:58     ` Jan Djärv
2009-11-21  4:59       ` Stefan Monnier
2009-11-21  9:33         ` Jason Rumney
2009-11-23  2:16           ` Stefan Monnier [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvbpiu56pt.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.