From: "Drew Adams" <drew.adams@oracle.com>
To: "'Francis Moreau'" <francis.moro@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: How to get skills in elisp ?
Date: Mon, 25 May 2009 10:11:12 -0700 [thread overview]
Message-ID: <E156081AD5124AEE97DCE8A075680D39@us.oracle.com> (raw)
In-Reply-To: <9c718a3f-d913-4a8d-b928-443c7e9d25d4@r34g2000vbi.googlegroups.com>
> > Yes, take a look at the manual (in Info, `C-h i') called `Emacs Lisp
> > Introduction' in the Info menu. The manual title is
> > actually "An Introduction to
> > Programming in Emacs Lisp". It's just what you're looking for.
>
> Ok, I did have a look to this but it starts by;
>
> "This is an `Introduction to Programming in Emacs Lisp', for people
> who are not programmers."
>
> so since I'm a programmer (well I try to be ;) I just skiped the
> document.
;-) !!!
That was probably written to avoid scaring away non-programmers.
It really should say something like "for non-programmers and programmers who are
not necessarily familiar with Lisp. Really, it's for anyyone interested in Emacs
Lisp.
> Is there any way to jump into a function definition (for example by
> using tags) when asking for help on this function (C-h f) ?
After `C-h f' (or `C-h v' for variables), you should see a link to the defining
source file near the beginning of the help text. Examples:
eval-defun is an interactive compiled Lisp function in `lisp-mode.el'.
forward-char is an interactive built-in function in `C source code'.
The text `lisp-mode.el' and the text `C source code' are links - click them to
go to the definitions of functions `eval-defun' and `forward-char'. You will not
be able to do the latter if you don't have a copy of the C source code (in
directory `src' under your Emacs installation directory). To see the former, you
will likewise need a copy of the Lisp source code file, in this case
`lisp-mode.el'.
You should always make sure you have a copy of all of the Lisp source code files
for the libraries that you use. It's an invaluable help to consult the source
code. If you have only the byte-compiled files (*.elc instead of *.el), then go
to gnu.org and pick up the source files now.
Yes, you can also use a tags file. For that, you will need to create the tags
file. Consult the doc or Emacs Wiki for more info. Once you have a tags file,
you can easily get to any function etc. definitions. This is an alternative to
using `C-h f' and then following the link to the defining code.
next prev parent reply other threads:[~2009-05-25 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 7:30 How to get skills in elisp ? Francis Moreau
2009-05-25 8:17 ` Drew Adams
[not found] ` <mailman.7753.1243239425.31690.help-gnu-emacs@gnu.org>
2009-05-25 9:15 ` Francis Moreau
2009-05-25 10:22 ` Pascal J. Bourguignon
2009-05-25 11:50 ` Andreas Röhler
2009-05-25 12:42 ` Richard Riley
2009-05-25 13:51 ` Pascal J. Bourguignon
2009-05-25 14:18 ` Richard Riley
2009-05-26 7:58 ` Francis Moreau
2009-05-25 17:11 ` Drew Adams [this message]
[not found] ` <mailman.7774.1243271469.31690.help-gnu-emacs@gnu.org>
2009-05-25 19:41 ` Francis Moreau
2009-05-25 20:52 ` Drew Adams
2009-05-25 10:04 ` Tassilo Horn
2009-05-25 11:01 ` Pascal J. Bourguignon
2009-05-25 12:03 ` Andreas Röhler
2009-05-27 13:05 ` Thien-Thi Nguyen
-- strict thread matches above, loose matches on Subject: below --
2009-05-28 7:09 Benjamin Badgley
2009-05-28 15:55 ` Drew Adams
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=E156081AD5124AEE97DCE8A075680D39@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=francis.moro@gmail.com \
--cc=help-gnu-emacs@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.
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).