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: Sat, 30 Oct 2004 12:32:49 -0400 [thread overview]
Message-ID: <m17jp8npa8.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <90659DCD-2A36-11D9-9E5D-000D93505B76@swipnet.se> (Jan D.'s message of "Sat, 30 Oct 2004 07:43:02 +0200")
>>> That is also possible, and seems to be what the previous discussion
>>> indicated. More work though.
>> But better result.
> I disagree, if I run Emacs on X I don't want to wade through lines of
> documentation that applies for W32/msdos/OSX.
My take on this is that if the documentation is very different for each
system, then either the function's functionality is ill-defined or the
docstring gives too much precision.
> And if the real function is in another file the benefit of clicking on "C
> source code" is reduced.
Good point. Richard's suggestion to tweak the link-following code
so as to look for macfoo.c (or w32foo.c) is a better idea.
Stefan
next prev parent reply other threads:[~2004-10-30 16:32 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 [this message]
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=m17jp8npa8.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).