- Add support for table-style listings (PR #44 - thanks to @cochaviz)
- Fix inconsistent behavior for relative paths when bib file is not enclosed in square brackets (issue #49)
- Citations entered from bibjson will have an editor and a clickable url/DOI on hover (PR #43 - thanks to @adunning)
- Try to load bib files similar to v0.9.3 because the newer versions are not working for some users (issue #41)
- Try to fix citation autocompletion not showing up if a workspace is not loaded
- The bibliography paths in the YAML header no longer need to be enclosed in square brackets (issue #32)
- The
DefaultBib
configuration now supports multi-root workspaces (issue #31) - Add initial support for CSL JSON files (issue #34)
- The fields specified by the
PandocCiter.CitationFormat
configuration will be used to filter suggestions (issue #33) - Add a new config
PandocCiter.DefaultBibs
which accepts a list of files (issue #18)
- Added support for citations in quarto[https://marketplace.visualstudio.com/items?itemName=quarto.quarto] documents
- Hovering and go-to support ( #29 - thanks to @Dominic-DallOsto )
- Hovering over a citation will now show relevant information (e.g. author & title)
- Ctrl+clicking a citation will now open the bibtex file and go to the line where the entry was defined
- Added support for pandoc-crossref crossreferences ( #26 - thanks to @yarray )
- Use
documentation
instead ofdetail
property for suggestions- This should fix incorrect newlines in intellisense (issue #21)
- Add support for
Pweave Markdown
files
- Remove support for
${workspaceFolder}
in bib path - If the path in
PandocCiter.DefaultBib
is relative, then it will be assumed that the path is relative to the workspaceFolder
- Support
${workspaceFolder}
in bib path (#13)
- Switch to latex-utensils on the backend to support custom BibEntries (#12)
- Fix UseDefaultBib with relative path ( #11 - @smartens )
- Added a config option which can disable the 'forgetting' feature added in 0.4.0
- For example, if a project has multiple markdown files where the bibliography should be shared but only one file has a YAML header, then setting
PandocCiter.ForgetUnusedBib: false
will allow the citation suggestions to appear in all of the markdown files.
- For example, if a project has multiple markdown files where the bibliography should be shared but only one file has a YAML header, then setting
- Added a language check when the text editor is changed.
- Otherwise, the extension forgets all of the citations whenever a non-markdown file was opened which is unnecessary.
- Fixed an issue where quoted paths were not recognized correctly
- Extension should now forget suggestions from bib files which are removed from the
bibliography
field
- Update to lighter dependencies
- Minor update to dependancies becuase of upstream security warnings
- The completion provider terminates itself if it isn't triggered by an
@
.- The completion provider was being executed for any typed character because intellisense is aggressive by default. Although not a big deal, it does mean that unnecessary computations are done for each keystroke. This update attempts to avoid the extra computation by terminating the function early if an
@
is not detected.- There might be a good reason for intellisense's aggressiveness that I'm unaware of. Remains to be seen if this update breaks the completions for any users.
- The completion provider was being executed for any typed character because intellisense is aggressive by default. Although not a big deal, it does mean that unnecessary computations are done for each keystroke. This update attempts to avoid the extra computation by terminating the function early if an
- Feature: Check if any duplicate keys exist when parsing a bib file
- For debugging: Add log event when providing suggestions
- Fixes:
- When
PandocCiter.ViewType
was set to"browser"
, the inserted citation would be placed in a selected state. This was a problem because typing any character would erase the inserted citation, e.g.@insertedKey
would become@
if the space bar is pressed. Updated version should now deselect the citation as soon as it is done inserting it. - The suggestions would pop-up as long as any
@key
exists on the line. This is because the regex searched for the suggestion trigger along the entire line, so any instance of a citation would lead to citation suggested throughout the line. Updated version should now only search for the citation trigger in the most recent word before the cursor instead of the entire line.
- When
- Updated vscode module to avoid potential security issue with the event-stream package.
- [0.3.0] Add configuration
PandocCiter.DefaultBib
andPandocCiter.UseDefaultBib
PandocCiter.DefaultBib
should be an absolute path to a bib file. This file will always be loaded in any markdown document without requiring a YAML entry.
- [0.2.0] Add support for
-@key
syntax
- Bib files will be searched on file save
- Previously, the text document had to be closed/re-opened whenever
bibliography: [./path/to/refs]
was updated
- Previously, the text document had to be closed/re-opened whenever
- Fix citations not being highlighted when inside square brackets in vscode 1.28
- Change
pandoc.citation
scope tostring.other.link.description.markdown.citation
- Citations should now be automatically hi-lighted by most (all?) themes
- Add support for R-Markdown documents
- Remove disallowed punctuation from citation scope
- Recognize citation scope when a reference is at the beginning of a new line
- Consolidate the two citation scopes into a single scope
- Add "pandoc.citation" scope for references: #1
- Enable
awaitWriteFinish
on file watcher. This might introduce a short delay before a modified .bib file is parsed, but it prevents .bib files from getting partially parsed when they are still being written to disk. - Adapted fix from: James-Yu/LaTeX-Workshop#817
- Should improve bib parsing speed
- Use newer versions of dependencies
- Output channel for the extension log should no longer be created if
PandocCiter.ShowLog
config is false
- Extension log can now be viewed in the output panel
- Fixed relative path in RootFile being incorrectly resolved relative to the Workplace Directory instead of the RootFile's directory
- Allow RootFile to either be a relative or absolute path
- Added configuration for ViewType and RootFile
- Initial release