emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Mark Elston <m_elston@comcast.net>
Cc: org-mode emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Hook Function Examples
Date: Mon, 25 Jan 2010 10:48:35 -0500	[thread overview]
Message-ID: <5002.1264434515@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Mark Elston <m_elston@comcast.net> of "Sun, 24 Jan 2010 22:21:21 PST." <4B5D3861.400@comcast.net>

Mark Elston <m_elston@comcast.net> wrote:

> 
> OK.  From what I read I am assuming that a buffer is created with some
> already-processed (though not completely) org data as its initial
> content.  Then, at some point, these hook functions are called on this
> new buffer.  I assume this is the case since you wouldn't want to go
> modifying the original buffer - though this is not stated anywhere that
> I can find.
> 
> Some hook functions apparently *do* take parameters (e.g.
> org-cycle-hook, etc) and I wasn't sure about the ones that didn't
> mention any.
> 

Yes - it is (in the terminology of the Elisp Ref manual) an "abnormal"
hook and should not be called ``org-cycle-hook'', but the convention is not
enforced.

> I was just trying to find my way and didn't have a map of what was
> where.  Even the org-export-blocks-preprocess()  function is a little
> difficult to wade through for someone not really familiar with elisp.
> I think I have pieced it together, though.  This may give me what I need
> to do what I want (remove some specific kinds of headers when creating
> certain LaTeX files).
> 
> Are my assumptions above correct, then?
> 

I think so.

Nick

  reply	other threads:[~2010-01-25 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-25  0:40 Hook Function Examples Mark Elston
2010-01-25  5:24 ` Nick Dokos
2010-01-25  6:21   ` Mark Elston
2010-01-25 15:48     ` Nick Dokos [this message]
2010-01-28 18:22     ` Carsten Dominik

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=5002.1264434515@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=m_elston@comcast.net \
    /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).