From: Dan Nicolaescu <dann@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 6588@debbugs.gnu.org
Subject: bug#6588: 24.0.50; built-in Lisp functions look strange
Date: Thu, 08 Jul 2010 22:36:52 -0400 [thread overview]
Message-ID: <yxqvd8p1iuz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <b4mwrt5v2cx.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri\, 09 Jul 2010 11\:02\:54 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Emacs head I built today looks strange; many built-in Lisp functions
> have `LISP-OBJECT' as the first argument. For example:
Please update again.
>
> ,----
> | kill-buffer is an interactive built-in function in `C source code'.
> |
> | It is bound to C-x k.
> |
> | (kill-buffer &optional LISP-OBJECT BUFFER-OR-NAME)
> |
> | Kill buffer BUFFER-OR-NAME.
> | [...]
> `----
>
> ,----
> | raise-frame is an interactive built-in function in `C source code'.
> |
> | (raise-frame &optional LISP-OBJECT FRAME)
> |
> | Bring FRAME to the front, so it occludes any frames it overlaps.
> | [...]
> `----
>
> This seems to be due to the recent change:
>
> Dan Nicolaescu wrote:
>> ------------------------------------------------------------
>> revno: 100758
>> committer: Dan Nicolaescu <dann@ics.uci.edu>
>> branch nick: trunk
>> timestamp: Thu 2010-07-08 14:25:08 -0700
>> message:
>> Convert DEFUNs to standard C.
>> * src/alloc.c: Convert DEFUNs to standard C.
>> * src/buffer.c:
> [...]
>> Diff too large for email (13107 lines, the limit is 10000).
>
> In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
> of 2010-07-09 on ******
> Windowing system distributor `Fedora Project', version 11.0.10802000
> configured using `configure '--verbose' '--with-x-toolkit=lucid'\
> '--without-xim''
next prev parent reply other threads:[~2010-07-09 2:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 2:02 bug#6588: 24.0.50; built-in Lisp functions look strange Katsumi Yamaoka
2010-07-09 2:36 ` Dan Nicolaescu [this message]
2010-07-09 3:18 ` Katsumi Yamaoka
2010-07-09 3:43 ` Dan Nicolaescu
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=yxqvd8p1iuz.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=6588@debbugs.gnu.org \
--cc=yamaoka@jpl.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.