From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 3888@emacsbugs.donarmstrong.com
Subject: bug#3888: Some variables get the wrong, platform-specific, documentation
Date: Tue, 21 Jul 2009 12:18:27 -0400 [thread overview]
Message-ID: <jwvljmi9fkm.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <87ws63gkzh.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 20 Jul 2009 16:25:38 -0400")
> I think, as a temporary solution, we should make the docstrings of all
> the affected functions and variables the same. If necessary, they can
> say somehthing like, "On Windows, this does X. On Nexstep, this does
> Y", and so on.
That sounds OK as a quick temporary solution. The longer-term solution
is to say that such variables defined in various places are bugs.
I.e. the definition should be moved to a common file.
Stefan
next prev parent reply other threads:[~2009-07-21 16:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 20:25 bug#3888: Some variables get the wrong, platform-specific, documentation Chong Yidong
2009-07-21 3:12 ` Eli Zaretskii
2009-07-21 16:18 ` Stefan Monnier [this message]
2009-07-21 18:30 ` Eli Zaretskii
2009-07-22 18:32 ` Stefan Monnier
2009-07-22 18:45 ` Eli Zaretskii
2009-07-23 2:43 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2009-07-20 21:33 bug#3888: " Chong Yidong
2009-07-21 18:59 ` Eli Zaretskii
[not found] <83k51y3up4.fsf@gnu.org>
2009-07-20 18:21 ` Glenn Morris
2009-07-20 18:56 ` Eli Zaretskii
2009-07-24 16:40 ` bug#3888: marked as done (Some variables get the wrong, platform-specific, documentation) Emacs bug Tracking System
2009-07-24 17:41 ` bug#3888: Some variables get the wrong, platform-specific, documentation Glenn Morris
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=jwvljmi9fkm.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=3888@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
/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).