joostkremers/parsebib

Issues

• invalid-read-syntax error

  #30 opened 2 years ago by lcm337
  3

• `point-at-eol` is obsolete

  #28 opened 2 years ago by bdarcus
  1

• Compilation failing on emacs 26.3

  #26 opened 2 years ago by kaushalmodi
  4

• Move `ebib-clean-TeX-markup` to parsebib

  #19 opened 3 years ago by bdarcus
  9

• New Release Tag?

  #24 opened 2 years ago by yewscion
  2

• Bug in `parsebib--convert-tex-italics`

  #22 opened 2 years ago by usaoc
  2

• Add support for org-bibtex

  #20 opened 3 years ago by bdarcus
  0

• String definitions are always returned braced, even when they are unbraced in the file

  #16 opened 3 years ago by Hugo-Heagren
  9

• Aligning key/type field names in json and bib/latex

  #13 opened 3 years ago by bdarcus
  2

• missing from melpa

  #15 opened 3 years ago by VladimirAlexiev
  2

• Excluding fields with parsebib-parse?

  #14 opened 3 years ago by bdarcus
  1

• direct parsing of files, csl-json feedback

  #12 opened 3 years ago by bdarcus
  62

• What can we expect if we round-trip a bibliography file?

  #9 opened 5 years ago by rpgoldman
  1

• Believe I have found an off-by-one error in parsebib--match-paren-forward

  #8 opened 7 years ago by rpgoldman
  9

• Please add a git tag for version 2.3

  #7 opened 7 years ago by spwhitton
  2

• support string replacements

  #5 opened 8 years ago by malb
  12

• Unexpected escape characters

  #4 opened 9 years ago by tmalsburg
  2

• M-x parsebib-find-next-item does not show up

  #3 opened 10 years ago by icymist
  11

• Normalize key and type fields?

  #1 opened 10 years ago by tmalsburg
  2

• parsebib uses cl-loop without requiring cl-macs

  #2 opened 10 years ago by swhahn
  1