From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: org-goto-local-search-headings usage? Date: Tue, 15 May 2012 11:48:55 -0400 Message-ID: <4409.1337096935@alphaville> References: <87obpp31ln.fsf@ed.ac.uk> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57573) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SUJzp-0001zR-Ke for emacs-orgmode@gnu.org; Tue, 15 May 2012 11:49:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SUJzf-0004jm-5s for emacs-orgmode@gnu.org; Tue, 15 May 2012 11:49:09 -0400 Received: from g6t0187.atlanta.hp.com ([15.193.32.64]:7994) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SUJzf-0004jO-1X for emacs-orgmode@gnu.org; Tue, 15 May 2012 11:48:59 -0400 In-Reply-To: Message from Myles English of "Tue, 15 May 2012 16:28:36 BST." <87obpp31ln.fsf@ed.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode Mode , Myles English Myles English wrote: > > Hi, > > Can anyone see what I am doing wrong here? I just want to open a file > ~/tmp/gtd.org and goto the heading "* My workflow". So, starting like > this: > > emacs -Q -l ~/tmp/gtd > > with ~/tmp/gtd: > > (add-to-list 'load-path > "~/.emacs.d/plugins/org-mode/lisp") > (require 'org-install) ;; to use the emacs-org-mode rather than the one > ;; installed with emacs > > (defun gtd() > (interactive) > (find-file "~/tmp/gtd.org") > (goto-char (point-min)) > (setq wf "My workflow") > (org-goto-local-search-headings wf nil nil) > ) > > and ~/tmp/gtd.org: > > * My workflow > > then I do: > > M-x gtd > > and get the message: > > byte-code: Search failed: "My workflow" > Works for me: the cursor is placed at the end of the headline. I tried both with just the one headline and also with half a dozen. Maybe M-x toggle-debug-on-error and try again to get a backtrace? Or add (setq debug-on-error t) to your initialization file. Nick