Re: All elisp package should be redirect Compilation Log to a file.

* WA => Wichert Akkerman WA> Yes, it's an evil patch because it a) will put the file in the WA> current directory, which can be anywhere, and b) it doesn't WA> check if the file already exists, and c) it means you won't WA> see errors. Take a look at mine (mailcrypt's one): it puts the file i

Re: All elisp package should be redirect Compilation Log to a file.

* TK => Takuo KITAME TK> +rm -f CompilationLog.gz What good is this rm for? You already `>' on CompilationLog.gz. Maybe I miss something here, what is it? TK> Any comments? Yes, one: I wish you good luck. :-) This is a very good idea, which I already proposed some time ago (indeed my pac

Re: All elisp package should be redirect Compilation Log to a file.

Interesting idea (I like it), but bad implementation (not that I have the time to try to fix it). Peter Takuo KITAME wrote: > Hello. > > Some elisp package will byte-compile at installing. > But stdouts of byte-compiling are very noisy and noisy. > I think that should be redirect to a Compilat

Re: All elisp package should be redirect Compilation Log to a file.

Previously Takuo KITAME wrote: > Any comments? Yes, it's an evil patch because it a) will put the file in the current directory, which can be anywhere, and b) it doesn't check if the file already exists, and c) it means you won't see errors. Wichert. -- __

All elisp package should be redirect Compilation Log to a file.

Hello. Some elisp package will byte-compile at installing. But stdouts of byte-compiling are very noisy and noisy. I think that should be redirect to a CompilationLog file. (and gzip this.) A patch for debian/emacsen-install.ex --- emacsen-install.ex Tue Oct 26 13:14:44 1999 +++ emacsen-install