emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kevin Liu <kevin@nivekuil.com>
To: emacs-orgmode@gnu.org
Subject: Bug: org-agenda-finalize throws args-out-of-range [9.3.6 (9.3.6-19-gf360f9-elpaplus @ /home/nivekuil/.emacs.d/elpa/org-plus-contrib-20200302/)]
Date: Mon, 02 Mar 2020 17:36:39 -0800	[thread overview]
Message-ID: <87d09u9q3c.fsf@nivekuil.com> (raw)

This bit in org-agenda-finalize:

(save-excursion
	  (while (org-activate-links (point-max))
	    (add-text-properties (match-beginning 0) (match-end 0)
				 '(face org-link))))

Will throw an error at add-text-properties:

Debugger entered--Lisp error: (args-out-of-range 0 2)
  add-text-properties(0 2 (face org-link))
  org-agenda-finalize()
  org-agenda-list(nil)
  funcall-interactively(org-agenda-list nil)
  call-interactively(org-agenda-list)
  org-agenda(nil)
  funcall-interactively(org-agenda nil)
  call-interactively(org-agenda nil nil)
  command-execute(org-agenda)

This happens after I open the agenda, C-c C-o a captured file from my
org-journal, and then open the agenda again.  The effect is that
subsequent links after the first are not styled (visible brackets, not a
link).

However, it seems like add-text-properties may be redundant, and
org-activate-links does it already?  I deleted the add-text-properties
sexp entirely and it seems to work as expected.

Emacs  : GNU Emacs 27.0.60 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.14, cairo version 1.17.3)
 of 2020-02-24
Package: Org mode version 9.3.6 (9.3.6-19-gf360f9-elpaplus @ /home/nivekuil/.emacs.d/elpa/org-plus-contrib-20200302/)

             reply	other threads:[~2020-03-03  1:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03  1:36 Kevin Liu [this message]
2020-05-24 12:27 ` Bug: org-agenda-finalize throws args-out-of-range [9.3.6 (9.3.6-19-gf360f9-elpaplus @ /home/nivekuil/.emacs.d/elpa/org-plus-contrib-20200302/)] Bastien

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=87d09u9q3c.fsf@nivekuil.com \
    --to=kevin@nivekuil.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).