From: Kyle Meyer <kyle@kyleam.com>
To: Simon Thum <simon.thum@gmx.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Regression in Org triggered from helm
Date: Sat, 31 Oct 2015 12:56:36 -0400 [thread overview]
Message-ID: <87vb9n0yez.fsf@kyleam.com> (raw)
In-Reply-To: <87vb9ojm8k.fsf@kyleam.com> (Kyle Meyer's message of "Fri, 30 Oct 2015 13:32:27 -0400")
Kyle Meyer <kyle@kyleam.com> writes:
> Simon Thum <simon.thum@gmx.de> writes:
>
>> I was a bit early; I am getting this error now:
>>
>> Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
>> replace-regexp-in-string("[ ]+\\'" "" nil)
>> (lambda (s) (replace-regexp-in-string "[ ]+\\'" "" s))(nil)
>> mapconcat((lambda (s) (replace-regexp-in-string "[ ]+\\'" "" s))
>> (#("Aktionen" 0 8 (face org-level-1)) #("Stellensuche" 0 12 (face
>> org-level-2)) #("Kandidaten" 0 10 (face org-level-3)) nil) "/")
>>
>>
>> I bet it's my habit of putting slashes into headlines which breaks the
>> logic. However it worked before.
>
> I can reproduce this with a buffer containing an empty heading.
> (Slashes should work fine.)
>
> org-format-outline-path takes a list of strings for path elements. It
> handles an empty list fine, but helm-get-org-candidates-in-file is
> passing it (nil). I'll update org-format-outline-path to discard nil
> path elements, but I should also probably submit a patch to helm to make
> it ignore empty headers rather than passing a non-string list.
This error should be fixed as of 59d7062.
--
Kyle
prev parent reply other threads:[~2015-10-31 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 20:22 Regression in Org triggered from helm Simon Thum
2015-10-26 20:58 ` Kyle Meyer
2015-10-27 21:48 ` Simon Thum
2015-10-26 22:40 ` Kyle Meyer
2015-10-28 6:29 ` Kyle Meyer
2015-10-28 13:34 ` Nicolas Goaziou
2015-10-31 12:14 ` Simon Thum
2015-10-31 16:50 ` Simon Thum
2015-10-30 17:32 ` Kyle Meyer
2015-10-31 16:56 ` Kyle Meyer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb9n0yez.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=simon.thum@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.