From: Peter Dyballa <Peter_Dyballa@Web.DE>
Subject: Re: Emacs 22 problems with split init file
Date: Tue, 16 Jan 2007 00:27:54 +0100 [thread overview]
Message-ID: <EB2579E5-A8EF-4C6A-8D21-0116D149F7C9@Web.DE> (raw)
In-Reply-To: <87mz4kufgg.fsf@lion.rapttech.com.au>
Am 15.01.2007 um 22:50 schrieb Tim X:
> As soon as you use just a single init file, there are no problems.
I am using exactly one file with
(custom-set-variables
and
(custom-set-faces
and a few others with just ELisp code. And it works. On Mac OS X.
--
Greetings
Pete
The day Microsoft makes something that doesn't suck
is the day they start selling vacuum cleaners.
Ernest Jan Plugge
prev parent reply other threads:[~2007-01-15 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 7:36 Emacs 22 problems with split init file Tim X
2007-01-14 11:14 ` Peter Dyballa
[not found] ` <mailman.3046.1168773302.2155.help-gnu-emacs@gnu.org>
2007-01-15 6:42 ` Tim X
2007-01-15 10:14 ` Peter Dyballa
[not found] ` <mailman.3068.1168856053.2155.help-gnu-emacs@gnu.org>
2007-01-15 21:50 ` Tim X
2007-01-15 23:27 ` Peter Dyballa [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
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=EB2579E5-A8EF-4C6A-8D21-0116D149F7C9@Web.DE \
--to=peter_dyballa@web.de \
/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.
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).