-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
explain how to use the script in README.rst #9
Comments
Just for run this command , you will get everything
|
Is this normal? Do I need to change permissions? Perhaps I have something mis-configured?
|
Now I have run this with sudo, things worked... ✘ ⮀ ~/repos/fontpatcher ⮀ ⭠ develop ⮀ sudo python setup.py install
Password:
running install
Checking .pth file support in /Library/Python/2.7/site-packages/
/usr/bin/python -E -c pass
TEST PASSED: /Library/Python/2.7/site-packages/ appears to support .pth files
running bdist_egg
running egg_info
creating Powerline_font_patcher.egg-info
writing requirements to Powerline_font_patcher.egg-info/requires.txt
writing Powerline_font_patcher.egg-info/PKG-INFO
writing top-level names to Powerline_font_patcher.egg-info/top_level.txt
writing dependency_links to Powerline_font_patcher.egg-info/dependency_links.txt
writing manifest file 'Powerline_font_patcher.egg-info/SOURCES.txt'
reading manifest file 'Powerline_font_patcher.egg-info/SOURCES.txt'
writing manifest file 'Powerline_font_patcher.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.11-intel/egg
running install_lib
warning: install_lib: 'build/lib' does not exist -- no Python modules to install
creating build/bdist.macosx-10.11-intel
creating build/bdist.macosx-10.11-intel/egg
creating build/bdist.macosx-10.11-intel/egg/EGG-INFO
installing scripts to build/bdist.macosx-10.11-intel/egg/EGG-INFO/scripts
running install_scripts
running build_scripts
creating build/bdist.macosx-10.11-intel/egg/EGG-INFO/scripts
copying build/scripts-2.7/powerline-fontpatcher -> build/bdist.macosx-10.11-intel/egg/EGG-INFO/scripts
changing mode of build/bdist.macosx-10.11-intel/egg/EGG-INFO/scripts/powerline-fontpatcher to 755
copying Powerline_font_patcher.egg-info/PKG-INFO -> build/bdist.macosx-10.11-intel/egg/EGG-INFO
copying Powerline_font_patcher.egg-info/SOURCES.txt -> build/bdist.macosx-10.11-intel/egg/EGG-INFO
copying Powerline_font_patcher.egg-info/dependency_links.txt -> build/bdist.macosx-10.11-intel/egg/EGG-INFO
copying Powerline_font_patcher.egg-info/not-zip-safe -> build/bdist.macosx-10.11-intel/egg/EGG-INFO
copying Powerline_font_patcher.egg-info/requires.txt -> build/bdist.macosx-10.11-intel/egg/EGG-INFO
copying Powerline_font_patcher.egg-info/top_level.txt -> build/bdist.macosx-10.11-intel/egg/EGG-INFO
creating dist
creating 'dist/Powerline_font_patcher-beta-py2.7.egg' and adding 'build/bdist.macosx-10.11-intel/egg' to it
removing 'build/bdist.macosx-10.11-intel/egg' (and everything under it)
Processing Powerline_font_patcher-beta-py2.7.egg
creating /Library/Python/2.7/site-packages/Powerline_font_patcher-beta-py2.7.egg
Extracting Powerline_font_patcher-beta-py2.7.egg to /Library/Python/2.7/site-packages
Adding Powerline-font-patcher beta to easy-install.pth file
Installing powerline-fontpatcher script to /usr/local/bin
Installed /Library/Python/2.7/site-packages/Powerline_font_patcher-beta-py2.7.egg
Processing dependencies for Powerline-font-patcher==beta
Finished processing dependencies for Powerline-font-patcher==beta But when I try and run ~/repos/fontpatcher ⮀ ⭠ develop ⮀ python scripts/powerline-fontpatcher
The required FontForge modules could not be loaded.
You need FontForge with Python bindings for this script to work. But didn't I just install FontForge when I ran |
@F1LT3R I chased this for hours upon hours, until realizing that instead of running the script through python, like:
I could just run the script though fontforge itself:
|
@tstelzer When i do that, i end up in the Python command line. Is that normal? I still don't understand how to actually patch the font. I'm with @PhillipSz, there should be instructions in the README.rst. |
@cargath I just run into the same issue and it worked when specifying the script location fontforge scripts/powerline-fontpatcher somefont.otf |
just a few lines
The text was updated successfully, but these errors were encountered: