From: Fren Zeee <frenzeee@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Comment on Emacs Lisp Introduction
Date: Sat, 31 Jul 2010 12:33:31 -0700 [thread overview]
Message-ID: <AANLkTim8a6FrOnOqx9ge9p5wHb4xQnA9RHQrE7RxzD8C@mail.gmail.com> (raw)
In-Reply-To: <877hkc2i7f.fsf@lola.goethe.zz>
On Sat, Jul 31, 2010 at 1:01 AM, David Kastrup <dak@gnu.org> wrote:
> Fren Zeee <frenzeee@gmail.com> writes:
>
>> Robert, does your intro book explain things like how to get the full
>> definition of a function like for example
>>
>> next-line which is a down arrow
>>
>> (symbol-function 'next-line)
>> #[(arg) " \203& [next-line-add-newlines arg abbrev-mode 1 nil "
>> " line-move (line-move arg) ((... ...))] 3 1337315 "p"]
>>
>> I could not figure out from online doc and apropos how to do it.
>
> Huh?
>
> C-h f next-line RET gives the online doc, and the very first line is
>
> next-line is an interactive compiled Lisp function in `simple.el'.
>
> where the string `simple.el' is a hyperlink leading to the definition of
> next-line in simple.el. So I don't understand what problem you
> encountered using the online documentation. You can also use
> M-x find-function RET next-line RET
> to get to the source.
>
> What is your problem?
David, My problem is that I want to see the function definition of next-line.
next prev parent reply other threads:[~2010-07-31 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinmXz=n0L4RS0SHRiJcA-Ob135RrKEzrZ=GvjDy@mail.gmail.com>
2010-07-29 22:22 ` Comment on Emacs Lisp Introduction Robert J. Chassell
[not found] ` <AANLkTi=SAbC_y+O3simX2dSLFYcpyVxPR-yZYsCMje42@mail.gmail.com>
2010-07-30 14:44 ` Robert J. Chassell
2010-07-31 7:43 ` Fren Zeee
2010-07-31 8:01 ` David Kastrup
2010-07-31 19:33 ` Fren Zeee [this message]
2010-07-31 19:34 ` Fren Zeee
2010-07-31 20:06 ` Drew Adams
2010-07-31 20:14 ` Óscar Fuentes
2010-08-01 6:36 ` David Kastrup
2010-08-01 12:06 ` Harald Hanche-Olsen
2010-08-02 8:26 ` Stephen J. Turnbull
2010-08-02 18:27 ` Fren Zeee
2010-08-03 3:26 ` Stephen J. Turnbull
2010-08-04 3:19 ` Fren Zeee
2010-08-04 5:25 ` Stephen J. Turnbull
2010-08-04 9:22 ` David Kastrup
2010-08-05 20:13 ` Fren Zeee
2010-08-05 20:27 ` Fren Zeee
2010-08-01 12:50 ` Óscar Fuentes
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=AANLkTim8a6FrOnOqx9ge9p5wHb4xQnA9RHQrE7RxzD8C@mail.gmail.com \
--to=frenzeee@gmail.com \
--cc=dak@gnu.org \
--cc=emacs-devel@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 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).