emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: emacs-orgmode@gnu.org
Subject: [BUG] Formatting of bracketed numbers in included source files
Date: Wed, 30 Apr 2014 01:55:29 -0400	[thread overview]
Message-ID: <8738gv744u.fsf@kmlap.domain.org> (raw)

Hello,

I'm experiencing issues including a file during export if that file has
a single number surrounded by brackets.

,----[ test.org ]
| #+include: "test.py" src Python
`----

,----[ test.py ]
| x = [1]
`----

With the current master (51893a4), trying to export test.org leads to
the following error.

,----
| Debugger entered--Lisp error: (error "Format specifier doesn't match argument type")
|   format("fn:%d-" "nil")
|   org-export--prepare-file-contents("/tmp/test.py" nil)
|   org-export-expand-include-keyword()
|   org-export-as(ascii nil nil nil (:ascii-charset ascii))
|   org-export-to-buffer(ascii "*Org ASCII Export*" nil nil nil nil (:ascii-charset ascii) #[nil "\300 \207" [text-mode] 1])
|   org-ascii-export-as-ascii(nil nil nil nil (:ascii-charset ascii))
|   (lambda (a s v b) (org-ascii-export-as-ascii a s v b (quote (:ascii-charset ascii))))(nil nil nil nil)
|   org-export-dispatch(nil)
|   ad-Orig-call-interactively(org-export-dispatch nil nil)
|   call-interactively(org-export-dispatch nil nil)
`----

It seems that `org-export--prepare-file-contents' is treating "[1]" as a
footnote. Bisecting this error suggests commit
b8781c4c85f0d51cecb32e5192b5049e8f241939 introduced the issue.

--
Kyle

             reply	other threads:[~2014-04-30  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30  5:55 Kyle Meyer [this message]
2014-04-30  7:34 ` [BUG] Formatting of bracketed numbers in included source files Nicolas Goaziou
2014-04-30 15:00   ` 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=8738gv744u.fsf@kmlap.domain.org \
    --to=kyle@kyleam.com \
    --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).