From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10783@debbugs.gnu.org, schwab@linux-m68k.org
Subject: bug#10783: Some built-in functionslost their argument names
Date: Sun, 12 Feb 2012 00:14:23 -0500 [thread overview]
Message-ID: <7h62fcmy4w.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83bop4zof4.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 12 Feb 2012 06:05:51 +0200")
Eli Zaretskii wrote:
>> That fixes the problem on GNU/Linux.
>
> How and why does it do that? And what problem is that?
The problem that I reported with the argument names being lost (replaced
by ARG1 etc).
Because help-function-arglist calls help-split-fundoc which expects to
find \n\n(fn in the doc of built-in functions. It doesn't expect
functions to be built-in on some platforms and not on others.
Example:
--- pc-win.el 2012-02-11 19:22:20.968856000 -0800
+++ pc-win.el.~1~ 2012-02-11 19:21:36.185359943 -0800
@@ -289,7 +289,9 @@
FRAME should be a frame that should own the selection. If omitted or
nil, it defaults to the selected frame.
-On Nextstep, FRAME is unused."
+On Nextstep, FRAME is unused.
+
+\(fn SELECTION VALUE &optional FRAME)"
(ignore-errors
(x-select-text value))
value)
next prev parent reply other threads:[~2012-02-12 5:14 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
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 [this message]
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=7h62fcmy4w.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=10783@debbugs.gnu.org \
--cc=eliz@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).