Stephen Berman wrote:
> Friday, also in other months and years -- and failed to get the
> fontification problem with all of them except '(5 4 2006) and '(5 5
> 2006)! With those two dates, and apparently those alone, I can
> replicate the fontification problem at will. I have no idea what's
> go
"Miguel V. S. Frasson" wrote:
> emacs -Q --eval \
> "(progn \
> (setq debug-on-error t) \
> (setq other-holidays '('((( 2 27 2006) \"Emacs bug\")"
This is not a bug, because you should be using:
emacs -Q --eval "(progn \
(setq debug-on-error t) \
(setq other-holidays '((holiday-fixed 2
On Wed, 10 May 2006 03:00:00 -0400 Glenn Morris <[EMAIL PROTECTED]> wrote:
> Stephen Berman wrote:
>
>> Friday, also in other months and years -- and failed to get the
>> fontification problem with all of them except '(5 4 2006) and '(5 5
>> 2006)! With those two dates, and apparently those alone
On Wed, May 10 2006, Richard Stallman wrote:
> The predicate is a lambda expression which was bytecomplied [I'm not
> sure if this is what you asked for]. I gave a recipe to reproduce in
> my first mail. FWIW, if I quote[1] the lambda expression in my
> recipe, I get the expected
In GNU Emacs 22.0.50.49 (i686-pc-linux-gnu, GTK+ Version 2.8.17)
of 2006-05-10 on escpc40
configured using `configure '--with-gtk''
With non-nil view-calendar-holidays-initially, org-schedule results in
an error. This is reproducible with emacs -Q and:
(load-library "org.el")
(with-temp
You are right. Thanks.
Miguel.
On 5/10/06, Glenn Morris <[EMAIL PROTECTED]> wrote:
"Miguel V. S. Frasson" wrote:
> emacs -Q --eval \
> "(progn \
> (setq debug-on-error t) \
> (setq other-holidays '('((( 2 27 2006) \"Emacs bug\")"
This is not a bug, because you should be using:
emacs -Q
On Wed, May 10 2006, Reiner Steib wrote:
> I still think we should avoid printing byte-code even in case third
> party libraries forget to quote a lambda expression.
I noticed that we also get byte-code for the `allout.el' variables
like `allout-numbered-bullet'. This happens because Ken Manheim
> ;;;###autoload
> (put 'allout-numbered-bullet 'safe-local-variable
> (lambda (x) (or (not x) (stringp x
> ... instead of...
> ;;;###autoload(put 'allout-numbered-bullet 'safe-local-variable (lambda (x)
> (or (not x) (stringp x
> ... (and similar for other many other variables) in
On Wed, May 10 2006, Stefan Monnier wrote:
[ (lambda (x) (or (not x) (stringp x))) ]
> Actually, we should use string-or-null-p here.
ACK. And (member x (quote (t nil))) should be booleanp.
But there are also expressions in `allout.el' where no predefined
predicate exists (AFAICS):
allout-use-
Reiner Steib wrote:
-use @code{booleanp} as the property value.
+use @code{booleanp} as the property value. Lambda expressions should
+be quoted so that @code{describe-variable} can display the predicate.
This is ambiguous.
What is meant by "quoting" a lambda expression '(lambda ... )
_If_ we are going to keep that safe-local-variable trivia in the `C-h v'
output, then at least it should be formulated in a less confusing way:
This variable is safe to use as a file local variable only if its value
satisfies the predicate ...
These variables are perfectly safe to use as file
On 5/10/06, Reiner Steib <[EMAIL PROTECTED]> wrote:
On Wed, May 10 2006, Stefan Monnier wrote:
[ (lambda (x) (or (not x) (stringp x))) ]
> Actually, we should use string-or-null-p here.
ACK. And (member x (quote (t nil))) should be booleanp.
i can make those changes. (booleanp must be rathe
On 5/10/06, Reiner Steib <[EMAIL PROTECTED]> wrote:
On Wed, May 10 2006, Reiner Steib wrote:
> I still think we should avoid printing byte-code even in case third
> party libraries forget to quote a lambda expression.
I noticed that we also get byte-code for the `allout.el' variables
like `allo
Hi,
On ms-windows when you (require 'ediff) on a computer where the diff
executable doesn't exist you get the backtrace below.
Of course, ediff probably isn't that useful if you don't have diff,
but still it would be nice to fail in a more gracefull way.
To reproduce, set ediff-diff-program to s
I still think we should avoid printing byte-code even in case third
party libraries forget to quote a lambda expression. May I install
the following change in `describe-variable'?
Yes, that change is ok.
___
emacs-pretest-bug mailing
Would you please fix the code in allout.el?
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
What is meant by "quoting" a lambda expression '(lambda ... ) or
#'(lambda ... )?
The former.
If you use '(lambda ... ) the expression does not get
compiled, which can be a nuisance if the lambda does any real work.
Speed is not important for these functions, so
An improvement would be:
This variable is considered safe as a file local variable if its
value satisfies the predicate ...
That change is good; please install it.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lis
Thanks for the report and diagnosis - fixed as you suggested.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
19 matches
Mail list logo
