all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: An alternative to a monolithic ~/.emacs init file
Date: Tue, 13 Nov 2007 08:56:08 +1100	[thread overview]
Message-ID: <8764075ds7.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 1194794977.329113.117040@s15g2000prm.googlegroups.com

rustom <rustompmody@gmail.com> writes:

> After my last post I I looked at my current .emacs file and realised
> its more difficult than I thought:
>
> Ideally if the separate aspects of the setup I want were independent
> they could be put into separate directories and the corresponding
> loaddefs and customizations loaded in any (non-deterministic) order.
>
> However there are dependencies: eg to use python (with refactoring)
> one needs bicyclerepairman; to use brm one needs pymacs.
>

The common way to get around this is to number your files -
e.g. 50my-lib.el 60my-other-lib.el etc. This forces files to be loaded in a
specific order. 


> What is worse there are emacs bugs whose correction needs careful
> sequencing:
> For example I need to put
> (provide 'sb-info)
> just before the brm-init otherwise I get 'recursive require' errors.
> What in the name of ... is sb-info -- thats another OT matter
>
I remember seeing this one when I was running CVS emacs prior to the
release of emacs 22. Its a bug from the interaction between the speedbar
installed as part of standard emacs and a free standing versions of
speedbar. I ran into this on a Debian box when I had emacs 21 and the
speedbar package installed and then installed the CVS version of emacs 22.

Note that your 'fix' i.e. putting a (provide 'sb.info) is only hiding the
problem and not actually fixing it. If your running emacs 22 and still have
a stand-alone version of speedbar installed, you could just remove the
stand-alone version.

Tim

-- 
tcross (at) rapttech dot com dot au

  reply	other threads:[~2007-11-12 21:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2759.1193756709.18990.help-gnu-emacs@gnu.org>
2007-11-07 17:13 ` An alternative to a monolithic ~/.emacs init file rustom
2007-11-08 13:08   ` Sebastian Tennant
     [not found]   ` <mailman.3126.1194527313.18990.help-gnu-emacs@gnu.org>
2007-11-08 19:53     ` rustom
2007-11-09 14:18       ` Sebastian Tennant
     [not found]       ` <mailman.3180.1194617919.18990.help-gnu-emacs@gnu.org>
2007-11-10 12:18         ` rustom
2007-11-10 17:13           ` Tom Tromey
     [not found]           ` <mailman.3247.1194750639.18990.help-gnu-emacs@gnu.org>
2007-11-11 15:29             ` rustom
2007-11-12 21:56               ` Tim X [this message]
2007-11-13  4:21                 ` rustom
2007-11-13  9:26                   ` Tim X
2007-11-14  3:52                     ` rustom
2007-11-13  1:22             ` rustom
2007-11-11  0:09       ` Francisco Miguel Colaço
2007-10-30 15:04 Sebastian Tennant
2007-10-30 20:30 ` Sebastian Tennant

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=8764075ds7.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --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.