ryanoasis / nerd-fonts

Iconic font aggregator, collection, & patcher. 3,600+ icons, 50+ patched fonts: Hack, Source Code Pro, more. Glyph collections: Font Awesome, Material Design Icons, Octicons, & more
https://NerdFonts.com
Other
52.6k stars 3.59k forks source link

invalid escape sequence warnings when running font-patcher script #1643

Closed mearleycf closed 1 month ago

mearleycf commented 1 month ago

Experienced behavior: I was performing a dry run of font-patcher to make sure it wouldn't return any errors, etc. When I run the following command, I get the following output:

❯ fontforge -script ~/Downloads/Nerd\ Fonts\ Patcher/font-patcher ~/patched_fonts/mononoki-nerd-fontv2/mononoki-Regular.otf --complete --dry --outputdir ~/patched_fonts/mononoki-nerd-font-v2/1.0.0/
Copyright (c) 2000-2023. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
 with many parts BSD <http://fontforge.org/license.html>. Please read LICENSE.
 Version: 20230101
 Based on sources from 2023-01-01 05:27 UTC-D.
/Users/mikeearley/Downloads/Nerd Fonts Patcher/font-patcher:432: SyntaxWarning: invalid escape sequence '\='
  message = "   Generated {} fonts\n   \===> '{}'".format(len(sourceFonts), outfile)
/Users/mikeearley/Downloads/Nerd Fonts Patcher/font-patcher:448: SyntaxWarning: invalid escape sequence '\='
  message = "   {}\n   \===> '{}'".format(sourceFont.fullname, outfile)
/Users/mikeearley/Downloads/Nerd Fonts Patcher/font-patcher:2028: SyntaxWarning: invalid escape sequence '\.'
  if re.match("\.ttc$", args.extension, re.IGNORECASE):
Nerd Fonts Patcher v3.2.1 (4.13.1) (ff 20230101)
INFO: Setting Panose 'Family Kind' to 'Latin Text and Display' (was 'Any')
INFO: Setting Panose 'Proportion' to 'Monospaced' (was 'Any')
Done with Patch Sets, generating font...

Expected behavior: As a test, I corrected those 3 issues, and they didn't print when I ran the --dry run again. Maybe the font-patcher script needs some minor updates?

Example symbols: n/a

🔧 Your Setup

Finii commented 1 month ago

Thanks for being observative and taking the time to report the issue :green_heart:

This has already been fixed via cb0c9ed1e7b70 in in-parens-version 4.14.3 (you use 4.13.1).

D3vil0p3r commented 1 month ago

Thanks for being observative and taking the time to report the issue 💚

This has already been fixed via cb0c9ed in in-parens-version 4.14.3 (you use 4.13.1).

I am getting the same issue when I use the latest stable 3.2.1 release. If the issue has been fixed in the git repo, could you please release a new stable release with this fix?