emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Thomas S. Dye" <tsd@tsdye.online>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
	"Thomas S. Dye" <tsd@tsdye.online>
Subject: Re: LaTeX export failure
Date: Wed, 29 Jan 2020 15:22:47 -1000	[thread overview]
Message-ID: <87k159u49k.fsf@tsdye.online> (raw)
In-Reply-To: <CA+M2ft8xQMPsgVHmaYB6rNU6qM+Xrus5AVeguoyj8VX-JqBJrA@mail.gmail.com>

Thanks John,

IIRC, this isn't the first time you've recommended that I divide 
and conquer :)

Here is the offending bit, which worked fine last November but 
fails today:

 #+caption: Compare figure\nbsp{}[[fig:mqs3_op]].

All the best,

John Hendy writes:

> On Wed, Jan 29, 2020 at 2:32 PM Thomas S. Dye <tsd@tsdye.online> 
> wrote:
>> Happy New Year!
>> Returning to a writing project after a few months absence, I'm 
>> no
>> longer able to export the writing project subtree.  Here is 
>> what I
>> find in *Messages*:
>>   Wrote /home/dk/Projects/historical-inference/r14c.org
>>   executing Shell code block...
>>   Wrote /tmp/babel-j0SOWm/ob-input-aS23DO
>>   Code block evaluation complete.
>>   match-string-no-properties: Args out of range: #<killed 
>>   buffer>,
>>   3, 11
> Are you able to share a portion of this? Or have you tried, say,
> creating a copy of the file and removing all but the first 
> heading and
> a sentence to see if it fails?
> Someone else might recognize that particular failure from past
> experience, but I'd have to try something locally. In the past 
> to
> debug I've moved all headings after the first under a new one, 
> marked
> that as :noexport:, and exported iteratively, moving each one 
> out of
> the :noexport: heading until I find the offending one. Then I 
> can hone
> in on where I should be looking.
> John
>> The writing project exported without issue on November 7, 2019.
>> I'm typically using up-to-date org-plus-contrib from Elpa, so
>> suspect my issue is due to a recent change in Org mode.
>> I don't know how to track down the problem.  Any ideas?
>> All the best,
>> Tom
>> --
>> Thomas S. Dye
>> https://tsdye.online/tsdye

Thomas S. Dye

  reply	other threads:[~2020-01-30  1:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 20:31 LaTeX export failure Thomas S. Dye
2020-01-29 23:02 ` John Hendy
2020-01-30  1:22   ` Thomas S. Dye [this message]
2020-01-30  6:53     ` Fraga, Eric
2020-01-30  8:05       ` Thomas S. Dye
2020-02-03 18:40         ` Nick Dokos

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=87k159u49k.fsf@tsdye.online \
    --to=tsd@tsdye.online \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \


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