Hello,
Nick Dokos writes:
> Evaluate the following form:
>
> (let ((org-agenda-overriding-header "")) (org-agenda-list))
>
> It fails with
>
> org-agenda-list: Args out of range: 0, 1
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
---
FWIW I do not see this issue on the latest version of org on the master
(dev) branch.
Based on the backtrace, it looks like for some reason comment-start-skip is
nil in your emacs session.
Here's the definition of org-agenda-skip:
(defun org-agenda-skip ()
"Throw to `:skip' in places that shou
Trying again since it wasn't received the first time.
On Tue, Aug 2, 2016 at 12:02 PM Robert Irelan wrote:
> Ever since updating to 20160801, I've encountered the following error
> whenever trying to run org-agenda-list:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>
Ever since updating to 20160801, I've encountered the following error
whenever trying to run org-agenda-list:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
looking-at(nil)
org-agenda-skip()
org-agenda-get-deadlines()
org-agenda-get-day-entries("/path/t
On 7/11/2013 1:51 PM, Charles wrote:
Thank you Nick. I can now uncomment my (:newline . t)'s
Charlie
Oops, that's (:newline . nil)
On 7/11/2013 8:50 AM, Nick Dokos wrote:
Bastien writes:
Rainer Stengele writes:
Yes, the fix works!
Applied, thanks.
Thanks! I just pulled again and I don't see the error any more.
Thank you Nick. I can now uncomment my (:newline . t)'s
Charlie
Bastien writes:
> Rainer Stengele writes:
>
>> Yes, the fix works!
>
> Applied, thanks.
Thanks! I just pulled again and I don't see the error any more.
--
Nick
Rainer Stengele writes:
> Yes, the fix works!
Applied, thanks.
--
Bastien
Am 11.07.2013 08:38, schrieb Bastien:
> Hi Nick,
>
> Nick Dokos writes:
>
>> I just pulled and I get the attached backtrace from org-agenda-list.
>> I tried with -q -l minimal.emacs and it's still there.
>> It's probably caused by commit 42691788273cecb75ec620d40cc5394d2cd95ed1.
>> When I revert
Hi Nick,
Nick Dokos writes:
> I just pulled and I get the attached backtrace from org-agenda-list.
> I tried with -q -l minimal.emacs and it's still there.
> It's probably caused by commit 42691788273cecb75ec620d40cc5394d2cd95ed1.
> When I revert that, the agenda comes up properly.
I'm in a hur
Nick Dokos writes:
> I just pulled and I get the attached backtrace from org-agenda-list.
> I tried with -q -l minimal.emacs and it's still there.
> It's probably caused by commit 42691788273cecb75ec620d40cc5394d2cd95ed1.
> When I revert that, the agenda comes up properly.
>
> Org-mode version 8.
I just pulled and I get the attached backtrace from org-agenda-list.
I tried with -q -l minimal.emacs and it's still there.
It's probably caused by commit 42691788273cecb75ec620d40cc5394d2cd95ed1.
When I revert that, the agenda comes up properly.
Org-mode version 8.0.5 (release_8.0.5-334-g1b1469 @
13 matches
Mail list logo
