From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Please help with location of .emacs file and .emacs.d folder location
Date: Wed, 11 Nov 2009 20:28:00 +0200 [thread overview]
Message-ID: <83skckor0v.fsf@gnu.org> (raw)
In-Reply-To: <c5d81590-fafa-49f6-8fb3-00144251310c@p28g2000vbi.googlegroups.com>
> From: patrol <patrol_boat@hotmail.com>
> Date: Mon, 9 Nov 2009 07:56:09 -0800 (PST)
>
> I'm not sure about this. Should I just create a new folder
> named .emacs.d in this directory? And should I just create a plain
> text file .emacs in the directory as well?
Just start Emacs, then type "C-x C-f ~/.emacs RET". Then type there
whatever you want, and finally type "C-x C-s" to save the file. Emacs
will put it in the correct place, and will find it there when you
restart it.
As for the .emacs.d directory, Emacs will create it itself when
needed. You don't need to be bothered.
prev parent reply other threads:[~2009-11-11 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 15:56 Please help with location of .emacs file and .emacs.d folder location patrol
2009-11-09 22:28 ` Lowell Gilbert
2009-11-11 18:28 ` Eli Zaretskii [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=83skckor0v.fsf@gnu.org \
--to=eliz@gnu.org \
--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.
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).