From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Hook Function Examples Date: Mon, 25 Jan 2010 10:48:35 -0500 Message-ID: <5002.1264434515@gamaville.dokosmarshall.org> References: <4B5CE87B.6060603@comcast.net> <2417.1264397075@gamaville.dokosmarshall.org> <4B5D3861.400@comcast.net> Reply-To: nicholas.dokos@hp.com Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZRD9-0002v0-CR for emacs-orgmode@gnu.org; Mon, 25 Jan 2010 10:50:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZRD4-0002nf-Iy for emacs-orgmode@gnu.org; Mon, 25 Jan 2010 10:50:42 -0500 Received: from [199.232.76.173] (port=36171 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZRD4-0002nH-4j for emacs-orgmode@gnu.org; Mon, 25 Jan 2010 10:50:38 -0500 Received: from vms173017pub.verizon.net ([206.46.173.17]:51424) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZRD3-0006oc-Ie for emacs-orgmode@gnu.org; Mon, 25 Jan 2010 10:50:37 -0500 Received: from gamaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173017.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KWT0077K7WZU2C1@vms173017.mailsrvcs.net> for emacs-orgmode@gnu.org; Mon, 25 Jan 2010 09:48:40 -0600 (CST) In-reply-to: Message from Mark Elston of "Sun, 24 Jan 2010 22:21:21 PST." <4B5D3861.400@comcast.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Mark Elston Cc: org-mode emacs-orgmode Mark Elston 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