all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Reitter <david.reitter@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Platform-specific symbols in cus-start.el
Date: Sat, 21 Mar 2009 16:44:03 +0200	[thread overview]
Message-ID: <u7i2jos0c.fsf@gnu.org> (raw)
In-Reply-To: <696E8C82-6119-47F3-9F46-F984ACAF29B7@gmail.com>

> Cc: emacs-devel@gnu.org
> From: David Reitter <david.reitter@gmail.com>
> Date: Sat, 21 Mar 2009 08:53:54 -0400
> 
> Related to this, is the kludge below found in nsterm.m appropriate, or  
> should cus-start be fixed?
> 
> 
>    /* these are unsupported but we need the declarations to avoid whining
>       messages from cus-start.el */
>    DEFVAR_BOOL ("x-use-underline-position-properties",
> 	       &x_use_underline_position_properties,
>       doc: /* NOT SUPPORTED UNDER NS.
> *Non-nil means make use of UNDERLINE_POSITION font properties.
> A value of nil means ignore them.  If you encounter fonts with bogus
> UNDERLINE_POSITION font properties, for example 7x13 on XFree prior
> to 4.1, set this to nil.
> 
> NOTE: Not supported on Mac yet.  */);
>    x_use_underline_position_properties = 0;

We could add an extra `cond' clause where it filters out symbols
native to other platforms, and then you could remove this DEFVAR_BOOL.
But, as Stefan points out, it's probably not worth the hassle to do
that for the sake of a single obscure variable, unless we think users
might be fooled to think that the existence of the variable means the
feature is supported.




      parent reply	other threads:[~2009-03-21 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21  9:48 Platform-specific symbols in cus-start.el Eli Zaretskii
2009-03-21 12:53 ` David Reitter
2009-03-21 13:55   ` Stefan Monnier
2009-03-22  1:48     ` YAMAMOTO Mitsuharu
2009-03-21 14:44   ` Eli Zaretskii [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=u7i2jos0c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@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.