Re: Byte-compilation warnings

[Florian Beck]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Florian Beck <abstraktion@t-online.de>
>> Date: Tue, 10 Jun 2008 22:01:54 +0200
>> Cc: help-gnu-emacs@gnu.org, 'Florian Beck' <abstraktion@t-online.de>
>> 
>> For me, byte compiler warnings would be a great way to avoid error,
>> would I not tend to ignore them because of the above problems. I can
>> work around `reference to free variable' warnings, but not the cl
>> warnings. 
>> 
>> The result is not me seriously considering the cl warnings but pretty
>> much disregarding all of them. Not very useful.
>> 
>> My point is, I might apprecciate the information *once*, but after that I
>> have made my deciscion. Further warnings only distract me.
>
> You can always fset byte-compile-cl-warn to something like `ignore',
> right?  Doesn't this work for some reason?

It doesn't. I guess you mean `byte-compiler-warnings'; that results in

Debugger entered--Lisp error: (setting-constant t)
  fset(t ignore)
  eval((fset byte-compile-warnings (quote ignore)))
  eval-last-sexp-1(nil)
  eval-last-sexp(nil)
  call-interactively(eval-last-sexp nil nil)

Anyway, you gave me a lead and:

(setq-default byte-compile-warnings '(not cl-functions)) 

does seem to do the trick.

Thanks!

BTW, I coudn't find anyting in info »byte compiler warnings, how to
avoid«. You might want to consider it there.

I'm using current CVS, if that matters.
-- 
Florian Beck