Re: How does Emacs load a non-existent .el file?

[Eli Zaretskii <eliz@gnu.org>]

> From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
> Cc: emacs-devel@gnu.org
> Date: Fri, 01 Mar 2024 17:15:21 +0300
> 
> > > I wonder if it's too hard to add to `*Help*` buffer mention that
> > > certain functions are not being read from the file where the buffer
> > > claims that they reside.
> > 
> > That claim is correct, so why change it?
> 
> What claim?

The claim you mention above.

> I'm pointing out the lack of information in *Help* buffer
> that certain functions are not read from the location where *Help*
> claims them to be.

The doc string doesn't say where the functions is read from, it says
where the function is defined in the source code.  And it's true that
command-line-1 is defined in startup.el.  Like it's true that, for
example, kill-buffer is defined in buffer.c, although it is built into
Emacs by way of compiling buffer.c into buffer.o, and then linking
buffer.o (together with other *.o files) into the Emacs executable.
the same happens with functions defined in startup.el: the code is
compiled into startup.elc or startup-xxx.eln, and then loaded into the
Emacs binary during dumping (actually, the *.eln files are only
recorded during dumping and then loaded anew at each startup).