From: Dima Kogan <dima@secretsauce.net>
To: emacs-orgmode@gnu.org
Subject: 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: Mon, 30 Nov 2020 10:43:05 -0800 [thread overview]
Message-ID: <87o8jebs92.fsf@jpl.nasa.gov> (raw)
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).
Also, it would be nice if the error message reported the source file and
line number of the bad link.
Thanks!
Please Cc me in replies; I'm not subscribed to the list.
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/)
next reply other threads:[~2020-11-30 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 18:43 Dima Kogan [this message]
2020-12-01 6:05 ` 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/)] Kyle Meyer
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=87o8jebs92.fsf@jpl.nasa.gov \
--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).