unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12395@debbugs.gnu.org
Subject: bug#12395: 24.2.50; `C-h f emacs-version' ignores doc string; gives no information
Date: Sat, 20 Oct 2012 21:21:20 -0400	[thread overview]
Message-ID: <1zpq4c39in.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <833919zauo.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Oct 2012 12:39:11 +0200")

Eli Zaretskii wrote:

> Incidentally, is it OK that cp51932.el and eucjp-ms.el are loaded as
> uncompiled Lisp files, but are not in src/lisp.mk? 

No, they should be there, well spotted. I imagine they were missed
because they are not in loadup.el, rather loaded by something that is.
(As an aside, that can be somewhat confusing, as this shows. Maybe it
would be better to move them to loadup.el. Same for term/internal.)

They don't contain any useful doc strings, so that does not matter, but
the rule for the Emacs binary in src/Makefile should depend on them.

> Also, charprop.el is loaded uncompiled, but its doc strings do not
> follow the conventions required by make-docfile.c.  We are lucky that
> none of charprop.el's forms are recognizable by make-docfile.c.

I don't see any reason _not_ to compile these 3 files.
It seems generated files are usually not compiled, but these ones
are in the repository.





  reply	other threads:[~2012-10-21  1:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-09 14:49 bug#12395: 24.2.50; `C-h f emacs-version' ignores doc string; gives no information Drew Adams
2012-09-11 14:44 ` Bastien
2012-09-11 14:52   ` Drew Adams
2012-09-11 15:31     ` Bastien
2012-10-19 14:45     ` Drew Adams
2012-10-20  5:58       ` Bastien
2012-10-20  9:23         ` Eli Zaretskii
2012-10-20 10:05           ` Eli Zaretskii
2012-10-20 10:39             ` Eli Zaretskii
2012-10-21  1:21               ` Glenn Morris [this message]
2012-11-03 14:02                 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1zpq4c39in.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=12395@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).