From: Dani Moncayo <dmoncayo@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Using the same custom file in two different OSes
Date: Mon, 14 Jan 2013 19:46:01 +0100 [thread overview]
Message-ID: <CAH8Pv0gBRdWQUXyD8uwfa72U61PDMuWJ=Bt5gf8A1Y7EZmJkow@mail.gmail.com> (raw)
In-Reply-To: <419D9CDD3C2740E3B0E0CDE556F7BD12@us.oracle.com>
> 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.)
Yes, that's how I have it.
> 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 ...))
That works, but I've observed that each time I save any customization,
my custom file is regenerated with _all_ the customization loaded at
that time, and the platform-specific stuff that I removed from my
custom file is then reinserted. Therefore, in my init file I must put
the platform-specific customization _after_ the loading of the custom
file:
(setq custom-file "my-custom-file.el")
(load custom-file)
(if (eq system-type 'windows-nt)
(custom-set-faces <windows-specific stuff>)
(custom-set-faces <ubuntu-specific stuff>)
Thank you so much for your help.
--
Dani Moncayo
next prev parent reply other threads:[~2013-01-14 18:46 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
2013-01-14 18:46 ` Dani Moncayo [this message]
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='CAH8Pv0gBRdWQUXyD8uwfa72U61PDMuWJ=Bt5gf8A1Y7EZmJkow@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=drew.adams@oracle.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.