Code::Blocks - User contributions [en]

SpellChecker plugin

2012-01-19T21:55:45Z

Danselmi:

[[Category:Code::Blocks Contrib Plugins]]

{{Infobox_Plugin|
name = SpellChecker |
logo = [[File:SpellChecker.png]] |
developer = Daniel Anselmi |
maintainer = Daniel Anselmi |
version = 0.1
}}

=Introduction=
A plugin to check the spelling of strings and comments. The spelling gets checked during typing. Additionally a thesaurus is provided. Both may be accessed on-demand by selecting the word in question, then choosing either ''Spelling...'' or ''Thesaurus...'' from the ''Edit'' menu (the operation can be bound to a hot-key via the [[Keyboard Shortcuts plugin]]). The context menu (right click the word) provides spelling suggestions.

=Configuration=
Configuration is in the menu Settings > Editor. The spell check option are about half way down the list on the left.
[[File:ConfigureSpellChecker.png]]

The meaning of the controls are:

'''Enable online spell checker'''
:Enable or disable the spell checker.

'''Language'''
:The language used for spell checking and the thesaurus is selected by choosing a dictionary. This can also be changed in the status bar.

'''Path settings, Dictionaries'''
:The plugin is looking in this path for the dictionary files.

'''Path settings, Thesauri'''
:The plugin is looking in this path for the files needed by the thesaurus.

'''Path settings, Bitmaps'''
:(Optional) The plugin is looking in this path for the flags to show in the status bar.

'''Note''': You can use Macros in the above three path settings, such as
<code>$(CODEBLOCKS)/share/codeblocks/SpellChecker</code>.
See [[Variable expansion]] for more details. This is quite convenient if you use portable C::B.

==Dictionaries==
SpellChecker uses a library called [http://hunspell.sourceforge.net/ hunspell]. Hunspell is the spell checker of OpenOffice.org, Mozilla Firefox and other projects. Dictionaries available for those applications are compatible with this plugin.

Open Office provides a collection of dictionaries for several languages and dialects to [http://wiki.services.openoffice.org/wiki/Dictionaries download]. The OOo 3.x extensions (*.oxt) are compressed archives which can be opened with your favourite archiver (for example [http://www.7-zip.org/ 7-Zip] or File Roller).
Copy the '''.aff''' file and the '''.dic''' file to the directory configured in 'Path settings, Dictionaries' (see above).

If you're running Linux you've probably already got compatible dictionaries installed. Look in '''/usr/share/hunspell''' or my choice is '''/usr/share/myspell/dicts'''. The reason I like the myspell files is they already include thesaurus files which are named correctly to work with the thesaurus, and everything is all in one location. Don't copy these files. Just point the spell checker to where the files are already located.

I understand on Windows, Firefox and Thunderbird also install compatible dictionary files. These can be found in...
'''C:\Program Files\Mozilla Firefox\dictionaries''' or '''C:\Program Files\Mozilla Thunderbird\dictionaries'''

The Google Chrome browser also installs dictionaries, but they are '''.bdic''' format and the Code::Blocks spell checker plugin will not work with them.

==Thesaurus files==
The files for the thesaurus are also available from OOo, like the dictionaries. Copy the thesaurus files ('''th_*.dat''' and '''th_*.idx''') to the directory configured in
'Path settings, Thesauri' (see above) and rename them to match the name of the dictionary but prepend "th_" and let the extension as is.

Example: If the dictionary files (for one language) are "en_GB.aff" and "en_GB.dic" the files used for the thesaurus are "th_en_GB.idx" and "th_en_GB.dat".

On my Linux system I found thesaurus files already installed in '''/usr/share/myspell/dicts''' and '''/usr/share/mythes'''. Again, don't move the files. Set the spell checker to use the files from their current location.

==Bitmaps (flags)==
The bitmap of the actually selected language is shown in the status bar. If no bitmap is found, the name of the language is shown. The bitmap must be a PNG image. Choose a flag from the [http://www.famfamfam.com/lab/icons/flags '''famfamfam_flag_icons'''] and copy it to the directory configured in 'Path settings, Bitmaps' (see above) and rename it to match the name of the dictionary but let the extension png.

Example: If the dictionary files (for one language) are "en_GB.aff" and "en_GB.dic" the the bitmap is named "en_GB.png" .

==Styles to check==
Only text with specific styles gets checked (for example only comments and strings). Styles are automatically set by Scintilla (CodeBlocks editing component).

The file '''OnlineSpellChecking.xml''' contains a list with indices of the styles to check. The indices differ for different programming-languages so the file contains a list for every programming-language. To add styles, look for the name of the programming-language and the indices in the corresponding [https://wiki.next.codeblocks.org/index.php?title=Creating_a_custom_lexer_for_Code::Blocks_editor#Lexers '''lexer_XY.xml'''] file and add this information to the file OnlineSpellChecking.xml.

For example, to check the spelling in bash shell files (<tt>*.sh</tt>) files, add the line:
<'''Language''' <span style="color:MidnightBlue">name</span>=<span style="color:Red">"Bash"</span> <span style="color:MidnightBlue">index</span>=<span style="color:Red">"2,5,6"</span> '''/'''>

SpellChecker plugin

2010-10-14T00:07:28Z

Danselmi: Created page with '=Introduction= A plugin to check the spelling of strings and comments. The spelling gets checked during typing. Additionally a thesaurus is provided. =Configuration= [[File:Co…'

=Introduction=
A plugin to check the spelling of strings and comments. The spelling gets checked during typing. Additionally a thesaurus is provided.

=Configuration=
[[File:ConfigureSpellChecker.png]]

The meaning of the controls are:

'''Enable online spell checker'''
:Enable or disable the spell checker.

'''Language'''
:The language used for spell checking and the thesaurus is selected by choosing a dictionary. This can also be changed in the status bar.

'''Path settings, Dictionaries'''
:The plugin is looking in this path for the dictionary files.

'''Path settings, Thesauri'''
:The plugin is looking in this path for the files needed by the thesaurus.

'''Path settings, Bitmaps'''
:(Optional) The plugin is looking in this path for the flags to show in the status bar.

==Dictionaries==
SpellChecker uses a library called [http://hunspell.sourceforge.net/ hunspell]. Hunspell is the spell checker of OpenOffice.org, Mozilla Firefox and other projects. Dictionaries available for those applications are compatible with this plugin.

Open Office provides a collection of dictionaries for several languages and dialects to [http://wiki.services.openoffice.org/wiki/Dictionaries download]. The OOo 3.x extensions (*.oxt) are compressed archives which can be opened with your favourite archiver (for example [http://www.7-zip.org/ 7-Zip] or File Roller).
Copy the '''.aff''' file and the '''.dic''' file to the directory configured in 'Path settings, Dictionaries' (see above).

==Thesaurus files==
The files for the thesaurus are also available from OOo, like the dictionaries. Copy the thesaurus files ('''th_*.dat''' and '''th_*.idx''') to the directory configured in
'Path settings, Thesauri' (see above) and rename them to match the name of the dictionary but prepend "th_" and let the extension as is.

Example: If the dictionary files (for one language) are "en_GB.aff" and "en_GB.dic" the files used for the thesaurus are "th_en_GB.idx" and "th_en_GB.dat".

==Bitmaps (flags)==
The bitmap of the actually selected language is shown in the status bar. If no bitmap is found, the name of the language is shown. The bitmap must be a PNG image. Choose a flag from the "famfamfam_flag_icons.zip" and copy it to the directory configured in 'Path settings, Bitmaps' (see above) and rename it to match the name of the dictionary but let the extension png.

Example: If the dictionary files (for one language) are "en_GB.aff" and "en_GB.dic" the the bitmap is named "en_GB.png" .

==Styles to check==
Only text with specific styles gets checked (for example only comments and strings). Styles are automatically set by Scintilla (CodeBlocks editing component).

The file '''OnlineSpellChecking.xml''' contains a list with indices of the styles to check. The indices differ for different programming-languages so the file contains a list for every programming-language. To add styles, look for the name of the programming-language and the indices in the corresponding [https://wiki.next.codeblocks.org/index.php?title=Creating_a_custom_lexer_for_Code::Blocks_editor#Lexers '''lexer_XY.xml'''] file and add this information to the file OnlineSpellChecking.xml.

File:ConfigureSpellChecker.png

2010-10-13T23:48:58Z

Danselmi:

NassiShneiderman plugin

2010-10-13T21:34:37Z

Danselmi:

[[Category: Code::Blocks Contrib Plugins]]
{{Infobox_Plugin|
name = NassiShneiderman |
logo = [[Image:Generic-plugin.png]] |
developer = [[User:danselmi|danselmi]] |
maintainer = |
version =
}}
NassiShneiderman plugin allows the creation of [http://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram Nassi Shneiderman diagrams] within Code::Blocks.

=Create a diagram=
There are two possibilities to create a diagram.
# To create an empty diagram select the menu options "File"->"New"->"Nassi Shneiderman diagram".
# The second option is to creates a diagram from C/C++ source code.

In an editor window highlight some code to create the diagram from. For example the body of a function/method from the opening braces till the closing brace. Then right click the selection and choose "Nassi Shneiderman"->"Create diagram".
[[File:NassiShneidermanCreate1.png]]<br />
You should get a new diagram:<br />
[[File:NassiShneidermanCreate2.png]]

The parser has some limitations:
* Comments can not be at the end of a branch.
* From a definition of a function it is only able to parse the body, not the declaration.
* For sure, you will find a lot more...

=Editing structograms=

=What to do with a diagram?=
You can do a lot of things with a structogram:
# Store for later usage. The diagram can be stored "File"->"Save file" or "File"->"Save file as...".
# It is possible to export to different formats "File"->"Export"->
#* "Export source..." to save as C source file.
#* "StrukTeX" to use in your documentation in LaTeX.
#* "PNG" or "PS" and eventually "SVG" to have a diagram in an image format known by a lot of other tools.
# Directly insert the code into the editor: Open or create a diagram. Back in an editor window right click and choose "Nassi Shneiderman"->"insert from xy" (You get a list with all open diagrams here).
# Drag'n'Drop the diagram (or parts of it) to other tools. For example to OpenOffice Writer to get an image in your documentation.

If the choosen diagram has a selection, the export or code-generation takes only this part of the diagram.

=Extensions=
The NassiShneiderman plugin supports some extensions of Nassi-Shneiderman diagrams:
# break has a special brick with an "right-arrow"
# continue has a special brick with a "left-arrow"
# To be able to create diagrams from c/c++ switch statements, the selection does not implicitely break before a case. The different cases are vertically aligned.

Code::Blocks Plugins

2010-10-13T21:14:19Z

Danselmi:

[[Category: User Documentation]]
== General ==

Code::Blocks' features can be extend by using '''plugins''', most of them listed on this page. There are generally three types of plugins:
# Core plugins - developed and maintained by the core C::B team.
# Contrib plugins - developed and maintained by the community and proven to be very valuable. So they are integrated into the C::B SVN.
# 3rd party plugins - developed and maintained by the community but not (yet?) in the C::B repository. Theses plugins often have their own repository or are being posted (including the source code) in the forums.

'''If you are looking for plugins:'''
# Look in the official release. Notice that the installer / package manager might require you to enable some of the plugins specifically. So READ carefully.
# Search the forums for announcements, especially the forums at [/index.php/board,14.0.html].
# There might be information on the WiKi concerning other plugins on this page and '''[[Announcement_for_plugins/patches|here]]'''.

For Windows users, the default behavior of the current installer (10.05) does not install contrib plugins. You need to manually check the "contrib plugin" checkbox when asked for selected components to install. There is no way to install them manually afterwards.

'''If you are developing plugins:'''
Surely you can work with plugin as you like, but here are some suggestions:
* Announce them in the plugin development board in the forums - including the (initial) source code at [/index.php/board,14.0.html].

OR

* Setup your own webpage (or use a file sharing platform) and post the link to the sources/binaries/svn access in the plugin development board in the forums at [/index.php/board,14.0.html].

OR

* Setup a repository, probably at BerliOS or SourceForge, post the link to the sources/binaries/svn access in the plugin development board in the forums at [/index.php/board,14.0.html]. Notice: This is very convenient as attachments in our forum might be deleted from time to time. So it is not safe to post source code in the forums.

THEN

# Enter the plugins description on this page.
# Announce the plugin '''[[Announcement_for_plugins/patches|here]]''' using '''[[Template_for_plugin_announcement|this]]''' template.

== Core Plugins ==

The core plugins are installed by default and offer the basic functions of Code::Blocks. The core plugins are maintained / developed by the official development team.

'''[[Autosave plugin|Autosave]]'''

:Saves project files between intervals.

'''[[Class Wizard plugin|Class Wizard]]'''

:Provides wizard for creating new classes.

'''[[Code Completion plugin|Code Completion]]'''

:Provides code completion functionality and class browser.

'''[[Compiler plugin|Compiler]]'''

:Provides support for various compilers in one interface.

'''[[Debugger plugin|Debugger]]'''

:Provides support for various debuggers in one interface.

'''[[File Extension Handler plugin|File Extensions Handler]]'''

:Adds extra file extension handlers.

'''[[Open Files List plugin|Open Files List]]'''

:Manages a list of all opened files (editors).

'''[[Projects Importer plugin|Projects Importer]]'''

:Imports projects from other IDE's, e.g. MS Visual Studio and DevC++.

'''[[Scripted Wizard plugin|Scripted Wizard]]'''

:Provides scripted wizard functionality.

'''[[Source Code Formatter plugin|Source Code Formatter]]'''

:Formats source code files with specific style.

'''[[To-Do List plugin|To-Do List]]'''

:Adds to-do items to source code.

'''[[WinXP Look'n'Feel plugin|WinXP Look'n'Feel]]'''

:Creates manifest file which enables the version 6.0 of the Common Controls on Windows XP.

== Contrib Plugins ==

The user-''contrib''uted plugins are not installed by default and offer extended functionality for Code::Blocks. The contrib plugins are maintained / developed by third-party developers.

'''[[Aligner]]'''

:Code alignment.

'''[[AutoVersioning|Auto Versioning]]'''

:Helps you keep track of your project version and status.

'''[[Browse Tracker plugins|Browse Tracker]]'''

:Browse to previous source positions.

'''[[C::B Games plugin|C::B Games]]'''

:Games in a integrated development environment? You bet.

'''[[Code Profiler plugin|Code Profiler]]'''

:Provides graphical interface to GNU GProf profiler.

'''[[Code Snippets plugin|Code Snippets]]'''

:Manages small pieces of code (i.e. snippets).

'''[[Code Statistics plugin|Code Statistics]]'''

:Shows various statistics from source code files.

'''[[Copy Strings to Clipboard plugin|Copy Strings to Clipboard]]'''

:Copies literal strings from the current editor to clipboard.

'''[[Cscope]]'''

:Integrates Cscope (http://cscope.sourceforge.net/) into Code::Blocks.

'''[[DevPak Installer plugin|DevPak Installer]]'''

:Installs and updates DevC++ DevPaks.

'''[[DoxyBlocks|DoxyBlocks]]'''

:This plugin provides doxygen integration for Code::Blocks.

'''[[DragScroll plugin|DragScroll]]'''

:Enables dragging and scrolling with mouse.

'''[[Editor Tweaks]]'''

:This plugin provides some additional tweaks for Code::Blocks editor.

'''[[Environment Variables plugin|Environment Variables]]'''

:Sets environment variables within the focus of Code::Blocks.

'''[[Help plugin]]'''

:Integrates third-party help files to the interface.

'''[[HexEditor plugin]]'''

:Opens files in a Code::Blocks integrated HexEditor.

'''[[Keyboard Shortcuts plugin|Keyboard Shortcuts]]'''

:Manages menu shortcuts.

'''[[Koders plugin|Koders]]'''

:Queries the Koders webpage for keywords.

'''[[KeyMacs plugin]]'''

:KeyMacs (or Keyboard Macros) plugin enables Recording, Playback, and editing of keystroke macros.

'''[[NassiShneiderman]]'''

:Allows the creation of Nassi Shneiderman diagrams within Code::Blocks.

'''[[RegEx Testbed plugin|RegEx Testbed]]'''

:Regular expressions testbed.

'''[[Source Exporter plugin|Source Exporter]]'''

:Exports source code files to other formats such as HTML and PDF.

'''[[Symbol Table plugin|Symbol Table]]'''

:A simple graphical interface to the GNU symbol table displayer (nm).

'''[[ThreadSearch]]'''

:Multi-threaded 'Search in files' with preview window.

'''[[Valgrind plugin|Valgrind]]'''

:Valgrind analysis tools integration.

'''[[wxSmith plugin|wxSmith]]'''

:RAD tool for creating wxWidgets dialogs.

== 3rd Party Plugins ==

3rd party plugins - developed and maintained by the community but not (yet?) in the C::B repository. The contrib plugins are maintained / developed by third-party developers.

'''[[Fortran Project plugin|Fortran Project]]'''

:This plugin provides symbol browser and code-completion for Fortran files.

'''[[TRACE32 Debugger]]'''

:Extends the Debugger plugin of Code::Blocks to work with the TRACE32 Debuggers. TRACE32 documentation "int_codeblock.pdf" and debuggert32.cbplugin are located on the enclosed SW CD on purchase of TRACE32

If you have questions -> ask in the forums at [/index.php/board,14.0.html].

'''[[SpellChecker]]'''

:A plugin to check the spelling of strings and comments.

NassiShneiderman plugin

2010-09-10T11:17:06Z

Danselmi:

NassiShneiderman plugin allows the creation of [http://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram Nassi Shneiderman diagrams] within Code::Blocks.

=Create a diagram=
There are two possibilities to create a diagram.
# To create an empty diagram select the menu options "File"->"New"->"Nassi Shneiderman diagram".
# The second option is to creates a diagram from C/C++ source code.

In an editor window highlight some code to create the diagram from. For example the body of a function/method from the opening braces till the closing brace. Then right click the selection and choose "Nassi Shneiderman"->"Create diagram".
[[File:NassiShneidermanCreate1.png]]<br />
You should get a new diagram:<br />
[[File:NassiShneidermanCreate2.png]]

The parser has some limitations:
* Comments can not be at the end of a branch.
* From a definition of a function it is only able to parse the body, not the declaration.
* For sure, you will find a lot more...

=Editing structograms=

=What to do with a diagram?=
You can do a lot of things with a structogram:
# Store for later usage. The diagram can be stored "File"->"Save file" or "File"->"Save file as...".
# It is possible to export to different formats "File"->"Export"->
#* "Export source..." to save as C source file.
#* "StrukTeX" to use in your documentation in LaTeX.
#* "PNG" or "PS" and eventually "SVG" to have a diagram in an image format known by a lot of other tools.
# Directly insert the code into the editor: Open or create a diagram. Back in an editor window right click and choose "Nassi Shneiderman"->"insert from xy" (You get a list with all open diagrams here).
# Drag'n'Drop the diagram (or parts of it) to other tools. For example to OpenOffice Writer to get an image in your documentation.

If the choosen diagram has a selection, the export or code-generation takes only this part of the diagram.

=Extensions=
The NassiShneiderman plugin supports some extensions of Nassi-Shneiderman diagrams:
# break has a special brick with an "right-arrow"
# continue has a special brick with a "left-arrow"
# To be able to create diagrams from c/c++ switch statements, the selection does not implicitely break before a case. The different cases are vertically aligned.

NassiShneiderman plugin

2010-09-10T11:15:06Z

Danselmi:

NassiShneiderman plugin allows the creation of [http://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram Nassi Shneiderman diagrams] within Code::Blocks.

=Create a diagram=
There are two possibilities to create a diagram.
# To create an empty diagram select the menu options "File"->"New"->"Nassi Shneiderman diagram".
# The second option is to creates a diagram from C/C++ source code.

In an editor window highlight some code to create the diagram from. For example the body of a function/method from the opening braces till the closing brace. Then right click the selection and choose "Nassi Shneiderman"->"create diagram".
[[File:NassiShneidermanCreate1.png]]<br />
You should get a new diagram:<br />
[[File:NassiShneidermanCreate2.png]]

The parser has some limitations:
* Comments can not be at the end of a branch.
* From a definition of a function it is only able to parse the body, not the declaration.
* For sure, you will find a lot more...

=Editing structograms=

=What to do with a diagram?=
You can do a lot of things with a structogram:
# Store for later usage. The diagram can be stored "File"->"Save file" or "File"->"Save file as...".
# It is possible to export to different formats "File"->"Export"->
#* "Export source..." to save as C source file.
#* "StrukTeX" to use in your documentation in LaTeX.
#* "PNG" or "PS" and eventually "SVG" to have a diagram in an image format known by a lot of other tools.
# Directly insert the code into the editor: Open or create a diagram. Back in an editor window right click and choose "Nassi Shneiderman"->"insert from xy" (You get a list with all open diagrams here).
# Drag'n'Drop the diagram (or parts of it) to other tools. For example to OpenOffice Writer to get an image in your documentation.

If the choosen diagram has a selection, the export or code-generation takes only this part of the diagram.

=Extensions=
The NassiShneiderman plugin supports some extensions of Nassi-Shneiderman diagrams:
# break has a special brick with an "right-arrow"
# continue has a special brick with a "left-arrow"
# To be able to create diagrams from c/c++ switch statements, the selection does not implicitely break before a case. The different cases are vertically aligned.

NassiShneiderman plugin

2010-09-09T22:56:01Z

Danselmi: Created page with 'NassiShneiderman plugin allows the creation of [http://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram Nassi Shneiderman diagrams] within Code::Blocks. =Create a diagra…'

NassiShneiderman plugin allows the creation of [http://en.wikipedia.org/wiki/Nassi%E2%80%93Shneiderman_diagram Nassi Shneiderman diagrams] within Code::Blocks.

=Create a diagram=
There are two possibilities to create a diagram.
# To create an empty diagram select the menu options "File"->"New"->"Nassi Shneiderman diagram".
# The second option creates a diagram from C/C++ source code.

In an editor window highlight some code to create the diagram from. For example the body of a function/method from the opening braces till the closing brace. Then right click the selection and choose "Nassi Shneiderman"->"create diagram".
[[File:NassiShneidermanCreate1.png]]<br />
You should get a new diagram:<br />
[[File:NassiShneidermanCreate2.png]]

The parser has some limitations:
* Comments can not be at the end of a branch.
* From a definition of a function it is only able to parse the body, not the declaration.
* For sure, you will find a lot more...

=Editing structograms=

=What to do with a diagram?=
You can do a lot of things with a structogram:
# Store for later usage. The diagram can be stored "File"->"Save file" or "File"->"Save file as...".
# It is possible to export to different formats "File"->"Export"->
#* "Export source..." to save as C source file.
#* "StrukTeX" to use in your documentation in LaTeX.
#* "PNG" or "PS" and eventually "SVG" to have a diagram in an image format known by a lot of other tools.
# Directly insert the code into the editor: Open or create a diagram. Back in an editor window right click and choose "Nassi Shneiderman"->"insert from xy" (You get a list with all open diagrams here).
# Drag'n'Drop the diagram (or parts of it) to other tools. For example to OpenOffice Writer to get an image in your documentation.

If the choosen diagram has a selection, the export or code-generation takes only this part of the diagram.

=Extensions=
The NassiShneiderman plugin supports some extensions of Nassi-Shneiderman diagrams:
# break has a special brick with an "right-arrow"
# continue has a special brick with a "left-arrow"
# To be able to create diagrams from c/c++ switch statements, the selection does not implicitely break before a case. The different cases are vertically aligned.

File:NassiShneidermanCreate2.png

2010-09-09T21:58:45Z

Danselmi:

File:NassiShneidermanCreate1.png

2010-09-09T21:50:49Z

Danselmi: Shows how to create a diagram from sourcecode.

Shows how to create a diagram from sourcecode.

Creating a custom lexer for Code::Blocks editor

2009-12-03T18:46:14Z

Danselmi: /* Adding support for a lexer not supported in Scintilla */

[[Category:Developer Documentation]]
Code::Blocks can provide syntax highlighting for any of the languages supported by Scintilla http://www.scintilla.org (the Rich Editing API used by C::B to provide syntax highlighting, code folding etc). Each language that C::B provides highlighting for has a C::B specific xml file found under <tt>sdk/resources/lexers</tt> that specifies styles and keywords of the language (they're simple XML files with names of the form <tt>lexer_*.xml</tt>). Adding a new language that is supported by Scintilla is as simple as adding an xml file for that language. At a minimum, the xml file must list the available set of styles for the lexical elements of a language and provide for keywords (the file will also specify a file containing sample code for editing and previewing lexer styles in Code::Blocks). Actual styles and keywords for each language can be edited by users within Code::Blocks under Settings->Editors->Syntax Highlighting allowing them view the results in a preview window (for the preview to display you will need to provide this sample code in a separate file also located in <tt>sdk/resources/lexers</tt>). User customized styles and keywords are kept in the users <tt>default.conf</tt> file (i.e. the xml file is never changed within codeblocks) allowing users to easily revert to the xml file.

To illustrate how you might construct a new lexer xml file let's look at the pre-installed CPP lexer, whose styles and keywords are stored in <tt>lexer_cpp.xml</tt>.

==XML==

<?xml version="1.0"?>

Basically this says "I am an XML file". '''Very Important'''

==DOCTYPE==

<!DOCTYPE CodeBlocks_lexer_properties>

This needs to be in every lexer file. Code::Blocks '''will not''' load the lexer if this is not present.

==Lexers==

<Lexer name="C/C++"
index="3"
filemasks="*.c,*.cpp,*.cc,*.cxx,*.h,*.hpp,*.hh,*.hxx,*.inl">

Pretty much self explanatory, except for the "magic" ''index'' number (we'll come to it in a sec).

* '''name''' is the lexer's configuration name. This will appear in the editor's configuration dialog, in the languages drop down box (in colors editing page).

* '''filemasks''' is a comma separated list of the extensions that this lexer should be used for. This is case-insensitive.

* '''index''' corresponds with the <tt>wxSCI_LEX_*</tt> constants, found in <tt>sdk/wxscintilla/include/wx/wxscintilla.h</tt>. In this example, if you look in <tt>sdk/wxscintilla/include/wx/wxscintilla.h</tt>, you'll see that ''index 3'' matches <tt>wxSCI_LEX_CPP</tt>. That is the ''lexer id'' for C/C++ syntax highlighting.

If we were building a lexer configuration for let's say, XML (random choice) we would look up the constant <tt>wxSCI_LEX_XML</tt> which is defined to be number ''5''. So ''index=5''. Simple.

==Styles==

Next follows many <tt><Style></tt> tags defining the different styles:

<Style name="Default"
index="0"
fg="0,0,0"
bg="255,255,255"
bold="0"
italics="0"
underlined="0" />

* '''name''' is the style's name. It appears in the editor's configuration dialog, in the colors editing page.

* '''fg''' is the foreground color. Comma separated list of three numbers from 0 to 255. In order: red, green and blue (RGB).

* '''bg''' is the background color.

* '''bold''' is <tt>"0"</tt> for disabled, <tt>"1"</tt> for enabled.

* '''italics''' is <tt>"0"</tt> for disabled, <tt>"1"</tt> for enabled.

* '''underlined''' is <tt>"0"</tt> for disabled, <tt>"1"</tt> for enabled.

You don't have to define all of these attributes. It's good to define them all for the <tt>"default"</tt> style (all lexers have a default style), but only the attributes needed should be defined for the rest of the styles.

* The '''index''' number in the <tt><Style></tt> tags, comes from a different set of constants defined in <tt>sdk/wxscintilla/include/wx/wxscintilla.h</tt>.

For each language supported by scintilla, there is a set of styles ''(lexical states)'' defined (these are what we're trying to configure with these files).

For example, for C/C++ files (<tt>wxSCI_LEX_CPP</tt>, remember?) the styles are defined as <tt>wxSCI_C_*</tt>.

For the <tt>"default"</tt> style shown above, this would be <tt>wxSCI_C_DEFAULT</tt> which is defined to be ''0''. Hence ''index=0'' for <tt>"default"</tt>.

<Style name="Comment (normal)"
index="1,2"
fg="160,160,160" />

This is the style definition for normal comments. As you can see you can define a single style for more than one style index, in this case two: ''1'' and ''2'' (always comma separated).

''1'' is for <tt>wxSCI_C_COMMENT</tt> (the C comment <tt>/* */</tt>) and ''2'' is for <tt>wxSCI_C_COMMENTLINE</tt> (the C++ comment to end of line <tt>// </tt>).

There are some special styles defined by Code::Blocks and are available to all lexers:

* '''index -99''' is the selected text style.
* '''index -98''' is the active line style (the line the caret is on).
* '''index -2''' is the breakpoint line style.
* '''index -3''' is the debugger active line style (while stepping the debugger).
* '''index -4''' is the compiler warning/error line style. ('''Note: this index was removed completely?''')

==Keywords==

Now on to the keywords.

<Keywords>
<Set index="0"
value="if int long try while and-so-on" />
<Set index="1" />
<Set index="2"
value="param remarks return $ @ \ & < > # { } and-so-on" />
</Keywords>

If you are defining a lexer configuration for a language that has keywords they should be added in the <tt><Keywords></tt> tag.
In the scintilla version used by Code::Blocks, you can setup up to 9 keyword sets (the "index" attribute). What each set does and which sets are used by a lexer, is defined by the lexer itself.

If you open LexCPP.cxx (from the scintilla sources), you will find the following:

static const char * const cppWordLists[] = {
"Primary keywords and identifiers",
"Secondary keywords and identifiers",
"Documentation comment keywords",
"Unused",
"Global classes and typedefs",
0,
};

This tells us which indices are valid and what each one represents:

Index 0, "Primary keywords and identifiers"

Index 1, "Secondary keywords and identifiers"

Index 2, "Documentation comment keywords"

(notice that index "3" is not used)

Index 4, "Global classes and typedefs"

==Sample Code==

The tag left is <tt>SampleCode</tt>. This is much pretty self explanatory:

<SampleCode value="lexer_cpp.sample"
breakpoint_line="20"
debug_line="22"
error_line="23"/>

* '''value''' is the filename of the code that will be shown in the Preview window.
When creating a <tt>lexer_*.sample</tt> try to do it with simple and concise sample code (like the ones found in a typical "Hello world!"), yet include all the styles of the lexer.

There are other optional options ('''Note: this index was removed completely?''')
* '''breakpoint_line''' is the number of the line in which a breakpoint line will be previewed.
* '''debug_line''' is the number of the line in which a debug line will be previewed.
* '''error_line''' is the number of the line in which an error line will be previewed.

==Tips==
When writting a lexer, this can be useful:
* .properties files of SciTE (the official Scintilla-based text editor) [http://scintilla.sourceforge.net/SciTE.html]

==Adding support for code-folding==

'''Note: support for code-folding can't be done from the lexer files. It must be done right in the Scintilla code'''.

See here: http://sphere.sourceforge.net/flik/docs/scintilla-folding.html

==Adding support for a lexer not supported in Scintilla==

'''Note: support for a lexer not supported in Scintilla is out of scope of Code::Blocks. It must be done right in the Scintilla code.'''

Here are some instructions: http://scintilla.sourceforge.net/Lexer.txt. To be able to use your newly created lexer in C::B, adjust the validity check of "lexer" in EditorColourSet::AddHighlightLanguage().

* After you've written the Scintilla lexer, submit the files to the [http://sourceforge.net/tracker/?group_id=2439 Scintilla tracker], following their own [http://scintilla.sourceforge.net/SciCoding.html coding style].

* After that, make any necesary change to wxScintilla and sumbit the files to the [http://sourceforge.net/tracker/?group_id=51305&atid=462818 wxScintilla tracker] or send a mail to the autor wyo@users.sourceforge.net (Otto Wyss).

* And finishing, be sure to send all to the [http://developer.berlios.de/patch/?func=addpatch&group_id=5358 Code::Blocks tracker] (Category: Lexer), and announce it at the [/index.php?board=7.0 Forum] and the [[Announcement for plugins/patches|Wiki announcement for plugins/patches]].

Languages supported by Code::Blocks lexers

2008-12-23T00:49:20Z

Danselmi:

[[Category:Developer Documentation]]
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 50%; table-layout: fixed;"

|- style="background: #ececec;"
! style="width: 12em" | Language
! [https://www.codeblocks.org/ Code::Blocks]
! [http://www.scintilla.org/SciTE.html SciTE]
|-

|-
! style="text-align: left; background: #ececec;" | Ada
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | AngelScript (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | ANS.1 MIB definition files
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | APDL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Assembler (NASM, MASM)
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Assembler (Hitachi, using the C++ lexer)
| {{yes}} (Why it uses the C++ lexer????)
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | AutoIt
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Avenue
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Batch (MS-DOS)
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Baan
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Bash
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | BlitzBasic
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Bullant
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | C/C++
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | C# (using the C++ lexer)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Clarion
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | conf (Apache)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | CSound
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | CSS
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | diff files
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | E-Script
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Eiffel
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Erlang
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Flagship (Clipper / XBase)
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Flash (ActionScript)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Fortran
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Forth
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Haskell
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | HTML
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | HTML with embedded JavaScript, VBScript, PHP and ASP
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | GameMonkey Script (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | Gui4Cli
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | IDL (both MSIDL and XPIDL)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Java
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | JavaScript
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | LISP
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | LOT
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Lout
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Lua
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Make
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Matlab
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Metapost
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | MMIXAL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | MSSQL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | nnCron
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | NSIS
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | nVidia cg (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | Objective Caml
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Ogre Material script (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | OpenGL Shading Language (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | Octave
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Pascal/Delphi
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Perl
| {{yes}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | PostScript
| {{yes}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | POV-Ray
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | PowerBasic
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Properties
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | PureBasic
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Python
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Rebol
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Ruby
| {{yes}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Scheme
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | scriptol
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Specman E
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Spice
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Smalltalk
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | SQL and PLSQL
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | TADS3
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | TeX and LaTeX
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Tcl/Tk
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | VB and VBScript
| {{yes}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Verilog
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | VHDL
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Windows resource (using the C++ lexer)
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | XML
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | YAML
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|}

*{{note|CodeFolding}} Supports code-folding.

Languages supported by Code::Blocks lexers

2008-12-23T00:40:56Z

Danselmi:

[[Category:Developer Documentation]]
{| border="1" cellpadding="1" cellspacing="0" style="font-size: 85%; border: gray solid 1px; border-collapse: collapse; text-align: center; width: 50%; table-layout: fixed;"

|- style="background: #ececec;"
! style="width: 12em" | Language
! [https://www.codeblocks.org/ Code::Blocks]
! [http://www.scintilla.org/SciTE.html SciTE]
|-

|-
! style="text-align: left; background: #ececec;" | Ada
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | AngelScript (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | ANS.1 MIB definition files
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | APDL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Assembler (NASM, MASM)
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Assembler (Hitachi, using the C++ lexer)
| {{yes}} (Why it uses the C++ lexer????)
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | AutoIt
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Avenue
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Batch (MS-DOS)
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Baan
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Bash
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | BlitzBasic
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Bullant
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | C/C++
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | C# (using the C++ lexer)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Clarion
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | conf (Apache)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | CSound
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | CSS
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | diff files
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | E-Script
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Eiffel
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Erlang
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Flagship (Clipper / XBase)
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Flash (ActionScript)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Fortran
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Forth
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Haskell
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | HTML
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | HTML with embedded JavaScript, VBScript, PHP and ASP
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | GameMonkey Script (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | Gui4Cli
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | IDL (both MSIDL and XPIDL)
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Java
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | JavaScript
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | LISP
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | LOT
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Lout
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Lua
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Make
| {{yes}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Matlab
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Metapost
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | MMIXAL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | MSSQL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | nnCron
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | NSIS
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | nVidia cg (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | Objective Caml
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Ogre Material script (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | OpenGL Shading Language (using the C++ lexer)
| {{yes}}{{refun|CodeFolding}}
| {{no}}
|-

|-
! style="text-align: left; background: #ececec;" | Octave
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Pascal/Delphi
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Perl
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | PostScript
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | POV-Ray
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | PowerBasic
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Properties
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | PureBasic
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Python
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Rebol
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Ruby
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Scheme
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | scriptol
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Specman E
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Spice
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Smalltalk
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | SQL and PLSQL
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | TADS3
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | TeX and LaTeX
| {{no}}
| {{yes}}
|-

|-
! style="text-align: left; background: #ececec;" | Tcl/Tk
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | VB and VBScript
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Verilog
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | VHDL
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | Windows resource (using the C++ lexer)
| {{yes}}
| {{no}}
|-
! style="text-align: left; background: #ececec;" | XML
| {{yes}}{{refun|CodeFolding}}
| {{yes}}{{refun|CodeFolding}}
|-

|-
! style="text-align: left; background: #ececec;" | YAML
| {{no}}
| {{yes}}{{refun|CodeFolding}}
|-

|}

*{{note|CodeFolding}} Supports code-folding.