In a response to issue #13, user rustianimal wrote the following comment: I took the liberty to use rustianimal's comment as a starting point for a new discussion. Please participate. Points to consid

#informational #needinfo

There are several ways to approach this. This is already possible: {define A⁷ base-fret 1 frets 0 2 2 2 3 0 } This is [A⁷]super! It is just tedious and clumsy... So we're going t

#informational #needinfo

Sure. See https://github.com/ChordPro/chordpro/wiki/Using-ChordPro#transcode. If the input is not in common notation, add --config notes:latin or something appropriate.

#resolved

You can add --output=newsong.cho, see https://www.chordpro.org/chordpro/Using-ChordPro.html#general-command-line-options_output

#resolved

It seems to miss essential tools like tar, gzip. Are these installed?

#resolved #mac

/sw/bin/tar is the program that unpacks the downloaded sources. It is a system program that should be available on your system. Are there any programs in your /sw/ and /sw/bin/ directories? Someone me

#resolved #mac

Well, it may be worth the experiment. Better still, try to run from git. See https://github.com/ChordPro/chordpro/wiki/ChordPro-run-from-Git to get started. You will probably miss some dependencies, l

#resolved #mac

Please continue here. Other Mac users can benefit as well.

#resolved #mac

The main reason is that there is no start_of_verse. ChordPro allows start_of and end_of anything. chorus, tab and grid have a predefined meaning, but you can use anything else. start_of_verse, start_o

#ChordPro #resolved

Yes, you are right. This is confusing. I assume I added start_of_verse and then decided to go for a more generic approach. However, the start_of_verse remained in the docs. The idea behind sections wa

#ChordPro #resolved

If you have the MuseJazz font (available on the internet), why not try the musejazz config? chordpro --config musejazz swinglow.cho (dev branch from git only, you may need to adapt the fonts section a

#informational

Hi Kevin, About the installation: there are several installation instructions on the ChordPro site. Which did you use? And what version of ChordPro did you install? About slash chords: ChordPro unders

#windows #needinfo

To install ChordPro you do not need wxperl. This is only required for the GUI (wxChordPro). Are you using it? ChordPro itself has just a few dependencies. I have no idea why it took so long. I assume

#windows #needinfo

Then I assume it didn't find the wxperl stuff (can't tell you why) and it downloaded and installed a complete wxWidgets environment. Yes, that takes a long time... ChordPro is currently available in t

#windows #needinfo

It's a guess. I need to see the logfiles to be sure. But as long as it works...

#windows #needinfo

They were written to the terminal during the build. Unless you captured them they are gone.

#windows #needinfo

On second thought, the chordpro kit does not have a dependency on wxperl so it won't pull in the Wx environment.

#windows #needinfo

It is correct that installing wxperl via the package manager is quick. I have no idea why install chordpro took such a long time. You could take a look at the .cpan/build directory of user root to see

#windows #needinfo

Currently not, but I could make one. However, installing ChordPro on Linux is usually trivial. Is there a specific reason you would want a prebuilt binary?

#linux #resolved

It should be (relatively) straightforward: Install PAR::Packer if necessary Copy (from github) pp/common/PDF_API2_Bundle.pm (this file was accidentally left out of the kit) Cd to the pp/linux director

#linux #resolved