Thanks for the info. I am afraid there is not much that can be done automatically. Wrapping the title would overflow into the subtitle and eventually affect almost every aspect of the layout. Some rem

#ChordPro

Can you run a sample song with --debug and attach the resultant PDF document.

#ChordPro

The dmg was built on 10.15 but I wouldn't know why this would require 10.15 or later... Any Mac gurus around? Building the dmg should be possible for any MacOS user, ask me for details.

#resolved #mac

AFAICS there are rebuilt packages for Mint 19.3. libwx-perl This will probably pull in other dependencies.

#needinfo

What Linux distro are you running? Practically all of them have perl-Wx as a prebuilt package. For Windows and MacOS there are other solutions.

#needinfo

This would definitely be nice to have. In fact, this is one of the reasons I created the ChordPro GUI -- to be able to extend it with some kind of document management. Would you consider to write such

#needinfo

As for running on MacOS, I overlooked that you meant the command line version. For this, you do not need a binary install kit. Have you tried https://www.chordpro.org/beta/chordpro-install-on-macos/ a

The idea behind labels is to mark sections individually, e.g. "Verse 1", "Bridge", "Repeat Chorus" and so on. Providing a default, generic label is possible, but I rather not do this until there is a

wrote: Theoretically, yes. Practically, use this one: https://www.chordpro.org/dl/dl/ChordPro-installer-0-977-28-1-macos-x64.dmg I still have to work out the exact procedure to create it. -- Johan

I've restored the "printing tags as comments" behaviour. You can enable it with pdf.labels.comment. Set it to the desired comment type, i.e. comment, comment_italic or comment_box. For example: "pdf"

Thanks, fixed.

#resolved

Yes, I see :) . The meaning should be reversed. If metadata.strict is true (default), {meta: XXX} only accepts the keys defined with metadata.keys. If metadata.strict is false, {meta: XXX} accepts any

#ChordPro

I've modified A2Crd.pm so that a2crd now does full config processing, just like chordpro. . I've added tab expansion (different algorithm, simpler functionality). Tab stop width is configurable in the

#informational

I definitely will, Jeff. Thanks for contributing. I had already set up a test set for a2crd and I'll see if I can incorporate your t/500-a2crd.t into it. I was considering two test sets, one set (the

#informational

For the toc issue, would it help if you could pass a list of files to chordpro (--filelist option) and have non-existing files silently skipped while they still make up an entry in the toc? So if you

#needinfo

I agree fully. As long as the OS packages are up to date it is better/easier to use these instead of installing yourself. But for a novice user it may be easier to just type a single 'cpan chordpro' c

#needinfo

I think it is a nice and interesting piece of work. It required some tweaking to get it going, but then it does a great job. A couple of remarks: All ChordPro dependencies should be installed automati

#needinfo

You only need to start adding settings to config files when you want to change ChordPro behaviour and results. So first remove your local ~/.config/chordpro/chordpro.json and try again. To create a de

#mac #needinfo

I've enhanced the documentation. Please feedback. https://www.chordpro.org/beta/directives-define/

#ChordPro

Interesting. Do you have pointers to charts like this, and/or tools that produce such charts?

#ChordPro