all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "oliver" <oliver_baumann@nospam.justemail.net>
Subject: Re: Making a nice .emacs file and configuration
Date: Fri, 24 Sep 2004 09:16:34 +1000	[thread overview]
Message-ID: <civlcl$ne1$1@otis.netspace.net.au> (raw)
In-Reply-To: m3r7ovwv7z.fsf@localhost.localdomain

"Alexandre Russel" <scandrou@hpo.net> wrote in message 
news:m3r7ovwv7z.fsf@localhost.localdomain...
> I am trying to find a set up so even in few years
> with lots more things in it it would stay clean. Would like advice
> from Emacs veteran on how to set up all that. What I am thinking
> about doing is:
>
> ---.emacs--start--
> (setq load-path
>  (cons "~/Emacs/Configurations"
>    (cons "~/Emacs/Extensions"
>      (cons "~/Emacs/DotEmacs" load-path))))
> (setq Info-default-directory-list (cons "~/Emacs/Info" 
> Info-default-directory-list))
> ---.emacs--end----
>
> Then have a Emacs directory with 4 directories inside:
>
> Info: with all the Info from the package I added
> DotEmacs: with the information found usually in .emacs such as 
> binding,configuration, macro, myfunction(probably with 1 file per thing)
> Extensions: All the package I download(template, w3m-emacs...)
> Configurations: All the configuration file for the extensions

set up sounds good. however you need to name explicitly the files you want 
to load on startup. including the direcory where the reside isn't enough.

another problem are auto changes emacs itself does to the .emacs file, e.g. 
when emacs enables disabled commands: so the .emacs file won't stay as clean 
as you want. at least the custumize-settings can be sourced out. read the 
emacs docu about the var custom-file.

cheers, oliver

      parent reply	other threads:[~2004-09-23 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 14:30 Making a nice .emacs file and configuration Alexandre Russel
2004-09-22 10:40 ` emacs Fan
2004-09-23 23:16 ` oliver [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='civlcl$ne1$1@otis.netspace.net.au' \
    --to=oliver_baumann@nospam.justemail.net \
    /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.