From: Eli Zaretskii <eliz@gnu.org>
To: Xue Fuqiao <xfq.free@gmail.com>
Cc: 13800@debbugs.gnu.org
Subject: bug#13800: 24.3.50; About an example in "(elisp) Writing Emacs Primitives"
Date: Sun, 24 Feb 2013 17:05:09 +0200 [thread overview]
Message-ID: <83obf9kb16.fsf@gnu.org> (raw)
In-Reply-To: <20130224145548.19f7704b99f913667ab3e4bb@gmail.com>
> Date: Sun, 24 Feb 2013 14:55:48 +0800
> From: Xue Fuqiao <xfq.free@gmail.com>
>
>
> In (info "(elisp) Writing Emacs Primitives"):
>
> INTERACTIVE
> This is an interactive specification, a string such as might be
> used as the argument of `interactive' in a Lisp function. In the
> case of `or', it is 0 (a null pointer), indicating that `or'
> cannot be called interactively. A value of `""' indicates a
> function that should receive no arguments when called
> interactively. If the value begins with a `(', the string is
> evaluated as a Lisp form. For examples of the last two forms, see
> `widen' and `narrow-to-region' in `editfns.c'.
>
> In the last sentence, neither the INTERACTIVE of the example primitive
> `widen' nor `narrow-to-region' begins with a `('. I think
> `narrow-to-region' should be replaced by primitives like `insert-char'
> instead.
And then, a few years later, someone else will say that the same
happened with insert-char, yes?
I'd rather suggest to remove any references to the sources, as that is
a source of constant maintenance pains and inaccuracies in the docs.
Instead, I suggest to add to the manual an example of such a DEFUN
declaration.
next prev parent reply other threads:[~2013-02-24 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 6:55 bug#13800: 24.3.50; About an example in "(elisp) Writing Emacs Primitives" Xue Fuqiao
2013-02-24 15:05 ` Eli Zaretskii [this message]
2013-02-24 22:23 ` Xue Fuqiao
2013-04-21 11:30 ` xfq
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=83obf9kb16.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13800@debbugs.gnu.org \
--cc=xfq.free@gmail.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).