From: Ihor Radchenko <yantar92@posteo.net>
To: pva-outdoor@yandex.ru
Cc: emacs-orgmode@gnu.org
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: Sun, 18 Feb 2024 15:38:53 +0000 [thread overview]
Message-ID: <87a5nxsrxu.fsf@localhost> (raw)
In-Reply-To: <87jzn7oz1u.fsf@yandex.ru>
pva-outdoor@yandex.ru writes:
> It seems that in ox-texinfo.el the `string-match-p' is used instead of
> `string-equal' (here is my patch):
`string-match-p' is used there on purpose to mark lisp, emacs-lisp, and
even elisp blocks with @lisp Texinfo markup.
See https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#g_t_0040lisp
> ... the
> :language property is nil for #+BEGIN_EXAMPLE ... #+END_EXAMPLE blocks.
`org-texinfo-src-block', which you modified in your patch, has nothing
to do with example blocks. It only handles exporting src blocks
(#+begin_src .. #+end_src).
Example blocks are exported using @example Texinfo markup.
See https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#g_t_0040example
Example blocks have no notion of language in Texinfo.
> Without this fix I can't export my `.org' files to `.texi' format ...
Please describe your problem in more details. What do you mean by "can't
export"? See https://orgmode.org/manual/Feedback.html#Feedback
--
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>
next prev parent reply other threads:[~2024-02-18 14:16 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 [this message]
[not found] ` <877cj0swz1.fsf@yandex.ru>
2024-02-24 10:05 ` Ihor Radchenko
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=87a5nxsrxu.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--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 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).