From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>,
"'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'Emacs-Devel devel' <emacs-devel@gnu.org>
Subject: RE: Where did all the wellknown faces go?
Date: Tue, 19 Oct 2010 15:43:31 -0700 [thread overview]
Message-ID: <37C7175BCB174359B84E057D7CB96F2B@us.oracle.com> (raw)
In-Reply-To: <87tykh7rf8.fsf@stupidchicken.com>
> If you've played around with the customize-themes code, there is an
> option to migrate your customizations into a theme, in which case they
> are removed from your custom file. It's unlikely you could have done
> that by accident, though, and it should not be limited to faces. I
> can't think of any other recent changes that writes to custom-file.
> Maybe you have some rogue user code somewhere.
Caveat: I have not been following this thread at all. If my questions seem
irrelevant, please ignore.
Moving stuff out of the `custom-file' or init file to a theme sounds risky. I
understand that you stated that it's an option. Still...
Do we take care to restore the original files if something goes wrong during the
move? After everything is moved successfully, do we give the user a command to
get back the original `custom-file' or init file? Is there a command that
migrates (or copies) all settings of a given custom theme to the user's
`custom-file' or init file?
next prev parent reply other threads:[~2010-10-19 22:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 20:34 Where did all the wellknown faces go? Lennart Borgman
2010-10-18 20:54 ` Chong Yidong
2010-10-18 21:08 ` Lennart Borgman
2010-10-18 22:27 ` Chong Yidong
2010-10-18 22:58 ` Lennart Borgman
2010-10-19 22:23 ` Chong Yidong
2010-10-19 22:43 ` Drew Adams [this message]
2010-10-19 22:54 ` Lennart Borgman
2010-10-20 15:49 ` Stefan Monnier
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=37C7175BCB174359B84E057D7CB96F2B@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
/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).