[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: allout-mode fixes - mode-specific settings, auto-fill, deactivation
From: |
Ken Manheimer |
Subject: |
Re: allout-mode fixes - mode-specific settings, auto-fill, deactivation hook |
Date: |
Mon, 10 Jul 2006 12:07:49 -0400 |
richard noticed that my patch did a require of 'cl, when it would be
sufficient and better to condition that to run only during byte
compilation. i've reworked the entire patch against the latest
checked-in version of allout (someone fixed some comments to
substitute eval-buffer for eval-current-buffer), and so am
resubmitting the entire bundle - patch, ChangeLog, and NEWS file - see
attached. these should be used instead of the items in the previous
bundle i submitted.
until thinking about it more, i hadn't connected the fact that it's
enough to limit to byte-compilation requires packages when all you
need are macros. i'm going to submit a separate patch for the
relevant tips.text entry which points out this fact.
On 7/10/06, Richard Stallman <address@hidden> wrote:
one easy solution is to move the `(require 'cl)' into the unit tests
where it is needed - just for the `assert' macro. the unit tests are
not intended to be run by most people, only allout code developers -
is this an ok run-time use of the cl functions?
Yes, that is ok. But if you just want a macro, you could use
(eval-when-compile (require 'cl)).
--
ken
address@hidden
http://myriadicity.net
allout-patch.txt
Description: Text document
ChangeLog-entry.txt
Description: Text document
allout-NEWS.txt
Description: Text document