[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: On elisp running native
From: |
Andrea Corallo |
Subject: |
Re: On elisp running native |
Date: |
Fri, 29 Nov 2019 21:18:32 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (berkeley-unix) |
Eli Zaretskii <address@hidden> writes:
>> From: Andrea Corallo <address@hidden>
>> Cc: address@hidden, address@hidden
>> Date: Fri, 29 Nov 2019 16:43:21 +0000
>>
>> (mapc #'byte-compile-file (directory-files "~/emacs/lisp" t "el$"))
>>
>> Then is one single start of the GUI for all compilations.
>>
>> I see an intense message activity going on in the mini-buffer so maybe
>> that's the reason?
>>
>> Question how could I delete the compilation log without interrupting the
>> compilation it-self?
>
> How about binding inhibit-message to a non-nil value, around that mapc
> call?
>
Great, doing that we are straight down into the 15s territory, exactly as
the measured batch. I guess this explains.
Andrea
--
address@hidden
- Re: On elisp running native, (continued)
- Re: On elisp running native, Stefan Monnier, 2019/11/28
- Re: On elisp running native, Andrea Corallo, 2019/11/28
- Re: On elisp running native, Stefan Monnier, 2019/11/28
- Re: On elisp running native, Andrea Corallo, 2019/11/28
- Re: On elisp running native, Eric Abrahamsen, 2019/11/28
- Re: On elisp running native, Andrea Corallo, 2019/11/29
- Re: On elisp running native, Eli Zaretskii, 2019/11/29
- Re: On elisp running native, Stefan Monnier, 2019/11/29
- Re: On elisp running native, Andrea Corallo, 2019/11/29
- Re: On elisp running native, Eli Zaretskii, 2019/11/29
- Re: On elisp running native,
Andrea Corallo <=