From: floyd@apaflo.com (Floyd L. Davidson)
Subject: Re: Multiple .emacs files
Date: Sat, 09 Sep 2006 07:25:37 -0800 [thread overview]
Message-ID: <87pse5f4em.fld@apaflo.com> (raw)
In-Reply-To: mailman.6688.1157814085.9609.help-gnu-emacs@gnu.org
Bill <tfc4@cybcon.com> wrote:
>After and hour or so of searching for the answer, I'm afraid I need to
>ask what should be a simple question. How would one go about forcing
>emacs to use a different .emacs config file?
>
>I have played a bit with the -u option, but have yet to get it to work
>with a config file named .emacsT
emacs -q -l ~/.emacsT
--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska) floyd@apaflo.com
next parent reply other threads:[~2006-09-09 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6688.1157814085.9609.help-gnu-emacs@gnu.org>
2006-09-09 15:25 ` Floyd L. Davidson [this message]
2006-09-11 6:29 ` Multiple .emacs files Mathias Dahl
2006-09-11 7:55 ` Floyd L. Davidson
2006-09-12 2:03 ` Tim X
2006-09-12 18:06 ` Kevin Rodgers
[not found] ` <mailman.6827.1158084485.9609.help-gnu-emacs@gnu.org>
2006-09-12 18:29 ` Floyd L. Davidson
2006-09-09 15:01 Bill
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=87pse5f4em.fld@apaflo.com \
--to=floyd@apaflo.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.
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).