From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: DOC for Mac OS shown for Emacs compiled for X.
Date: Thu, 28 Oct 2004 02:24:49 -0400 [thread overview]
Message-ID: <E1CN3iL-0006xi-Ap@fencepost.gnu.org> (raw)
In-Reply-To: <417F65AE.80000@swipnet.se> (jan.h.d@swipnet.se)
1. make-docfile should not read the .c file if the .o one does not exist.
2. Emacs is supposed to find the correct entry in DOC.
3. macfns.o should not be in SOME_MACHINE_OBJECTS when building for X.
4. Symbols that occur in several files (x, mac, w32) should have the same doc
string.
If we make sure macfns.c has only functions and variables that appear
also in xfns.c, then we can always omit macfns.o from
SOME_MACHINE_OBJECTS. The doc strings that are really used would come
from xfns.c, regardless of the platform. We could replace the doc
strings in macfns.c with "This is a dummy--see xfns.c", so people
won't waste time editing them.
#1 is also a possible solution. It is more general, since it could
handle other problems too. Maybe we should choose that.
prev parent reply other threads:[~2004-10-28 6:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 9:09 DOC for Mac OS shown for Emacs compiled for X Jan D.
2004-10-27 9:46 ` Andreas Schwab
2004-10-28 7:26 ` Jan D.
2004-10-28 9:47 ` Andreas Schwab
2004-10-28 13:16 ` Jan D.
2004-10-28 13:57 ` Andreas Schwab
2004-10-28 19:56 ` Stefan
2004-10-29 8:00 ` Jan D.
2004-10-29 20:37 ` Stefan
2004-10-29 21:16 ` Jan D.
2004-10-29 21:48 ` Stefan
2004-10-30 5:43 ` Jan D.
2004-10-30 16:32 ` Stefan
2004-10-30 17:43 ` Jan D.
2004-10-30 21:59 ` Kim F. Storm
2004-10-30 14:20 ` Richard Stallman
2004-10-30 14:19 ` Richard Stallman
2004-10-30 14:39 ` Jan D.
2004-11-01 7:23 ` Richard Stallman
2004-11-01 8:47 ` Jan D.
2004-11-02 14:08 ` Richard Stallman
2004-10-28 6:24 ` Richard Stallman [this message]
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=E1CN3iL-0006xi-Ap@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).