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: Org exporter: broken-link errors can't be debugged with debug-on-error [9.3 (release_9.3 @ /usr/share/emacs/28.0.50/lisp/org/)]
Date: Tue, 01 Dec 2020 01:05:28 -0500	[thread overview]
Message-ID: <87k0u2t61j.fsf@kyleam.com> (raw)
In-Reply-To: <87o8jebs92.fsf@jpl.nasa.gov>

Dima Kogan writes:

> Hi. I'm using the org included with a very recent emacs built from git.
> I have a large project consisting of many .org files that I'm exporting
> to html. Somewhere there's a broken link, so when I export the project I
> get
>   user-error: Unable to resolve link: "figures/blahblahblah.svg"
> This doesn't tell me where the problem is, specifically, so to find out
> I
>   (setq debug-on-error t)
> and go again. But something about the org code is preventing the
> debugger from triggering on this. That really shouldn't be happening.
> This is an error that's causing the export to give up and quit, and the
> debugger should come up (when debug-on-error).

It's not Org specific; it's a default behavioral difference between
error and user-error:

,----[ C-h f user-error RET ]
| [...]
| In contrast with other errors, user errors normally do not cause
| entry to the debugger, even when ‘debug-on-error’ is non-nil.
| This can be overridden by ‘debug-ignored-errors’.

> Also, it would be nice if the error message reported the source file and
> line number of the bad link.

That does sound helpful.  Completely guessing, but I would think the
source file but not the line number may be easily obtainable when the
org-link-broken error (later converted to a user-error) is signaled.

You may find setting org-export-with-broken-links to `mark' helpful for
locating the broken links, though it marks the broken links in the
output, so the results still need to be mapped back to the corresponding
source file.

      reply	other threads:[~2020-12-01  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 18:43 Bug: Org exporter: broken-link errors can't be debugged with debug-on-error [9.3 (release_9.3 @ /usr/share/emacs/28.0.50/lisp/org/)] Dima Kogan
2020-12-01  6:05 ` 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:

  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=87k0u2t61j.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).