emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Salazar <cycleofsong@gmail.com>
To: Peter Salazar <cycleofsong@gmail.com>, org-mode <emacs-orgmode@gnu.org>
Subject: Re: org-agenda error
Date: Tue, 15 Mar 2016 19:58:29 -0400	[thread overview]
Message-ID: <CAE+_6TyLTV-ZnfEk9Bfm8K66CP-7LpOYJ6kpQScCvYQ1Q-WxhQ@mail.gmail.com> (raw)
In-Reply-To: <87h9gen3oi.fsf@nicolasgoaziou.fr>

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Unfortunately, that's not the case (that helm-org-in-buffer-headings) is
called in a non-org buffer. It happens whenever I call it from within any
org-file. I also tried calling it from within a short, minimal org-file
with just a few headings of various levels, and I get the same error.

The error, once again, is this:
http://i.imgur.com/FoTiwoq.png

And again, the error I get when I call org-agenda is this:
http://pastebin.com/wCBgAQLp

On Thu, Mar 10, 2016 at 3:21 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Hello,
>
> Peter Salazar <cycleofsong@gmail.com> writes:
>
> > Any thoughts on that? I'm not sure if it's related, but I also get errors
> > when I try to call helm-org-in-buffer-headings. Somehow the backtrace
> gets
> > immediately erased, so here's a screenshot:
> > http://i.imgur.com/FoTiwoq.png
>
> From the above, it looks like `helm-org--get-candidate-in-file' is
> erroneously called from a non-Org buffer (here, "*Backtrace*").  Outside
> Org, `org-complex-heading-regexp' is nil, hence the result.
>
> Regards,
>
> --
> Nicolas Goaziou
>

[-- Attachment #2: Type: text/html, Size: 1955 bytes --]

  reply	other threads:[~2016-03-15 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06  3:49 org-agenda error Peter Salazar
2016-03-07 11:09 ` Nicolas Goaziou
2016-03-07 15:40   ` Peter Salazar
2016-03-10  3:44     ` Peter Salazar
2016-03-10  8:21       ` Nicolas Goaziou
2016-03-15 23:58         ` Peter Salazar [this message]
2016-03-16  1:11           ` Peter Salazar

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=CAE+_6TyLTV-ZnfEk9Bfm8K66CP-7LpOYJ6kpQScCvYQ1Q-WxhQ@mail.gmail.com \
    --to=cycleofsong@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).