Re: Convert README.org to plain text README while installing package

[Eli Zaretskii]

> From: Ihor Radchenko <yantar92@gmail.com>
> Cc: luangruo@yahoo.com,  michael.albinus@gmx.de,  acm@muc.de,
>   stefan@marxist.se,  tsdh@gnu.org,  akib@disroot.org,  emacs-devel@gnu.org
> Date: Sun, 05 Jun 2022 23:53:14 +0800
> 
> > No, sorry.  Suggest to profile it to see what takes time.
> 
> Well. I tried, but it is not terribly helpful:
> 
>          251  85% - command-execute
>          251  85%  - funcall-interactively
>          251  85%   - eval-last-sexp
>          251  85%    - elisp--eval-last-sexp
>          251  85%     - progn
>          251  85%      - benchmark-call
>          251  85%       - #<lambda 0x14e0668>
>          251  85%        - load
>          251  85%         - load-with-code-conversion
>          130  44%          - require
>          120  40%           - load-with-code-conversion
>           70  23%            + internal-macroexpand-for-load
>           30  10%            - require
>           20   6%             - load-with-code-conversion
>           20   6%              - require
>           10   3%                 load-with-code-conversion
>           10   3%             + byte-code
>           10   3%             byte-code
>          101  34%          + internal-macroexpand-for-load
>           10   3%          + custom-declare-variable
>           43  14% - ...
>           33  11%    Automatic GC
>           10   3%  + byte-compile-preprocess
> 
> Looks like macroexpand takes time, but I have no idea how to interpret
> this.

I think also load-with-code-conversion, which probably means we are
loading gobs of Lisp.  That could also explain why macroexpansion
takes a significant percentage.