From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>
Cc: 10057@debbugs.gnu.org
Subject: bug#10057: 24.0.91; doc string of `Info-find-file'
Date: Tue, 15 Nov 2011 14:21:04 -0800 [thread overview]
Message-ID: <07F6A0871C094E70B3ED250E4B93F9EF@us.oracle.com> (raw)
In-Reply-To: <m21ut9c9pf.fsf@igel.home>
> You are supposed to use only the value that is documented. This is
> called future compatibility.
In that case, if that is truly a worry, then the doc should say that. As it is,
the doc is vague and incomplete. It does not at all convey the interpretation
you are adding here.
Hey - pick any set of supported values and associated behaviors you like. Have
them mean whatever you like. But document what they do, completely and
unambiguously. If non-nil other than `t' is to be unsupported or discouraged
for reasons of <whatever>, then say so.
Sheesh. This really should be a no-brainer.
next prev parent reply other threads:[~2011-11-15 22:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 20:30 bug#10057: 24.0.91; doc string of `Info-find-file' Drew Adams
2011-11-15 21:39 ` Juri Linkov
2011-11-15 21:56 ` Drew Adams
2011-11-15 22:17 ` Andreas Schwab
2011-11-15 22:21 ` Drew Adams [this message]
2011-11-15 21:50 ` Stefan Monnier
2011-11-15 22:08 ` Drew Adams
2011-11-16 2:28 ` Stefan Monnier
2011-11-16 2:29 ` Stefan Monnier
2011-11-16 3:05 ` Drew Adams
2011-11-16 3:24 ` Glenn Morris
2011-11-16 5:23 ` Drew Adams
2011-11-16 4:22 ` Stefan Monnier
2011-11-16 5:24 ` Drew Adams
2011-11-16 8:34 ` Eli Zaretskii
2011-11-16 14:52 ` Drew Adams
2011-11-16 18:10 ` Eli Zaretskii
2011-11-16 18:29 ` Drew Adams
2011-11-16 18:43 ` Memnon Anon
2011-11-16 19:56 ` Eli Zaretskii
2011-11-16 17:03 ` Juri Linkov
2011-11-16 18:29 ` Drew Adams
2011-11-16 19:31 ` Juri Linkov
2011-11-16 20:04 ` Drew Adams
2011-11-16 20:28 ` Juri Linkov
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=07F6A0871C094E70B3ED250E4B93F9EF@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=10057@debbugs.gnu.org \
--cc=schwab@linux-m68k.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.