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

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

Where would I find those logs?

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

So you think I have 2 separate wxperl environments installed now?

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

Sorry, I should have mentioned that I wanted to use the GUI. But, again, the wxPerl part installed way more quickly than the sudo cpan install chordpro. I don't understand Linux well enough to know

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

Thanks! Maybe I got the errors because I hadn't turned off chord diagrams (-G), but I think they persisted--specifically referencing all my slash chords. I'll take a look at the configuration file

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

I have an old Win32 Linux (Peppermint 10 distro) machine (Asus Eee PC) that I sometimes use to write and edit ChordPro files. I wanted to use ChordPro software to preview my files on that machine. I

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

Is this still the case? Otherwise add a #resolved tag,

No need. This is already implemented in the development branch.

Nice work. Explains the custom and expanded set of standard sections in a straightforward manner. Do we need a feature request ticket to be added to reference implementation to handle the new short

Please take a look at the docs in the wiki, https://github.com/ChordPro/chordpro/wiki/ChordPro-Directives#environment-directives .

Sean, I forgot to mention: you need to run “sudo cpan”.

Great news about Fedora! I have never made a package for Homebrew before, but I can give it a go (unless someone else has experience in this area). Using cpan for Mac installation is pretty painful,

Interesting to read this! It make the value of custom sections clear. At the very least the documentation should include a description of custom sections. As for short forms, even though they are

Consistency is always good, at least from my point of view ;)