That's actually a really good question. I hadn't thought about that
before, but that's obviously an important thing to have as a
user-settable preference.
> Adding ~/.peppy/synmap doesn't help.
No, that's not something that peppy looks at. In the short term until
I figure out how to make that a preference, you can edit the file
peppy/editra/syntax/synextreg.py and add the ".pt" extension to line
#337, i.e.
'htm html shtm shtml xhtml pt' : LANG_HTML,
but there definitely needs to be a better way to do this. I'll have
to think about it.
Rob
I'm working on this now. My intention is to add a preference that
will contain extensions for each major mode. You can then modify the
extension list using the preferences dialog.
Rob
Try the latest 0.12 release. You can now edit filename extensions for
each major mode through the preferences.
Rob
Thanks!
> The problem now I faced is Syntax Highlighting is completely gone, all
> text shown as default black.
Hmmm, I haven't seen that problem yet.
> Below is what I did to troubleshoot.
> * remove whole folder ~/.peppy and restart app. still NO go.
I wonder if it's two conflicting peppy installs? I changed the syntax
highlighting stuff to be able to support the custom filename
extensions, so if there are old files in the dist-packages directory,
it might cause the problem. I'd suggest removing any of the old
peppy/ directories anywhere in your PYTHONPATH and try to reinstall.
> * when I run peppy from command line, I got some warning msg
> /usr/local/lib/python2.6/dist-packages/peppy/lib/pkg_resources.py:17:
> DeprecationWarning: the sets module is deprecated
> from sets import ImmutableSet
> /usr/local/lib/python2.6/dist-packages/peppy/lib/setuptools_utils.py:
> 33: UserWarning: Module site was already imported from /usr/lib/
> python2.6/site.pyc, but /usr/local/lib/python2.6/dist-packages/
> distribute-0.6.3-py2.6.egg is being added to sys.path
> import peppy.lib.pkg_resources as pkg_resources
I do see the first warning, but I don't see the second. I didn't
realize that distribute was a fork of setuptools; so I bet you're
right: that's probably causing the second warning. I've only used
setuptools.
I'll have to upgrade the setuptools I provide in the peppy/lib
directory to the latest version and see if that fixes the problem.
Rob