From: Ihor Radchenko <yantar92@posteo.net>
To: pva-outdoor@yandex.ru
Subject: Re: [BUG] ox-texinfo can't export example blocks [9.6.9 (release_9.6.9 @ /usr/local/share/emacs/30.0.50/lisp/org/)]
Date: Sat, 24 Feb 2024 10:05:06 +0000 [thread overview]
Message-ID: <87frxixjn1.fsf@localhost> (raw)
In-Reply-To: <877cj0swz1.fsf@yandex.ru>
[ Adding Org mailing list back to CC for public record ]
pva-outdoor@yandex.ru writes:
>> Please describe your problem in more details. What do you mean by "can't
>> export"? See https://orgmode.org/manual/Feedback.html#Feedback
>
> To reproduce my problem you can write create an org-mode buffer (C-x b
> 1.org M-x org-mode) with the following content:
>
> #+begin_src lua :tangle yes :noweb yes
> aaa
> <<second>>
> #+end_src
>
> #+name: second
> #+begin_src
> bbb
> #+end_src
>
> Then enable exporting to texinfo and export the buffer:
> M-: (require 'ox-texinfo)
> C-c C-e i t
>
> The folllowing backtrace appears (providing you already enabled
> debugging on errors):
Thanks!
I fixed this and similar problems on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f90322377
Fixed.
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> apply(debug error (wrong-type-argument stringp nil))
> edebug(error (wrong-type-argument stringp nil))
> signal(wrong-type-argument (stringp nil))
> edebug-signal(wrong-type-argument (stringp nil))
> string-match("lisp" nil nil t)
> string-match-p("lisp" nil)
> ...
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-02-24 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 15:17 [BUG] ox-texinfo can't export example blocks [9.6.9 (release_9.6.9 @ /usr/local/share/emacs/30.0.50/lisp/org/)] pva-outdoor
2024-02-18 15:38 ` Ihor Radchenko
[not found] ` <877cj0swz1.fsf@yandex.ru>
2024-02-24 10:05 ` Ihor Radchenko [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frxixjn1.fsf@localhost \
--to=yantar92@posteo.net \
--cc=pva-outdoor@yandex.ru \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.