[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: error in calendar
From: |
Frederik Fouvry |
Subject: |
Re: error in calendar |
Date: |
Tue, 8 Mar 2005 18:13:17 +0100 (CET) |
,-- On Tue, 08 Mar 2005 11:02:54 -0500, Richard Stallman wrote:
|
| It may not have to do with the compiler at all, but with a variable
| (mark-diary-entries-in-calendar) being reset by the evaluation, which
| caused the problematic code not to be executed.
|
| I don't understand. Could you explain what that means?
That while I was trying to understand what was going on, during a call
to `calendar' the value of mark-diary-entries-in-calendar had
unexpectedly changed from t to nil, so that I the #include'd file were
not read the next time `calendar' was called. I don't know why it
happened, all I know is _that_ it happened, because I had to reset the
variable to get the entries in the calendar again. In some functions,
the value is changed, but I do not understand how they can affect the
final value.
I recollect that after I evaluated the function, the function finished
very quickly, without problems, but it only printed the message
"Marking diary entries..." once, which - as I later found out - means
that the included files are not read. I have not been able to
reproduce this now.
| Anyway, why does this resetting effect differ depending
| on whether the function is compiled?
See above. There is no dependency.
| Did you try compiling vs interpreting *just this function*
| or *the whole file*?
I tried both (first the function, later the file), but unfortunately I
cannot reconstruct what I did precisely.
| It may have to do with customisations.
|
| They may be relevant somehow, but didn't you try both forms of the
| function with the same customisations?
Indeed.