From: Stefan <monnier@iro.umontreal.ca>
Cc: Andreas Schwab <schwab@suse.de>, emacs devel <emacs-devel@gnu.org>
Subject: Re: DOC for Mac OS shown for Emacs compiled for X.
Date: Fri, 29 Oct 2004 17:48:57 -0400 [thread overview]
Message-ID: <m1mzy5xkn1.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <D7366131-29EF-11D9-AB37-000D93505B76@swipnet.se> (Jan D.'s message of "Fri, 29 Oct 2004 23:16:46 +0200")
> That is also possible, and seems to be what the previous discussion
> indicated. More work though.
But better result.
> And it does not solve the error that doing C-h f x-server-vendor and
> clicking on the "C source code" link gives xfns.c when it should give
> macfns.c. I think a list of what files where used in the link is the only
> way to solve this. For a build on Mac OSX xfns.c or macfns.c could be
> used, depending on if it was an X build or Carbon build.
I'd just move all those DEFUNs to a shared file. If necessary the body of
those DEFUNs can just be a call to some function that's either in macfns.c
or xfns.c, tho ideally some actual code should be shared.
Stefan
next prev parent reply other threads:[~2004-10-29 21:48 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 [this message]
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
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=m1mzy5xkn1.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=schwab@suse.de \
/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).