You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was poking around to consider making a Chordpro plugin for Obsidian, and I realized that with something like the following code as a preprocessor (and converting {this} to [this]), you could render 99% of all real world Chordpro files that just have chords and a few {chorus} notes. Or a similar bit of TS code; this is not a terribly complex text transformation.
I haven't dug into the chordlyrics code, but it could be as simple as ```chordlyrics rendering as it does currently, and ```chordpro could apply a preprocessor, followed by treating it as input. Admittedly a bit of a hack, but a very easy one to catch most usage cases for a popular format.
Is there any interest in this, or would it be considered outside the scope of this project?
The text was updated successfully, but these errors were encountered:
I was poking around to consider making a Chordpro plugin for Obsidian, and I realized that with something like the following code as a preprocessor (and converting {this} to [this]), you could render 99% of all real world Chordpro files that just have chords and a few {chorus} notes. Or a similar bit of TS code; this is not a terribly complex text transformation.
https://github.com/jperkin/chordpro.js/
I haven't dug into the chordlyrics code, but it could be as simple as
```chordlyrics
rendering as it does currently, and```chordpro
could apply a preprocessor, followed by treating it as input. Admittedly a bit of a hack, but a very easy one to catch most usage cases for a popular format.Is there any interest in this, or would it be considered outside the scope of this project?
The text was updated successfully, but these errors were encountered: