From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 10783@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#10783: Some built-in functionslost their argument names
Date: Sat, 11 Feb 2012 12:01:55 +0200 [thread overview]
Message-ID: <8339ah1yek.fsf@gnu.org> (raw)
In-Reply-To: <a6mx8qp8p8.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Fri, 10 Feb 2012 18:30:59 -0500
> Cc: 10783@debbugs.gnu.org
>
> Deleting the doc-strings altogether from the duplicate definitions in
> pc-win.el would make this problem go away.
Maybe I'm missing something, but deleting the doc string from
pc-win.el shows x-get-selection-internal as "not documented" in the
MS-DOS build.
So for now, I sync'ed the doc strings with the X sources.
Note that some doc strings seem to require "more work™". E.g., this:
DEFUN ("x-disown-selection-internal", Fx_disown_selection_internal,
Sx_disown_selection_internal, 1, 3, 0,
doc: /* If we own the selection SELECTION, disown it.
Disowning it means there is no such selection.
TERMINAL should be a terminal object or a frame specifying the X
server to query. If omitted or nil, that stands for the selected
frame's display, or the first available X display. */)
(Lisp_Object selection, Lisp_Object time_object, Lisp_Object terminal)
(TIME_OBJECT is not mentioned). Or this:
DEFUN ("x-get-selection-internal", Fx_get_selection_internal,
Sx_get_selection_internal, 2, 4, 0,
doc: /* Return text selected from some X window.
SELECTION is a symbol, typically `PRIMARY', `SECONDARY', or `CLIPBOARD'.
\(Those are literal upper-case symbol names, since that's what X expects.)
TYPE is the type of data desired, typically `STRING'.
TIME_STAMP is the time to use in the XConvertSelection call for foreign
selections. If omitted, defaults to the time for the last event.
TERMINAL should be a terminal object or a frame specifying the X
server to query. If omitted or nil, that stands for the selected
frame's display, or the first available X display. */)
(Lisp_Object selection_symbol, Lisp_Object target_type,
Lisp_Object time_stamp, Lisp_Object terminal)
(refers to SELECTION, TYPE and TIME_STAMP, whereas the actual
parameters are SELECTION-SYMBOL, TARGET-TYPE, and TIME-STAMP).
next prev parent reply other threads:[~2012-02-11 10:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 21:25 bug#10783: Some built-in functionslost their argument names Glenn Morris
2012-02-10 23:04 ` Andreas Schwab
2012-02-10 23:30 ` Glenn Morris
2012-02-11 7:43 ` Andreas Schwab
2012-02-11 9:54 ` Eli Zaretskii
2012-02-11 10:01 ` Eli Zaretskii [this message]
2012-02-11 22:40 ` Glenn Morris
2012-02-12 3:23 ` Glenn Morris
2012-02-12 4:05 ` Eli Zaretskii
2012-02-12 5:14 ` Glenn Morris
2012-02-12 16:30 ` Eli Zaretskii
2012-03-06 19:50 ` Glenn Morris
2012-02-12 4:02 ` Eli Zaretskii
2012-02-12 15:28 ` Stefan Monnier
2012-02-12 16:29 ` Eli Zaretskii
2012-02-12 17:01 ` Stefan Monnier
2012-02-12 19:53 ` Glenn Morris
2012-02-13 13:19 ` Jason Rumney
2012-02-13 15:19 ` Stefan Monnier
2012-02-12 19:58 ` 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=8339ah1yek.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10783@debbugs.gnu.org \
--cc=rgm@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 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).