Not yet. I found out (thanks to one of your earlier tests) that there are still library references that contain hardcoded filenames, pointing to libraries that are in my user directory. I'll try to ge

#resolved #mac

Something new to try: https://www.chordpro.org/dl/ChordPro-installer-0-977-10-1-macos-x64.dmg

#resolved #mac

Update: After enabling 'Allow Apps from Anywhere' wxchordpro binary runs as expected, regardless of how it was downloaded. So there must be something different between your system and mine. I hope som

#resolved #mac

On the system I currently use (Catalina 10.15, Intel X86_64) I created a new user. This user has no private perl stuff or whatsoever installed. I open the Finder, navigate to my Downloads folder, conn

#resolved #mac

Thanks for trying, I'll investigate. As an alternative, can you download https://www.squirrel.nl/pub/xfer/uploads/3Cu4TljasJ7t8-bLF2Byt1Vg.zip and unpack it? It contains a single binary version of wxc

#resolved #mac

There is an experimental MacOS 'kit' that you can download from https://www.chordpro.org/dl/ChordPro-0.977-macos.tar.gz . You can unpack the tar.gz in any convenient place. This will give a ChordPro-0

#resolved #mac

I've done so many years ago. Citrus (not Citrix) Perl came with a very nice packager system called Cava Packager. With Cava I could make identical install kits for Linux, Windows and Mac. But the prod

#resolved #mac

I also tried an alternative route: Citrus Perl. Citrus Perl is officially deceased but you can still find some kits on the net. I used https://osdn.net/projects/sfnet_citrusperl/downloads/Perl5.24.1/c

#resolved #mac

Welcome to ChordPro! Having multiple chord sets displayed in the same output seems a bit confusing to me. Do you have a sample of how that would look like? What ChordPro currently can do is produce mu

#needinfo

Thanks. I found the cause of the warnings and they will be gone in the next version. You may remove the setting pdf.diagrams.diagramscolumn. There is no such setting.

#resolved

I'm glad you went for the approach of the additional config file. Such a file is easy to create and maintain, and the behaviour is well defined. I have quite a few of these files in my ChordPro librar

#resolved

... which is implemented in the development version. You can target individual elements of an array valued config setting by using a numeric key. In your specific case this would become: --def pdf.for

#resolved

It is currently not possible to specify an array, or inidividual element of an array, using --define on the command line. The best alternative would be to create a one-liner json. e.g. tweak.json: { "

#resolved

Nice style! A good example of using the new ChordPro features. May I suggest to use font descriptions for all the lato fonts? It makes maintenance easier. To cancel a background colour you can set it

#informational

I've improved the document on using fonts and added examples. I hope this will clarify how to use fonts in ChordPro. Please give it a read and feedback. https://www.chordpro.org/beta/chordpro-fonts/

#informational

Pre-built versions for Windows will now be part of the releases.

#windows #resolved

The instrument and its characteristics are determined by the configuration file, and currently the configuration applies to the whole songbook, So it is either guitar, or ukulele. This may change in t

#resolved

I think in the font associations, you used "name" : "times" instead of "description" : "times". "name" refers to builtin fonts only. See also https://www.chordpro.org/chordpro/chordpro-fonts/ .

#informational #linux #resolved

Can you run chordpro with additional --debug and attach the generated PDF file?

#informational #linux #resolved

This style I have been using for quite a while to print songs that old eyes can read. The config is updated for ChordPro 0.977 and requires private fonts. Config september.json is the main config, sep

#informational