Open landroni opened 10 years ago
Never considered, no. Definitely not opposed to the idea. Do you think it needs a bit more testing before its inclusion?
The theme maintainer recommends the following: "You should check out what the scheme looks like in a few different language styles. For example, C++, Python, and XML. Using one statically typed, one dynamically typed, and one tag/structured markup language [..]"
If you take http://svn.emelfm2.net/trunk/src/e2_filelist.c , notice how much yellow bold there is in the document (using the latest base16 dark theme). I have little experience with this filetype, but as per my tastes I'd remove the bold here. What do you think?
If you take a ruby file: https://github.com/chriskempson/base16-builder/raw/master/base16 , then I notice similar bold issue with both yellow and blue. Again, should we remove these?
Python: https://github.com/landroni/pLyX/raw/master/scripts/pLyX.py . I'm actually not quite sure how it should look like. At the very least, on line 9 this looks weird: re.compile
. The first bit is bold yellow, and the 2nd bit is of a greyish hue. And shouldn't '''Send a help message to a yellow note in LyX.'''
be of color green?
XML: http://msdn.microsoft.com/en-us/library/ms762271(v=vs.85).aspx . Looks fine, but for the out-of-tune ?>
on the 1st line.
I can provide the fixes to the templates, but let me know what direction we should take.
I made a small tweak on my fork: https://github.com/landroni/base16-builder/commit/7e564056928874fa401dde46d62b592842e0e3b9
This ensures that for R files both 'asdf' and "asdf" strings have the same color (as in RStudio). I'll wait to see if there are other issues to fix before making a PR.
Also: https://github.com/landroni/base16-builder/commit/ca75cda5a9a65417caec8ac2dceb7f1d585fccbb
Avoids a formatting glitch in R files with keywords like parallel
or acme
. Again improves compatibility with RStudio.
I made yet another minor tweak: https://github.com/landroni/base16-builder/commit/4b25ea28face8c6f6b6f1957fbde76d5508d3c77
Now secondary keywords are properly highlighted.
I think I have sufficient (minor) fixes to make another PR upstream. Are you OK with the changes?
I went ahead with the PR: https://github.com/chriskempson/base16-builder/pull/155
Awesome! Thanks so much for pushing this forwards. Makes Geany so much better.
Thanks. :) I made yet another PR addressing most of the issues that I've pointed out above for *.py
, *.c
, and *.xml
files: https://github.com/chriskempson/base16-builder/pull/157. This time I modeled the tweaks based on the Default theme in Geany.
Once this PR is merged, I think we can regenerate the base16-geany and then propose that for inclusion in https://github.com/codebrainz/geany-themes.
Now this latest PR has been merged. Could you update the outputed themes in base16-geany, so that we could subsequently propose them for inclusion into geany-themes
?
https://github.com/RobLoach/base16-geany/commit/44d9e2e1bbcad5f396a8316b8c5fc9fceb61b194
Also added a Makefile to ease the building process. Thanks so much!
Cool! I'm leaving this open until we hear from the geany-themes
maintainer.
Have you considered proposing to include base16-geany into geany-themes ( https://github.com/codebrainz/geany-themes ), so that it could reach a wider audience? The inclusion process is described here: https://github.com/codebrainz/geany-themes/blob/master/ADDING-A-THEME.md .