siefkenj/unified-latex

Issues

• Parsing takes absurdly long time for some simple documents

  #115 opened 22 days ago by squ1dd13
  3

• Index tokens ('^', '_') are parsed as string

  #114 opened 2 months ago by slava-arapov
  2

• LaTex format to invalid style

  #107 opened 2 months ago by tc1989tc
  11

• cli

  #85 opened 3 months ago by MarcelSchaible
  1

• Cannot import any types in unified-latex-types with `"module": "Node16"`

  #72 opened 9 months ago by pddg
  2

• Parse setting macros like `lineskip`

  #111 opened 3 months ago by rrrnld
  1

• Seemingly accidental publish of version 2.4.2 makes npm miss out on 1.6.0+

  #96 opened 6 months ago by FelixZY
  5

• minted and lstlisting environment should be parsed as `verbatim`

  #77 opened 9 months ago by pddg
  6

• Method to leave `math` and `inlineMath` sections as is

  #95 opened 6 months ago by dmca-glasgow
  7

• \path macro should be parsed like \verb

  #94 opened 7 months ago by retorquere
  3

• `match.macro` should accept `any`

  #89 opened 8 months ago by siefkenj
  1

• Comments after empty string do not have position

  #86 opened 8 months ago by pddg
  4

• Problems with \^{} escape

  #28 opened 9 months ago by udovin
  5

• building a bibtex plugin

  #65 opened 9 months ago by retorquere
  67

• erroneous `openMark`/`closeMark` on argument parse

  #76 opened 9 months ago by retorquere
  7

• unified-latex and tree-sitter-latex

  #74 opened 9 months ago by batchor
  1

• Parbreak between item environment has no position

  #73 opened 9 months ago by pddg
  2

• A bug of attachMacroArgsInArray

  #71 opened 9 months ago by theseanl
  0

• Ignore macros with problematic argument specifications in `listNewcommands`

  #64 opened 10 months ago by theseanl
  1

• Embellishment argspec should not return a group

  #48 opened a year ago by siefkenj
  2

• Should force newline after \\

  #13 opened a year ago by siefkenj
  0

• \phantom \hphantom in math mode

  #53 opened a year ago by siefkenj
  0

• Space after argument-less macro should be absorbed

  #56 opened a year ago by Evan-Zhao
  2

• Parser takes an excessive amount of time for particular file

  #47 opened a year ago by dwillhalm
  2

• Allow non-character brace tokens in xparse argument specification

  #46 opened a year ago by theseanl
  2

• [enhancement] Allow for per-environment macro specifications

  #43 opened a year ago by siefkenj
  0

• \\ macro should be parsed differently in some math environments

  #40 opened a year ago by theseanl
  8

• Need help setting up local development environment

  #38 opened a year ago by rrrnld
  2

• `$` parsing in verbatim

  #35 opened a year ago by James-Yu
  1

• Possibility of downgrading `unified` dependency to 9.2.2

  #32 opened a year ago by James-Yu
  2

• [html] Issues with \begin{tabular}

  #36 opened a year ago by udovin
  3

• type guard is not working when visitinfo is provided in test function

  #30 opened 2 years ago by mooncaker816
  5

• [unified-latex-prettier] Maybe introduce more break point?

  #25 opened 2 years ago by Enter-tainer
  2

• So cool!

  #21 opened 2 years ago by rowanc1
  3

• Macro default argument support

  #24 opened 2 years ago by theseanl
  1

• npm package @unified-latex/unified-latex-util-match contains broken .d.ts

  #23 opened 2 years ago by theseanl
  2

• Question: How to add support of new macros

  #17 opened 2 years ago by udovin
  2

• Error [ERR_REQUIRE_ESM]: Must use import to load ES Module

  #15 opened 2 years ago by udovin
  3

• Multiple newlines processed as multiple whitspace in math mode

  #14 opened 2 years ago by siefkenj
  0

• Potential parsing issue

  #7 opened 2 years ago by kylebutts
  3

• Thank you!

  #9 opened 2 years ago by tefkah
  1

• Attempt to parse math

  #8 opened 2 years ago by mcendu
  1

• failed to build locally

  #3 opened 2 years ago by yunmc
  14

• missing index.cjs files in the dist packages

  #4 opened 2 years ago by williamstein
  4