bug#13217: 24.3.50; emacs-version output not showing up

[nyc4bos]

Glenn Morris <rgm@gnu.org> writes:

> nyc4bos@aol.com wrote:
>
>> This is both with my full setup and with `runemacs.exe -Q'
>>
>> However with the latest trunk version (bzr 111253) I can only see
>> the `emacs-version' value with `runemacs.exe -Q'
>>
>> With my identical full setup I don't see the `emacs-version' in the
>> echo-area nor in the *Messages* buffer with trunk version.
>
> So, do the usual thing of commenting out half your init file to identify
> which half has the problem, then once you know which half, comment out
> half of what remains, and so on, till you narrow down the problem.

When I invoke `runemacs.exe -q`, the problem still occurs.

So, perhaps the problem is in my site-lisp directory.

> You might start by C-h f emacs-version...

>From a `runemacs.exe --no-site-lisp is see:

emacs-version is an interactive compiled Lisp function in
`version.el'.

So I checked my site-lisp directory and I had:
simple.el
simple.elc
subdirs.el

So to test, I copied the current lisp\simple.el* to site-lisp and I
now see:

emacs-version is an interactive compiled Lisp function.

(No 'version.el')

OK, seeing that message from `C-h f' is no problem.

However, when I subsequently startup Gnus, I see the problem with not
geting `emacs-version' to work.

Of course, the solution is to delete the simple.el* files from the
site-lisp directory.

But should having the existance of the current-up-to-date simple.el*
files in the site-lisp directory cause this problem?

You can close this bugreport if it is deemed not interesting to look
into why this happens (with subsequently starting Gnus?) since I can
just remove the simple.el* files from site-lisp.

Thanks.