From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Cc: Fren Zeee <frenzeee@gmail.com>
Subject: Re: Comment on Emacs Lisp Introduction
Date: Sat, 31 Jul 2010 22:14:39 +0200 [thread overview]
Message-ID: <87aap7flxs.fsf@telefonica.net> (raw)
In-Reply-To: AANLkTi=Re8pgdGokZ5x2G-0GoMmjMp6F1k659V=ZGB8g@mail.gmail.com
Fren Zeee <frenzeee@gmail.com> writes:
>> David, My problem is that I want to see the function definition of
>> next-line.
>>
> ie lisp code without having to search, find which file has it and then
> open it.
Emacs, the self-documenting text editor.
You know that whatever C-h f is, it knows what you want to know, so you
just need to investigate "C-h f". For that you can do "C-h k C-h f" for
seeing help about the function invoked with "C-h f", which is
describe-function. You use the hyperlink from the Help window to jump to
the function definition. Then you read the source code a bit or do a
quick text search to learn that what you probably want is
find-lisp-object-file-name
What's find-lisp-object-file-name? Well,
C-h f find-lisp-object-file-name RET
will tell you... and so on.
> On some platforms, I dont have the source and its an unnecessary
> interruption in the work to go and make the detour to search for it.
Sorry, I don't understand this. How do you expect seeing the function
definition without having the source code?
next prev parent reply other threads:[~2010-07-31 20:14 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
2010-07-31 19:34 ` Fren Zeee
2010-07-31 20:06 ` Drew Adams
2010-07-31 20:14 ` Óscar Fuentes [this message]
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=87aap7flxs.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--cc=emacs-devel@gnu.org \
--cc=frenzeee@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).