all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Dani Moncayo'" <dmoncayo@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Using the same custom file in two different OSes
Date: Sun, 13 Jan 2013 14:18:54 -0800	[thread overview]
Message-ID: <419D9CDD3C2740E3B0E0CDE556F7BD12@us.oracle.com> (raw)
In-Reply-To: <CAH8Pv0gP3UtCd-U_PhRtWBSJ94ye_3aFZW0_O4N2afw_rTfwRA@mail.gmail.com>

> I'd like to use the same Emacs custom file in two different OSes:
> MS-Windows and Ubuntu, but I have one problem: I want to define the
> :family property of the `default' and `variable-pitch' faces based on
> the `system-type' (because my favorite family on MS-Windows isn't
> available on Ubuntu and vice-versa), but without having to duplicate
> my custom file (one for each system-type), so that I can tweak my
> customization at any time, in any OS, and get an updated custom file
> that is still valid for both OSes.
> 
> Is there a way to achieve that goal?  If so, how?

With a single `custom-file', using Customize, no, I don't think so.

But you can do it using Lisp, in your init file (~/.emacs).  (Use a separate
`custom-file' for the stuff that Customize manages.  Keep your init file for
Lisp that you manage.)

Try first using Customize on each of the platforms separately, to see what
values it gives you for those faces, for the automatically generated
`custom-set-faces' sexp.

Then remove the settings for those exceptional faces from `custom-file', moving
them to your init file instead and wrapping them with (custom-set-faces ...):

(if (eq system-type 'windows-nt)
    (custom-set-faces ...)
  (custom-set-faces ...))




  reply	other threads:[~2013-01-13 22:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-13 22:00 Using the same custom file in two different OSes Dani Moncayo
2013-01-13 22:18 ` Drew Adams [this message]
2013-01-14 18:46   ` Dani Moncayo
2013-01-14 19:13     ` Drew Adams
2013-01-14 19:42       ` Dani Moncayo
2013-01-14 21:55         ` Peter Dyballa
2013-01-14 23:00           ` Dani Moncayo
2013-01-15  8:25             ` Didier Verna
2013-01-15  8:42               ` Dani Moncayo
2013-01-14 22:05         ` Drew Adams
2013-01-16 21:03           ` Dani Moncayo
     [not found]           ` <mailman.17633.1358371586.855.help-gnu-emacs@gnu.org>
2013-01-17  8:43             ` Sebastien Vauban
2013-01-17 14:19               ` Drew Adams
2013-01-17 14:38                 ` Peter Dyballa
2013-01-17 15:22                   ` Dani Moncayo
2013-01-17 16:38                     ` Eli Zaretskii
2013-01-17 16:01                   ` Drew Adams
2013-01-17 16:33                   ` Eli Zaretskii
2013-01-17 16:32                 ` Eli Zaretskii
2013-01-17 16:57                   ` Drew Adams
2013-01-17 17:48                     ` Eli Zaretskii
2013-01-17 18:15                       ` Drew Adams
2013-01-17 18:44                         ` Eli Zaretskii
2013-01-15 13:27 ` Stefan Monnier
2013-01-15 20:27   ` Dani Moncayo
     [not found]   ` <mailman.17532.1358281671.855.help-gnu-emacs@gnu.org>
2013-01-16  8:58     ` Sebastien Vauban
2013-01-16 20:35       ` Dani Moncayo
2013-01-16 12:59     ` Jason Rumney

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=419D9CDD3C2740E3B0E0CDE556F7BD12@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=dmoncayo@gmail.com \
    --cc=help-gnu-emacs@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.