From: Jambunathan K <kjambunathan@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Exporter] How to save 'info' plist for later use?
Date: Wed, 10 Jul 2013 22:46:50 +0530 [thread overview]
Message-ID: <8761wi5o8t.fsf@gmail.com> (raw)
In-Reply-To: <87a9lufj44.fsf@gmail.com> (Thorsten Jolitz's message of "Wed, 10 Jul 2013 18:57:31 +0200")
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Looking in the source-code is of course the best way to find out, but I
> thought I would have access to all function-names anyway with
>
> ,----------------------
> | C-h f org-export- TAB
> `----------------------
>
> until I figured out that defining some autoloads and actually loading
> the whole library are two different things, and that I will find all
> functions that way only after doing an explicit 'M-x load-library' or
> after actually using it ... ;)
There is an outline struture to the way source code is organized.
(add-hook 'emacs-lisp-mode-hook 'outline-minor-mode)
(add-hook 'outline-minor-mode-hook
(lambda ()
(define-key outline-minor-mode-map [(control tab)] 'org-cycle)
;; (define-key outline-minor-mode-map [(shift tab)] 'org-global-cycle)
(define-key outline-minor-mode-map [backtab] 'org-global-cycle)
))
Now doing
M-x find-library RET ox.el RET
S-TAB (one or more times)
will give you a give quick overview of all the function names.
----------------------------------------------------------------
Also there is always this:
C-1 C-x $
which can be expected to give a quick overview any source file.
Just snap out with:
C-x $
----------------------------------------------------------------
Or you can build a TAGS file (ctags/etags) and you can find all commands
that match a regexp.
----------------------------------------------------------------
prev parent reply other threads:[~2013-07-10 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 10:56 [Exporter] How to save 'info' plist for later use? Thorsten Jolitz
2013-07-10 11:34 ` Robert Klein
2013-07-10 12:21 ` Thorsten Jolitz
2013-07-10 15:41 ` Eric Abrahamsen
2013-07-10 11:46 ` Thorsten Jolitz
2013-07-10 12:17 ` Nick Dokos
2013-07-10 12:30 ` Thorsten Jolitz
2013-07-10 13:59 ` Jambunathan K
2013-07-10 15:33 ` Thorsten Jolitz
2013-07-10 15:40 ` Eric Abrahamsen
2013-07-10 16:57 ` Thorsten Jolitz
2013-07-10 17:16 ` Jambunathan K [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761wi5o8t.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tjolitz@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/org-mode.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).