emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dima Kogan <dima@secretsauce.net>
To: emacs-orgmode@gnu.org
Subject: Bug: Following a link to a #+NAME causes '(wrong-type-argument stringp nil)' [9.3 (release_9.3 @ /usr/share/emacs/28.0.50/lisp/org/)]
Date: Sun, 22 Nov 2020 12:44:28 -0800	[thread overview]
Message-ID: <875z5xf7f7.fsf@secretsauce.net> (raw)

Hi. I'm using the org included with a recent build from emacs git. I
have this tst.org:




[[name][link]]

* heading
#+NAME: name

text




I open it with 'emacs -Q'. I move the point to the link at the top, and
C-c C-o to follow the link. This doesn't work:

  Debugger entered--Lisp error: (wrong-type-argument stringp nil)
    string-match("[ \f\11\n\15\13]+" nil 0)
    split-string(nil)
    org-link-search("name" 3)
    org-link-open((link (:type "fuzzy" :path "name" :format bracket :raw-link "name" :application nil :search-option nil :begin 1 :end 15 :contents-begin 9 :contents-end 13 :post-blank 0 :parent (paragraph (:begin 1 :end 17 :contents-begin 1 :contents-end 16 :post-blank 1 :post-affiliated 1 :parent nil)))) nil)
    org-open-at-point(nil)
    funcall-interactively(org-open-at-point nil)

Apparently org doesn't like the empty line right after the #+NAME tag.
Removing that empty line makes it work.

Thanks!
 

Emacs  : GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.23, cairo version 1.16.0)
 of 2020-09-29, unofficial emacs-snapshot build: http://emacs.secretsauce.net
Package: Org mode version 9.3 (release_9.3 @ /usr/share/emacs/28.0.50/lisp/org/)


             reply	other threads:[~2020-11-22 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 20:44 Dima Kogan [this message]
2020-11-27  4:49 ` Bug: Following a link to a #+NAME causes '(wrong-type-argument stringp nil)' [9.3 (release_9.3 @ /usr/share/emacs/28.0.50/lisp/org/)] Dante Catalfamo
2020-12-01  5:14 ` Kyle Meyer
2020-12-01  5:19   ` Dima Kogan

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=875z5xf7f7.fsf@secretsauce.net \
    --to=dima@secretsauce.net \
    --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).