Hi all,
I've created a basic Scintilla lexer for the Markdown formatting syntax along with Geany syntax and tag support. It doesn't do everything; indented code blocks and embedded HTML aren't highlighted, but it's already very useful. Some extra highlighting features are added for the Pandoc implementation: strikeout, using '#.' as a default ordered list item marker, and delimited code blocks.
Patch against build 4026 with -p5 from Geany's top build directory.
This was built and tested on Linux.
Cheers, Jon
On Sun, 26 Jul 2009 00:33:08 -0700 Jon Strait jstrait@moonloop.net wrote:
I've created a basic Scintilla lexer for the Markdown formatting syntax along with Geany syntax and tag support. It doesn't do everything; indented code blocks and embedded HTML aren't highlighted, but it's already very useful. Some extra highlighting features are added for the Pandoc implementation: strikeout, using '#.' as a default ordered list item marker, and delimited code blocks.
Patch against build 4026 with -p5 from Geany's top build directory.
Thanks, applied in SVN.
But because we update Scintilla regularly we try to push modifications upstream; can you try to get the Scintilla changes into the standard Scintilla release please?
Regards, Nick
On Thu, 30 Jul 2009 12:29:54 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Patch against build 4026 with -p5 from Geany's top build directory.
Thanks, applied in SVN.
Just remembered, also we need a filetypes.markdown file so the user can easily customize the syntax highlighting, word chars, etc.
Regards, Nick
Nick Treleaven wrote:
On Thu, 30 Jul 2009 12:29:54 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Patch against build 4026 with -p5 from Geany's top build directory.
Thanks, applied in SVN.
Just remembered, also we need a filetypes.markdown file so the user can easily customize the syntax highlighting, word chars, etc.
Regards, Nick _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
# For complete documentation of this file, please see Geany's main documentation [styling] # foreground;background;bold;italic # default=0x000000;0xffffff;false;false # strong=0xff0000;0xffffff;false;false # emphasis=0xff0000;0xffffff;false;false # header1=0x0000bb;0xffffff;false;false # header2=0x0000bb;0xffffff;false;false # header3=0x0000bb;0xffffff;false;false # header4=0x0000bb;0xffffff;false;false # header5=0x0000bb;0xffffff;false;false # header6=0x0000bb;0xffffff;false;false # ulist_item=0x007f00;0xffffff;false;false # olist_item=0x007f00;0xffffff;false;false # blockquote=0xff0000;0xffffff;false;false # strikeout=0xaa00ff;0xffffff;false;false # hrule=0xff901e;0xffffff;false;false # link=0x0000ff;0xffffff;false;false # code=0x009f00;0xffffff;false;false # codebk=0x005f00;0xffffff;false;false
[settings] # default extension used when saving files extension=mdml
Nick Treleaven wrote:
On Sun, 26 Jul 2009 00:33:08 -0700 Jon Strait jstrait@moonloop.net wrote:
I've created a basic Scintilla lexer for the Markdown formatting syntax along with Geany syntax and tag support. It doesn't do everything; indented code blocks and embedded HTML aren't highlighted, but it's already very useful. Some extra highlighting features are added for the Pandoc implementation: strikeout, using '#.' as a default ordered list item marker, and delimited code blocks.
Patch against build 4026 with -p5 from Geany's top build directory.
Thanks, applied in SVN.
But because we update Scintilla regularly we try to push modifications upstream; can you try to get the Scintilla changes into the standard Scintilla release please?
Regards, Nick _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
I sent a patch for Scintilla to the project lead. Some extra warnings were thrown on my code when building for Scintilla, which were quite nice to have, and I don't remember seeing them when I built for Geany.
Cheers, Jon
On Thu, 20 Aug 2009 15:54:44 -0700 Jon Strait jstrait@moonloop.net wrote:
But because we update Scintilla regularly we try to push modifications upstream; can you try to get the Scintilla changes into the standard Scintilla release please?
I sent a patch for Scintilla to the project lead.
OK, thanks, did he say he'll commit it then?
Some extra warnings were thrown on my code when building for Scintilla, which were quite nice to have, and I don't remember seeing them when I built for Geany.
Not sure how to enable warnings by default for gcc/g++ in a portable way, but I'm no autotools guru.
Regards, Nick
P.S. Thanks also for the filetypes file, I'll commit that soon.
On Mon, 24 Aug 2009 16:46:07 +0100, Nick wrote:
On Thu, 20 Aug 2009 15:54:44 -0700 Jon Strait jstrait@moonloop.net wrote:
But because we update Scintilla regularly we try to push modifications upstream; can you try to get the Scintilla changes into the standard Scintilla release please?
I sent a patch for Scintilla to the project lead.
OK, thanks, did he say he'll commit it then?
Some extra warnings were thrown on my code when building for Scintilla, which were quite nice to have, and I don't remember seeing them when I built for Geany.
Not sure how to enable warnings by default for gcc/g++ in a portable way, but I'm no autotools guru.
It's not really about autotools but more about which compiler to use. Not everyone is using gcc/g++ and other compilers don't necessarily understand the same command line options as gcc/g++ (besides the pseudo-standard options like -c, -o and -g). IIRC Scintilla's Makefile is assuming g++ is available which we don't do in Geany. Using appropriate compiler flags to trigger warnings is in the responsibility of the developer, I think. That is, if you personally want more warnings, define them using the global CFLAGS environment variable for example. At least this is what I do and I'm happy with this concept and it doesn't break the build for users with other compilers.
Last but not least with regards to compiling Scintilla in Geany, we just *use* Scintilla here, so we don't care so much about warnings. We don't actively develop Scintilla except for a few patches here and there. In contrary, for the Geany code itself we (i.e. Nick and me) use a good set of specific gcc options to trigger various warnings.
Regards, Enrico
Nick Treleaven wrote:
On Thu, 20 Aug 2009 15:54:44 -0700 Jon Strait jstrait@moonloop.net wrote:
But because we update Scintilla regularly we try to push modifications upstream; can you try to get the Scintilla changes into the standard Scintilla release please?
I sent a patch for Scintilla to the project lead.
OK, thanks, did he say he'll commit it then?
Yes. I'm having to make several small changes regarding the warnings and the liscesing which you will see on a future update.
Some extra warnings were thrown on my code when building for Scintilla, which were quite nice to have, and I don't remember seeing them when I built for Geany.
Not sure how to enable warnings by default for gcc/g++ in a portable way, but I'm no autotools guru.
Regards, Nick
P.S. Thanks also for the filetypes file, I'll commit that soon. _______________________________________________ Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Adding these warning options to the AM_CXXFLAGS line for the Makefile.am in the scintilla/ directory, should give the same mix of warnings that the Scintilla build will:
-Wall -Wno-missing-braces -Wno-char-subscripts -pedantic
I'm thinking it might make sense to have these warnings thrown for the scintilla/ make, if most new code created in there is destined for Scintilla.
Cheers, Jon
On Mon, 24 Aug 2009 14:15:59 -0700, Jon wrote:
Hi,
Adding these warning options to the AM_CXXFLAGS line for the Makefile.am in the scintilla/ directory, should give the same mix of warnings that the Scintilla build will:
-Wall -Wno-missing-braces -Wno-char-subscripts -pedantic
I'm thinking it might make sense to have these warnings thrown for the
Please don't. See my other mail in this for the reason.
Regards, Enrico
On Mon, 24 Aug 2009 23:38:37 +0200 Enrico Tröger enrico.troeger@uvena.de wrote:
Adding these warning options to the AM_CXXFLAGS line for the Makefile.am in the scintilla/ directory, should give the same mix of warnings that the Scintilla build will:
-Wall -Wno-missing-braces -Wno-char-subscripts -pedantic
I'm thinking it might make sense to have these warnings thrown for the
Please don't. See my other mail in this for the reason.
Yes, that's why I said I didn't know how to do it in a *portable* way.
Regards, Nick
On Mon, 24 Aug 2009 16:46:07 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
P.S. Thanks also for the filetypes file, I'll commit that soon.
Now committed, thanks.
Regards, Nick