[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Is (provide 'foo) at the start good or bad?
From: |
Leo |
Subject: |
Re: Is (provide 'foo) at the start good or bad? |
Date: |
Thu, 11 Jun 2009 18:01:55 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) |
On 2009-06-11 13:56 +0100, William Xu wrote:
> Hi,
>
> I got a problem while configuring ffap. I have this in my .emacs:
>
> (eval-after-load 'ffap
> '(progn
> (setq ffap-c-path (cons "../inc" ffap-c-path))))
>
> And when I M-x ffap, it will complain that ffap-c-path is not defined.
> I figured it out it is due to (provide 'ffap) at the very start of
> ffap.el. The easist solution is changing it to:
>
> (eval-after-load "ffap"
> ... Then it will depend on loading of the file, not just the
> feature. But I always like to depend on the feature(at least typing
> one less char). So what is the benefit of providing it at the very
> start?
I have run into this problem before. I prefer putting provide at the end
of the file.
--
Leo's Emacs uptime: 1 day, 3 hours, 18 minutes, 37 seconds
- Is (provide 'foo) at the start good or bad?, William Xu, 2009/06/11
- Re: Is (provide 'foo) at the start good or bad?,
Leo <=
- Re: Is (provide 'foo) at the start good or bad?, Alan Mackenzie, 2009/06/12
- Re: Is (provide 'foo) at the start good or bad?, Stephen J. Turnbull, 2009/06/12
- Re: Is (provide 'foo) at the start good or bad?, Davis Herring, 2009/06/12
- Re: Is (provide 'foo) at the start good or bad?, Stephen J. Turnbull, 2009/06/13