From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30068@debbugs.gnu.org
Subject: bug#30068: 26.0; REGRESSION: no doc for `x-display-pixel-*'
Date: Sat, 20 Jan 2018 13:14:06 -0500 [thread overview]
Message-ID: <yolggs2ya9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83vag619ks.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Jan 2018 09:50:27 +0200")
Eli Zaretskii wrote:
> So you want to special-case pc-win.el?
No.
> I thought this was a more general proposal.
Yes.
>> In addition, all the X/W32/NS "x-" doc-strings need to be combined so
>> that the X version describes all platforms. I thought this was already
>> done, but in one of the first cases I looked it, it wasn't. But this has
>> to be done anyway in the "real" solution, so the effort won't be wasted.
>
> I'm not sure I understand: I thought we made all the doc strings of
> such functions identical some time ago, to avoid this issue. Which
> doc strings are not identical between different implementations?
The first one I happened to look at was x-server-max-request-size.
Cf nsfns.m and xfns.c.
>> + /* Ignore docs that start with SKIP. These mark
>> + placeholders where the real doc is elsewhere. */
>
> This must be in the ELisp manual, of course, and perhaps also in NEWS.
I don't see why an internal implementation detail that will be
self-documenting ("SKIP: real doc in xfns.c") needs to be in the
manual and NEWS, but if you say so.
Is this change then approved?
next prev parent reply other threads:[~2018-01-20 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 18:11 bug#30068: 26.0; REGRESSION: no doc for `x-display-pixel-*' Drew Adams
2018-01-10 19:26 ` Eli Zaretskii
2018-01-10 19:41 ` Glenn Morris
2018-01-10 20:21 ` Eli Zaretskii
2018-01-11 19:26 ` Glenn Morris
2018-01-11 20:19 ` Eli Zaretskii
2018-01-11 20:25 ` Eli Zaretskii
2018-01-13 0:16 ` Glenn Morris
2018-01-13 7:50 ` Eli Zaretskii
2018-01-20 18:14 ` Glenn Morris [this message]
2018-01-20 18:58 ` Eli Zaretskii
2018-01-11 19:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yolggs2ya9.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=30068@debbugs.gnu.org \
--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.