From: Markus Heller <hellerm2@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Problem after updating org: C-c a a broken
Date: Fri, 28 Oct 2011 12:16:59 -0700 [thread overview]
Message-ID: <0v8vo5udsk.fsf@gmail.com> (raw)
In-Reply-To: 9724.1319828957@alphaville.americas.hpqcorp.net
Nick Dokos <nicholas.dokos@hp.com> writes:
> Markus Heller <hellerm2@gmail.com> wrote:
>
>> Hello all,
>>
>> just pulled from git.
>>
>> When I type C-c a a to pull up the agenda, I get the error shown below.
>>
>> This used to work prior to the update.
>>
>> Org version is 7.7, pulled 5 min ago on emacs 23.3.1.
>>
>> Help please, can't access my agenda anymore :(
>>
>> Thanks
>> Markus
>>
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>> format(nil "COMMENT")
>> (setq re (format org-heading-keyword-regexp-format org-comment-string))
>
> I can't reproduce this: Org-mode version 7.7 (release_7.7.485.gcfed6.dirty)
> (this is a pull from about 30mins ago plus Eric Schulte's code block keywords patch).
>
> org-heading-keyword-regexp-format is initialized to nil and made
> buffer-local in org.el It is set to a non-nil value in
> org-set-regexps-and-options which is called from org-mode. So if the
> visited files's major mode is indeed org, I cannot imagine how this
> error can come about.
>
> What happens if you visit the three files in your agenda list and *then*
> do C-c a a? While visiting each file, do C-h v
> org-heading-keyword-regexp-format RET and see if it is nil or not.
>
Hi Nick,
I've visited all 3 agenda files. C-c a a doesn't work in any of them,
and org-heading-keyword-regexp-format is NIL in all 3 of them.
Other thoughts?
Markus
next prev parent reply other threads:[~2011-10-28 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 18:36 Problem after updating org: C-c a a broken Markus Heller
2011-10-28 19:09 ` Nick Dokos
2011-10-28 19:16 ` Markus Heller [this message]
2011-10-28 19:19 ` Markus Heller
2011-10-28 19:25 ` Nick Dokos
2011-10-28 19:27 ` Nick Dokos
2011-10-28 21:11 ` Sebastien Vauban
2012-04-13 0:45 ` Jinli
2011-10-28 19:19 ` Nick Dokos
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=0v8vo5udsk.fsf@gmail.com \
--to=hellerm2@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).