Re: Some native compiler related renaming

[Eli Zaretskii <eliz@gnu.org>]

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: Andrea Corallo <akrl@sdf.org>,  emacs-devel@gnu.org
> Date: Sat, 08 May 2021 16:03:50 +0100
> 
> No bonus points for me please, only some nits.  How's this:

Thanks.  I don't agree with some of your changes:

> @@ -875,9 +875,9 @@ Native-Compilation Functions
>    Native compilation might produce warning or error messages; these
>  are normally recorded in the buffer called
>  @file{*Native-compile-Log*}.  In interactive sessions, it uses the
> -special LIMPLE mode (@code{native-comp-limple-mode}), which sets up
> -@code{font-lock} as appropriate for this log, and is otherwise the
> -same as Fundamental mode.  Logging of messages resulting from
> +special @acronym{LIMPLE} mode (@code{native-comp-limple-mode}), which

Here "LIMPLE" shouldn't be an acronym, since it's part of a mode
name.

>    If Emacs was compiled with support for native compilation
> -(@pxref{Native Compilation}), then when a @samp{.elc} byte-compiled
> +(@pxref{Native Compilation}), then when a @file{.elc} byte-compiled
>  file is found by searching @code{load-path}, Emacs will try to look
> -for a corresponding @samp{.eln} file holding the corresponding
> +for a corresponding @file{.eln} file holding the corresponding

The text uses @samp elsewhere for file-name extensions, so I wanted to
be consistent.

> -system directory, i.e.@: the directory with @samp{.eln} files
> -installed by the Emacs build and installation procedure.  In each of
> -the directories in the list, Emacs looks for @samp{.eln} files in a
> +system directory, i.e., the directory with @file{.eln} files installed

I VERY much dislike using a comma after "i.e.".