From: "Drew Adams" <drew.adams@oracle.com>
To: "'Sean Sieger'" <sean.sieger@gmail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: documentation
Date: Sun, 26 Oct 2008 16:06:58 -0700 [thread overview]
Message-ID: <013101c937bf$8c9201f0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <87bpx70z8o.fsf@gmail.com>
> I'm trying my hand at juggling etc/NEWS, doc/lispref/*.texi and the
> elisp files of CVS Emacs. I am familiar with C-h v and C-h f,
> find-library and locate-library ... but does anyone have any advice or
> technique one could share with me in navigating NEWS, .texi and .el?
Others will no doubt have additional suggestions (e.g. for texi files).
* For NEWS, you can use `outline-minor-mode' or `outline-mode'. See the Emacs
manual, node Outline Mode. If you use `Help > Emacs News' (`C-h n') to read the
NEWS, then you are automatically put in Outline mode and View mode. `C-h m' in
the NEWS buffer will also tell you about these modes.
* Emacs Tags and Imenu are great ways to navigate code, including Emacs-Lisp
code. See the Emacs manual, node Tags and node Imenu (see also node Defuns).
* Use `M-x grep' on the source code to find stuff. See node Grep Searching of
the Emacs manual.
* Icicles has lots of features that help you find your way around Emacs and
Emacs Lisp. I shamelessly ;-) recommend it as a way to learn about Emacs and
Emacs-Lisp code. This page explains how it can help:
http://www.emacswiki.org/emacs/EmacsNewbieWithIcicles
* In addition to what is mentioned at that URL, Icicles has enhancements for
Tags, Imenu, `grep', etc. (to navigate Emacs-Lisp code), explained here:
** Tags:
http://www.emacswiki.org/emacs/Icicles_-_Tags_Enhancements
** Imenu:
http://www.emacswiki.org/emacs/Icicles_-_Other_Search_Commands#IciclesImenu
** other navigation enhancements (Info, bookmarks, search, grep, markers,...):
http://www.emacswiki.org/emacs/Icicles_-_Tripping
next prev parent reply other threads:[~2008-10-26 23:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 22:26 documentation Sean Sieger
2008-10-26 23:06 ` Drew Adams [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-02 16:07 Documentation Brandon Taylor
2021-06-08 11:25 ` Documentation pillule
2008-10-10 15:26 Documentation Eli Zaretskii
2008-10-10 17:02 ` Documentation Chong Yidong
2008-10-11 20:05 ` Documentation Alfred M. Szmidt
2008-10-11 21:22 ` Documentation Eli Zaretskii
2008-10-11 21:42 ` Documentation Chong Yidong
2008-10-12 1:23 ` Documentation Stefan Monnier
2008-10-12 3:14 ` Documentation Chong Yidong
2008-10-12 19:01 ` Documentation Alfred M. Szmidt
2005-07-31 14:08 Documentation Sean Sieger
[not found] <mailman.2129.1122754137.20277.help-gnu-emacs@gnu.org>
2005-07-30 20:27 ` Documentation Matthieu Moy
2005-07-31 3:49 ` Documentation Tim X
2005-07-30 19:36 Documentation Sean Sieger
2005-07-30 20:18 ` Documentation Lennart Borgman
2005-07-30 20:21 ` Documentation Drew Adams
2002-07-15 10:21 Documentation abhi.davande
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='013101c937bf$8c9201f0$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=sean.sieger@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 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.