all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 4402@emacsbugs.donarmstrong.com
Subject: bug#4402: apropos-documentation and platform-specific docs
Date: Sat, 12 Sep 2009 15:45:55 -0400	[thread overview]
Message-ID: <jwvtyz8hrst.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <83zl90zgmk.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 12 Sep 2009 11:55:47 +0300")

>> > DOC is an architecture-independent file, so it must include the doc
>> > strings of all symbols.
>> My question is, why must DOC be architecture independent?
>> There are certianly drawbacks to this, so what's the benefit?

Actually, I can't think of many drawbacks.  Most of the problems we face
in this respect are just the tip of the iceberg, where the rest of the
iceberg is the inconsistency we have in the different implementations of
"the same" function/variable.
If we fix the real underlying problems, then there are no problems with
the DOC file.


        Stefan





  reply	other threads:[~2009-09-12 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11  7:01 bug#4402: apropos-documentation and platform-specific docs Glenn Morris
2009-09-11  9:02 ` Eli Zaretskii
2009-09-11 18:05   ` Glenn Morris
2009-09-12  8:55     ` Eli Zaretskii
2009-09-12 19:45       ` Stefan Monnier [this message]
     [not found]         ` <os1vmatjml.fsf@fencepost.gnu.org>
2009-09-14  1:20           ` Processed: " Emacs bug Tracking System
2017-12-04  3:05           ` Glenn Morris
2009-09-11 19:04 ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=jwvtyz8hrst.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=4402@emacsbugs.donarmstrong.com \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.