Github messages for voidlinux
 help / color / mirror / Atom feed
From: lukeflo <lukeflo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] pandoc package way out of date, should be V 3.2
Date: Fri, 24 May 2024 14:48:04 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50500@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]

New issue by lukeflo on void-packages repository

https://github.com/void-linux/void-packages/issues/50500

Description:
### Is this a new report?

Yes

### System Info

Void 6.6.31_1 x86_64 GenuineIntel uptodate rrFFF

### Package(s) Affected

pandoc-2.17.1.1_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Convert between document formats using the up-to-date functions of `pandoc`, such as the renewed AST in combination with Lua filters.

### Actual behaviour

Some of my Lua filters which use the new AST Figure elements are not working as expected, since the old `pandoc` version can't handle its syntax. Surely there are other drawbacks which I didn't encounter so far.

### Steps to reproduce

1. Install the `pandoc` package from void repo
2. For example, use my [GitLab Repo](https://gitlab.com/lukeflo/dailatex/-/tree/main/test-files?ref_type=heads) which contains my publication workflow and run `pandoc -t native cls-dai.md` after cloning. The resulting AST don't show a Figure block as it should.
3. Maybe try running the `makefile` and check the resulting `.tex` file, the changes which the filters should handle are not there.
4. This can be reproduced with running `pandoc -t native` on any `.md` file containing Pandoc's Markdown syntax for images/figures or exporting to LaTeX using some Lua filter acting on the [Figure element](https://pandoc.org/lua-filters.html#pandoc.figure). 

             reply	other threads:[~2024-05-24 12:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 12:48 lukeflo [this message]
2024-05-24 13:04 ` classabbyamp
2024-05-24 13:04 ` ahesford
2024-05-24 13:04 ` [ISSUE] [CLOSED] " classabbyamp
2024-05-24 13:04 ` ahesford
2024-05-24 13:23 ` classabbyamp
2024-05-24 13:58 ` lukeflo
2024-05-24 13:59 ` lukeflo

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50500@inbox.vuxu.org \
    --to=lukeflo@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).