From: Sivaram Neelakantan <nsivaram.net@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: OT: version control of .el files in NT Emacs
Date: Sat, 10 Sep 2016 10:27:29 +0530 [thread overview]
Message-ID: <871t0stkqu.fsf@gmail.com> (raw)
In-Reply-To: 87wpilyu31.fsf@wanadoo.es
On Fri, Sep 09 2016,Óscar Fuentes wrote:
[snipped 17 lines]
> You probably noticed that you need to adjust the load-path. A robust way
> of doing that is to put in your_el_repo/emacs.el :
>
> (add-to-list 'load-path (file-name-directory load-file-name))
>
> It is also is useful to put this
>
> (setq user-init-file load-file-name)
>
> at the beginning of your emacs.el file in your_el_repo. Look up the
> docstring for the user-init-file variable to see why.
>
How does this help? Because I have just 2 lines in the $HOME/.emacs
(setq user-emacs-directory "c:/gnu/initfiles/.emacs.d/" )
(load-file "c:/gnu/initfiles/.emacs")
And in the c:/gnu/initfiles/.emacs file I hard coded paths like
(load-file "c:/gnu/initfiles/.text_config.el")
(load-file "c:/gnu/initfiles/.ido_config.el")
(load-file "c:/gnu/initfiles/.ac_config.el")
(load-file "c:/gnu/initfiles/.r_ess_config.el")
(load-file "c:/gnu/initfiles/.cygwin_config.el")
(load-file "c:/gnu/initfiles/.uniq_config.el")
(load-file "c:/gnu/initfiles/.smex_config.el")
I get it that .sh_history, .smex_history and other .history*
files used/created by various packages will be still created in
$HOME/.emacs but those are fairly transient stuff aren't they?
sivaram
--
next prev parent reply other threads:[~2016-09-10 4:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 17:32 OT: version control of .el files in NT Emacs Sivaram Neelakantan
2016-09-08 20:05 ` John Mastro
2016-09-08 23:03 ` Óscar Fuentes
2016-09-09 4:50 ` Sivaram Neelakantan
2016-09-09 7:38 ` tomas
2016-09-09 14:53 ` Sivaram Neelakantan
2016-09-09 15:24 ` Óscar Fuentes
2016-09-10 4:57 ` Sivaram Neelakantan [this message]
2016-09-10 12:52 ` Óscar Fuentes
2016-09-10 14:04 ` Sivaram Neelakantan
2016-09-10 23:01 ` Óscar Fuentes
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=871t0stkqu.fsf@gmail.com \
--to=nsivaram.net@gmail.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.