|
1 | 1 | Python Improved v1.2.1 |
2 | 2 | ====================== |
3 | 3 |
|
4 | | -A couple changes for this new release: first, while AAAPackageDev's facility for |
5 | | -translating XML-based `.tmLanguage` files to and from YAML is great for |
6 | | -developing language definitions, it has a small bug where spaces can be inserted |
7 | | -into extra-long single-line regexes. After this was kindly pointed out by |
8 | | -@inancsevinc, I have instituted an extra step after each build to remove these |
9 | | -spaces, which had been interfering with matching some scopes. Second, after |
10 | | -experimenting with bringing the contents of the base Python package's `Regular |
11 | | -Expressions (Python).tmLanguage` file into Python Improved, I have decided to |
12 | | -remove it. It was causing some significant problems highlighting regexes in |
13 | | -Python code, and rather than wade through it line-by-line I found it works just |
14 | | -as well as if I just use a single `include` statement. Finally, I updated the |
15 | | -license to CC-BY-SA 4.0, an upgrade from 3.0. I think it's a little more |
16 | | -clearly written, but still says essentially the same thing: feel free to use my |
17 | | -work as the basis of your own, but please acknowledge me in your work, and |
18 | | -license it with the same or a similar license. |
| 4 | +A couple changes for this new release: first, while AAAPackageDev's facility for |
| 5 | +translating XML-based `.tmLanguage` files to and from YAML is great for |
| 6 | +developing language definitions, it has a small bug where spaces can be inserted |
| 7 | +into extra-long single-line regexes. After this was kindly pointed out by |
| 8 | +@inancsevinc, I have instituted an extra step after each build to remove these |
| 9 | +spaces, which had been interfering with matching some scopes. Second, after |
| 10 | +experimenting with bringing the contents of the base Python package's `Regular |
| 11 | +Expressions (Python).tmLanguage` file into Python Improved, I have decided to |
| 12 | +remove it. It was causing some significant problems highlighting regexes in |
| 13 | +Python code, and rather than wade through it line-by-line I found it works just |
| 14 | +as well as if I just use a single `include` statement. Third, I added the |
| 15 | +ability to highlight `XXX`, `BUG`, `FIXME`, and `TODO` in comments, as well as |
| 16 | +highlight the entire line containing that word. You can find the latest scopes |
| 17 | +in the README. Finally, I updated the license to CC-BY-SA 4.0, an upgrade from |
| 18 | +3.0. I think it's a little more clearly written, but still says essentially the |
| 19 | +same thing: feel free to use my work as the basis of your own, but please |
| 20 | +acknowledge me in your work, and license it with the same or a similar license. |
19 | 21 |
|
20 | | -To take full advantage of the extra scopes included in Python Improved, check out |
| 22 | +To take full advantage of the extra scopes included in Python Improved, check out |
21 | 23 | the Neon Color Scheme at https://sublime.wbond.net/packages/Neon%20Color%20Scheme |
22 | 24 | If you'd rather modify your own color scheme, a list of scopes is included in |
23 | 25 | the README.md in the `Packages/Python Improved` directory. You can also find |
24 | 26 | them on GitHub at https://github.com/MattDMo/PythonImproved#readme |
25 | 27 |
|
26 | 28 | If you have any questions, comments, concerns, bugs, or patches, please open an |
27 | 29 | issue or pull request on GitHub and I'll do what I can to help out. You can also |
28 | | -email me directly at < [email protected]> or find me on Twitter at @MattDMo. |
29 | | -This is definitely a work in progress, so if you'd like to contribute I'd love |
| 30 | +email me directly at < [email protected]> or find me on Twitter at @MattDMo. |
| 31 | +This is definitely a work in progress, so if you'd like to contribute I'd love |
30 | 32 | to hear from you! |
0 commit comments