emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Dima Kogan <dima@secretsauce.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: 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: Tue, 01 Dec 2020 00:14:42 -0500	[thread overview]
Message-ID: <87mtyyt8e5.fsf@kyleam.com> (raw)
In-Reply-To: <875z5xf7f7.fsf@secretsauce.net>

Dima Kogan writes:

> 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)
> Apparently org doesn't like the empty line right after the #+NAME tag.
> Removing that empty line makes it work.

Thanks for the report.  As suggested in Dante's reply, the blank line
following #+name is invalid syntax.


On maint (3bb073b63), the type error is now avoided for invalid name
keywords.  No attempt is made to match these keywords, though, so your
example won't lead to a match aside from through a fuzzy text search
when org-link-search-must-match-exact-headline is nil.

  parent reply	other threads:[~2020-12-01  5:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-22 20:44 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/)] Dima Kogan
2020-11-27  4:49 ` Dante Catalfamo
2020-12-01  5:14 ` Kyle Meyer [this message]
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:

  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=87mtyyt8e5.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=dima@secretsauce.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).